Convertr Help Centre Help Center home page
Submit a request
Sign in
  1. Convertr Help Centre
  2. Product
  3. Integrations

Cvent Lead Ingestion Follow

Cvent Lead Ingestion turns event attendance into pipeline-ready leads automatically — every attendee flows into Convertr where they are instantly enriched, validated, and delivered to your sales team as fresh, complete leads ready for action. This reduces the time your team spends processing each event data from hours or days to minutes.

 

Overview

Cvent Lead Ingestion brings attendee data from completed Cvent events into Convertr as leads.

Convertr checks for completed events every hour. Once a completed event is detected, attendee records are ingested immediately and flow through Convertr's full processing pipeline:

  • All standard attendee fields and custom fields are ingested as lead data.
  • Leads are automatically enriched based on your campaign setup — filling in gaps that are common with event attendee data.
  • Leads are validated against your configured rules using any of the ingested fields.
  • Validated leads are delivered to your CRM and downstream systems.

The result is a fully automated, end-to-end pipeline from event completion to CRM delivery — no manual exports, no data gaps, no processing errors.

 

Setup Process

Connecting Your Cvent Account

Before you begin, locate your Cvent API credentials (Client ID and Client Secret). See the Cvent Developer Quickstart in Cvent developer documentation for instructions.

Please note: Your Cvent credentials must have event and attendee API permissions.

To connect your Cvent account:

  1. In the main navigation, go to Connected Apps → Cvent.
  2. On the Cvent Accounts page, click Connect Cvent Account.
    Screenshot of Connect Cvent Account button
  3. In the Connect Cvent Account form, provide the following details:
    Screenshot of Connect Cvent Account form
    • Name — a label of your choice to help you identify these credentials.
    • Cvent Host Region — select the region that matches your Cvent account. You can identify your region from your Cvent dashboard URL: app.cvent.com indicates North America, app-eur.cvent.com indicates Europe.
    • Client ID — your Cvent API Client ID.
    • Client Secret — your Cvent API Client Secret.
  4. Click Save.

Connecting a Convertr Campaign to a Cvent Event

To connect a Convertr campaign to a Cvent event:

  1. In Connected Apps → Cvent, click Manage Connected Campaigns next to the Cvent account you connected earlier.
    Screenshot of Manage Connected Campaigns button
  2. On the Cvent Connected Campaigns page, click Connect Campaign.
    Screenshot of Connect Campaign button
  3. In the Connect Campaign to Cvent Event form, select:
    Screenshot of Connect Campaign to Cvent Event form
    • Campaign — the Convertr campaign you want to connect.
    • Event — the Cvent event to ingest attendees from.
    • Form — the Convertr form to associate ingested leads with.
    • Publisher — the publisher to associate ingested leads with.
    • Link — the link to associate ingested leads with.
  4. Click Save.

Once saved, the campaign will appear in the list of connected campaigns for the Cvent account.
Screenshot of the connected campaign

Ingesting Cvent Attendee Data as Leads

Once a Convertr campaign is connected to a Cvent event, leads are ingested automatically as soon as the event reaches Completed status in Cvent. No manual action is required.

Each ingested attendee record creates a lead in Convertr with the channel set to Cvent and the following data.

Standard Fields

Label Name
Title title
First Name firstName
Last Name lastName
Email email
Telephone telephone
Mobile Phone mobilePhone
Address Line 1 addressLine1
Address Line 2 addressLine2
Address Line 3 addressLine3
Address Line 4 addressLine4
Postcode postcode

 

In addition to standard attendee fields, three Cvent-specific metadata fields are appended to every ingested lead:

Field Name Description
cvent_attendee_id The unique identifier of the attendee record in Cvent.
cvent_event_id The unique identifier of the Cvent event the attendee registered for.
cvent_event_name The name of the Cvent event as defined in Cvent.

 

This is how ingested standard and metadata Cvent fields appear in the Lead view:
Screenshot of ingested Cvent fields in the Lead view

Custom Contact Fields

If your Cvent account uses custom contact fields, these are automatically ingested and appended to the lead alongside standard fields. See Using Custom Contact Fields in Cvent documentation for details.

