- DATE:
- AUTHOR:
- Cvent Product News Team
Links
Actionable Insights Releases for August 20, 2025
Integrations
Integration Alerts: Real-time email notification
Expected Release Date: September 3, 2025
Cvent now offers real-time email notifications for authentication (auth) failures for integrations. This enhancement ensures that users are immediately informed when an integration connection fails due to authentication issues, allowing for prompt resolution and minimizing business disruption. The feature is designed to automatically notify all relevant integration contacts whenever an auth failure is detected, and notifications will continue until the issue is resolved.
What problem does it solve?
Cvent’s new real-time email notification feature for authentication (auth) failures in integrations is designed to address a longstanding gap in integration monitoring and user awareness. Previously, when an integration between Cvent and an external platform (such as a marketing automation tool) failed due to authentication issues, like expired credentials, revoked access, or permission changes, users often remained unaware until they noticed missing data or downstream business impacts. This lack of proactive visibility led to business disruption, data loss, increased support dependency, and potential compliance risks, as users had no way to know that their integration was no longer functioning as expected.
Current Scope
With this enhancement, all relevant integration contacts will be notified via email whenever an authentication failure is detected. The system covers several critical scenarios, including:
Authentication failures that cannot be recovered (for example, when the user who set up the integration is deleted, deactivated, or demoted, resulting in the integration being disabled).
Authentication failures where the root cause is unknown, prompting users to investigate and resolve the issue or contact Cvent support.
Authorization failures are caused by insufficient permissions (e.g., when the authenticated user no longer has the required access level).
The current release scope is limited to
Alerts for only Cvent authentication
The integrations are powered by Cvent Integration Hub.
How to Enable or Disable Email Alerts
Default State: Authentication alerts are enabled by default for all eligible integrations.
Toggle Control: Users can enable or disable email alerts for a specific integration using a toggle button located on each integration’s tile within the Integration Apps page.
Managing Recipients: To add or remove recipients, navigate to the Integration Contacts page (Admin > Integration > Integration Contacts). Here, you can edit the list of users who will receive notifications for each integration. The user who has authenticated the integration will be added automatically as an integration contact.
Frequency: Each recipient will receive at most one email per auth error per 24-hour period. If the error persists, daily reminders will continue until the issue is resolved.
Key Things to Note
Alerts for third-party authentication failures are not included in the current release. Support for these scenarios is planned for future updates.
Alerts for custom integrations are not supported at this time.
REST API Enhancements for List Orders, List Order Items, and List Transaction Items
This release delivers a set of enhancements to the Orders and Transactions REST API endpoints, focused on improving developer experience and operational efficiency in reconciling financial data for an event.
Key Highlights:
Additional Discount Details in Orders and Order Items: The GET /orders and GET /orders/items endpoints will now return the discount ID and the calculated total amount of the discount applied to each order and order item. This enables clients to accurately track and reconcile the actual discount amount applied at both the order and item levels.
General Ledger Code Allocation: The GET /orders/items endpoint will now include the ID and percent allocation for each general ledger item. This provides greater transparency into how order item amounts are distributed across general ledger codes, supporting more precise accounting and integration with financial systems.
Transaction Item Unique Identifier: The GET /transactions/items endpoint will now return a unique ID and the associated order item ID for each transaction item. These identifiers improve traceability between specific transaction items and their corresponding order items, facilitating easier data mapping and reconciliation.
Retrieval of Deleted Orders and Order Items: The GET /orders and GET /orders/items endpoints will now support returning deleted orders and order items through a query parameter, to provide an accurate record of all order activity.
Once released, documentation updates for these REST API endpoints can be found on the Cvent Developer Portal under the "Events" section.
Integration App History Report - Expanded Support for Data Sync Errors
The Integration App History Report is a key tool within Cvent for monitoring the health and reliability of integrations powered by Cvent Integration Hub. Historically, this report has enabled users to track authentication errors, helping ensure that integrations are properly connected and authorized. However, until now, it has not provided visibility into workflow-level (data sync) errors - issues that occur during the actual transfer of data between Cvent and third-party systems.
With this release, the report is being significantly enhanced to capture and display workflow errors. This update directly addresses longstanding pain points for two key personas: Planner Admins and Cvent Support Teams.
Scope of the Release
This release significantly expands the capabilities of the Integration App History Report to provide comprehensive visibility into data sync (workflow) errors. The enhanced report now captures and displays detailed information for each error, including (not limited to):
Error Type: Differentiates between authentication and workflow (data sync) errors.
Source: Identifies whether the error originated from Cvent or a third-party system (e.g., Zoom).
Operation: Specifies the integration operation or workflow step where the error occurred.
Error Details: Presents clear, actionable error messages, including status codes and user-friendly descriptions.
Entity Information: This includes details about the affected entity (such as an attendee, session, or event), along with relevant identifiers and context.
User and Configuration Data: Shows which user and configuration were involved in the failed integration attempt.
The initial rollout of this expanded error reporting focuses on the Zoom integration.
Future Scope
Additional integrations will be supported in future phases as part of an ongoing effort to standardize and improve error visibility across all supported integrations.
Accessing the Report
You can access the Integration App History Report (the name might be updated) through two primary paths within the Cvent platform:
Via Admin Reports:
Navigate to Admin > Reporting > Reports
In the search bar, enter “Integration App History.”
Select the report from the search results to view detailed integration error logs.
Via Integration Apps:
Go to Admin > Integrations > Integration Apps
Locate the integration tile for the specific integration you want to review (e.g., Zoom)
Click the View Report link available on the integration tile to access the error log for that integration
Who Benefits and How?
The expanded Integration App History Report is designed for these audiences:
Planner/Integration Admins:
Gain real-time visibility into both authentication and data sync (workflow) errors for integrations powered by Cvent Integration Hub.
Can proactively troubleshoot issues such as invalid data formats or missing fields, and actionable error messages are surfaced directly in the product.
This self-service capability reduces reliance on support teams, speeds up resolution, and helps maintain business continuity and trust in the platform.
Internal Support Teams:
Benefit from centralized, standardized error reporting, which provides detailed diagnostic information for each integration failure.
Enables faster, more accurate troubleshooting without needing to dig through backend logs or escalate to engineering.
Improves operational efficiency and scalability, allowing support to resolve more cases with less manual effort and deliver a better customer experience.
Key Things to Note
Custom integrations are not supported at this time.
Allow Updating Attendee Status from Pending to Accepted/Declined via REST API
This release enhances the flexibility and efficiency of attendee management by extending the ability to update an invitee's status from Pending to Accepted or Declined through the "Update Attendee" REST API. Previously, this functionality was only available to planners through the UI, and even then, planners could not update the attendees’ registration details while changing their status. With this update, planners and integrators can programmatically update both the attendee status and their registration details in a single API request, streamlining workflows and reducing manual intervention.
User Accomplishment
Users can now automate the process of moving invitees between Pending, Accepted, and Declined statuses via REST API, while simultaneously updating registration details such as responses to custom questions, session selections, or personal information. This eliminates the need for separate manual updates and allows for more seamless integration with external systems.
Key Highlights and Changes
The "Update Attendee" REST API now supports the following Attendee status movements
'No response' to 'Pending approval'
'Pending approval' to 'Accepted'
'Pending approval' to 'Denied'
'Denied' to 'Pending approval'
Planners can also add the invitee directly to the 'Pending Approval' status using the "Add Attendee" Rest API.
In addition to changing the status, planners can update registration details (e.g., custom questions, session choices, personal info) in the same API call.
Enables automation for organizations with custom workflows or external systems.
Cvent Data Bridge - Expanded Data Entities Support
Expected Release Date: September 3, 2025
Cvent Data Bridge is a scalable and automated solution that enables organizations to seamlessly and securely transfer their event data from Cvent to their cloud storage. This eliminates the need for manual exports, complex workarounds, and IT-heavy integrations. With automated access to event data in cloud storage, organizations can easily integrate it into data solutions that natively connect to clouds, such as data warehouses (Snowflake, Databricks, Salesforce Data Cloud) and analytics platforms (Adobe Experience Platform). This empowers sales, marketing, and analytics teams to unlock deeper insights, enhance personalization, automate workflows, and drive data-driven decision-making, ultimately accelerating business growth and maximizing event ROI.
Cvent Data Bridge - AWS S3 (Released on May 7, 2025, Release Notes)
Cvent Data Bridge - SFTP (Releasing on Aug 20, 2025, Release Notes)
What’s New
We are excited to announce support for additional data entities in Data Bridge. This enhancement allows you to sync even more types of event data to your preferred cloud storage, expanding your analytics and reporting capabilities.
List of new data entities
Attendee Activities
Contact Groups
Admission Items
Attendance Duration
Email History
Transactions
Transaction Items
Order
Order Items
Custom Fields
We are committed to continuously expanding Data Bridge’s capabilities, and support for additional data entities will be added on an ongoing basis to meet evolving customer needs.
Action Required for Integration Admins
To start syncing the newly supported entities, integration admins must update their Data Bridge configuration:
Go to your Cvent Data Bridge configuration.
Select the new entities you wish to sync.
Save your configuration to ensure these entities are included in future data transfers to your cloud storage.
Only the entities you select will be synced. If you do not select the new entities, their data will not be transferred to your cloud storage.
Enhancements to Cvent and Jifflenow Integration
The integration introduces key enhancements to improve appointment handling, streamline setup, and reduce manual dependencies for customers and internal teams. These updates are designed to deliver a more seamless and scalable experience for event planners who leverage both platforms.
Key Enhancements
Removed Dependency on 'Cvent Contact ID' Custom Field
Previously, syncing registrants from Cvent to Jifflenow required storing the Cvent Contact ID in a custom user field. This manual setup often led to sync failures if the field was missing, modified, or not properly maintained.
What’s new: The Contact ID is now securely stored in the backend, eliminating the need for a custom field. This change ensures reliable meeting synchronization and removes the risk of misconfiguration or manual errors.
Introduction of Standard 'Meeting Title' Field
Customers previously had to create a custom 'Meeting Title' field in Jifflenow, leading to inconsistent API names and the need for custom mapping.
What’s new: A standard 'Meeting Title' field is now available in Jifflenow. If populated, this value will sync as the Subject of the appointment in Cvent. If left empty, the integration will default to the existing 'Meeting With' field.
This ensures consistent mapping and removes the need for custom integrations.
Support for Substituted Registrants
Earlier versions did not handle attendee substitutions, resulting in sync errors when a registrant was replaced in Cvent.
What’s new: When a registrant is substituted in Cvent, the corresponding Jifflenow user is automatically marked as Unregistered during the next sync. This prevents them from being associated with meetings or causing sync errors.
Note: The newly substituted attendee is not automatically added to the original meetings; this must be done manually in Jifflenow.
Improved Appointment Location Handling
Previously, if a Jifflenow meeting location name matched an existing Cvent location, sync errors could occur due to duplicate names.
What’s new: The integration now checks for existing Cvent locations during sync. If a match is found, the Location ID is used for appointment creation or updates. If not, the location name is passed as a custom string, ensuring accurate mapping and preventing errors.
Disable Enforce Scheduling Rules by Default
In some scenarios, scheduling rules in Cvent caused appointment creation to fail, such as when a user had a conflicting appointment or when rules restricted scheduling.
What’s new: The "Enforce Scheduling Rules" option is now disabled by default for appointments created from Jifflenow. This ensures all Jifflenow meetings are successfully created in Cvent, regardless of existing scheduling constraints.
Action Required: Re-authenticate Existing Integrations
With the introduction of a new scope in the Jifflenow <> Cvent integration, all existing integrations must be re-authenticated to ensure continued functionality and access to the latest features.
What you need to do: Integration administrators should initiate the re-authentication process for all active Jifflenow <> Cvent integrations. This step is mandatory to grant the updated permissions required by the new version.
Why this is important: Without re-authentication, the integration may not function as expected, and new enhancements will not be available.
Reporting
Compare Cross Event Insights
With the new Comparison feature on Cross Event Insights, event planners and marketers can instantly compare key event metrics from the current period to a previous one, all within the familiar reporting interface. This enhancement eliminates the need for manual data exports and cumbersome spreadsheet work, empowering users to spot trends, measure growth, and identify areas for improvement at a glance. Now, making data-driven decisions and optimizing event strategies is faster and easier than ever before.
Important Notes
Instantly view side-by-side comparisons of essential metrics (like registration counts and attendee engagement) for current versus previous event periods, directly in the Cross Event Insights dashboard.
No more manual exports or calculations—period-over-period analysis is now fully integrated into the user's reporting workflow.
The streamlined experience supports faster, evidence-based decision-making and more impactful performance reporting.
Additional Resources
Cvent Community: Do you have questions about anything we’ve rolled out this window? As always, get questions answered in the Community via the Open Forum.
Beta Program Opportunities: Help us improve Cvent Products by being the first to test products before they're widely available. Join Beta Programs.
Links