Custom contact field values are stored using the field name as defined in Cvent, converted to lowercase. For example, a Cvent custom contact field named "How did you learn about us?" is stored as how did you learn about us?:
Screenshot of the ingested Cvent custom field in the Lead view

Please note:

  • This uses the field Name as defined in Cvent, not the field Code.
  • Even if the name includes spaces and punctuation, it can be mapped in the delivery (integration) jobs the same way as any other lead field. For example, this is how a custom field is mapped in HTTP Integration job configuration:
    Screenshot of the custom Cvent field mapped in HTTP Integration job configuration

Event Question Fields

Event question fields are custom questions added to your Cvent event registration form — such as dietary preferences, session choices, or any other information collected from attendees at registration. See Adding Event Questions in Cvent documentation for details.

Please note: Cvent Lead Ingestion does not currently support ingestion of event question fields (also referred to as registration questions). We are working to add support for this in a future update. If event question fields are important for your use case, please let us know — your feedback helps us prioritise this work.

 

Updating Credentials for a Connected Cvent Account

You can update the name or credentials of a connected Cvent account at any time.

Please note: For security reasons, the Client Secret field is not pre-filled when editing an existing connection. You must re-enter the Client Secret every time you save this form, even if you are only changing the connection name. If the Client Secret is left empty, the connection will not be updated successfully.

To update credentials for a connected Cvent account:

  1. Go to Connected Apps → Cvent.
  2. On the Cvent Accounts page, click Update Credentials next to the account you want to update.
    Screenshot of Update Credentials button
  3. In the Update Cvent Credentials form, update any of the following fields:
    • Name — a new label to help identify the connection.
    • Cvent Host Region — select the region that matches your Cvent account.
    • Client ID — the new Client ID.
    • Client Secret — re-enter the existing Client Secret or provide a new one.
  4. Click Save.

Removing a Connected Cvent Account

To remove a connected Cvent account:

  1. Go to Connected Apps → Cvent.
  2. On the Cvent Accounts page, select the account(s) you want to remove.
  3. Click Delete.
    Screenshot of the Delete button on Cvent Accounts page
  4. Confirm deletion in the confirmation dialog.

Once confirmed, the selected Cvent accounts and their credentials are permanently removed from the platform.

Please note:

  • This also removes all connections between Convertr campaigns and Cvent events for these accounts. Attendee records from completed events will no longer be automatically ingested for the affected campaigns.
  • This action can't be undone.

 

Removing Cvent Lead Ingestion from Campaigns

To remove Cvent Lead Ingestion from a campaign, disconnect the campaign from the relevant Cvent account.

  1. Go to Connected Apps → Cvent.
  2. On the Cvent Accounts page, click Manage Connected Campaigns next to the relevant Cvent account.
  3. From the list of connected campaigns, select the campaign(s) you want to remove.
  4. Click Delete.
    Screenshot of Delete button on Cvent Connected Campaigns page
  5. Confirm deletion in the confirmation dialog.

Once confirmed, attendee records from completed Cvent events will no longer be automatically ingested for the selected campaigns.

Articles in this section

  • Microsoft Teams Webinars Lead Ingestion
  • NeverBounce Email Verification
  • Cvent Lead Ingestion
  • Bombora Intent Enrichment
  • Connections Hub - Explore All Supported Connections in One Place
  • Apollo Contact Enrichment (via Universal Enrichment)
  • Airtable Enrichment (via Universal Enrichment)
  • ZoomInfo Contact Enrichment
  • Madison Logic Intent Enrichment (via Universal Enrichment)

Related articles

  • Microsoft Teams Webinars Lead Ingestion
  • NeverBounce Email Verification
  • Bombora Intent Enrichment
  • Bulk Lead Editing - Publisher User
  • Release Notes - March 2026
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Return to top

Related articles

  • Microsoft Teams Webinars Lead Ingestion
  • NeverBounce Email Verification
  • Bombora Intent Enrichment
  • Bulk Lead Editing - Publisher User
  • Release Notes - March 2026
Convertr