Skip to main content
Sign in

Mapping an Event Form to an Event Source in the Demand Acceleration Platform

Ashley.Jones
  • Updated

Relevant to: Demand Acceleration Platform | Event Lead Management

This Help Center section is specific to using Event Lead Management with the Demand Acceleration Platform.
For a comprehensive guide to using the Event Lead Management solution, see Event Lead Management Guides. 

Map Event form fields in the Event Lead Management system to those in an Event Source. This is the final step in enabling data flow between the two platforms and determines where data will be sent in the Demand Acceleration Platform.

This will be completed by your Events Power User(s) in the Event Lead Management system > Event > Setup Integrations.

For an overview of the entire process using both Integrate systems, see Event Lead Management with the Demand Acceleration Platform.

You will need to have 1) built an Event Source in the Demand Acceleration Platform and have finalized the form fields, and 2) connected the Event Lead Management system with the Demand Acceleration Platform - before mapping Event fields.
Building an Event Source

Connecting the Event Lead Management system with the Demand Acceleration Platform

 

 

Mapping Event form fields to an Event Source

This step needs to be repeated for each Event that will create leads for the Demand Acceleration Platform.
Duplicating an existing Event that already has an integration will duplicate the setup.
1. In the Event Lead Management dashboard, click on the Event where data will be collected (before being sent to the Demand Acceleration Platform). 

elm-integrations-dap-05.png

 

2. Select Setup integrations. 

elm-integrations-dap-06.png

 

3. Select Integrate and click on Add.

elm-integrations-dap-07.png

 

4. Click on the Integrate Source dropdown menu and select the Event Source where lead data should be sent. 

elm-integrations-dap-08.png

If you do not see your Event Source on this list, confirm that 1) you have completed the step Building an Event Source within the Demand Acceleration Platform and 2) the Start Date of your Event Source has been reached.

 

5. You will now see the Source Mapping page, where there are two columns used to match fields in the Event Lead Management system with the Source fields in the Demand Acceleration Platform.

The columns are:

(Form Question / Transcribed) Responses column

  • This column represents the Event fields in the Event Lead Management system, the incoming data.
  • The name displayed here corresponds to the Event form fields.
  • The responses column is grouped as:
    Responses column groups Description
    Form Question Responses

    A list of fields that are in the form.

    • This data here can be from the form itself or data retrieved from a badge scan if set-up for the Event.
    Transcribed Responses

    Data that might be returned once a business card has been transcribed.

    • This availability of this data is dependent on what is printed on the business card and the legibility of the photo scan.
    Other Data

    Includes data and metadata that is automatically generated (eg. app user name, event name, start date, device ID).

Matches with... column

  • Represents the Source fields in the Demand Acceleration Platform, which you wish to send the Event data into.
  • The name displayed here corresponds to the Field Name section on the Fields tab.

 

Map the fields by methodically working down the page. Choose the corresponding Event Response and Source value by using the drop-down menus to make your selection.

elm-integrations-dap-09.png

For example:

Responses
(Event Lead Management field)		 posts to

Matches with...
(Campaign/Source field)
First Name posts to

First Name [Text]
Last Name posts to

Last Name [Text]
Email posts to

Email Address [Email]
  • Fields left as Unassigned will not send any data to the Demand Acceleration Platform. 
    • Fields with the data type Label should remain unassigned as they represent headers on the form.
    • If your field contains a Badge Scan field, this is usually left unassigned. This field is typically a string of random characters and is of little use outside of the event's badging system. 

A note on Match and Mismatch labels

The label displayed next to each mapped field indicates whether the mapped field data types are the same. For example, a string field mapped to a string field is the same data type and will display a Match label.

Different data types that are mapped together will display a Mismatch label. This will not prevent you from saving the integration setup because certain data types are compatible despite them not being the same - for example, a string field can receive data from a number field.

Some field types are not compatible and will cause leads to be rejected in the Demand Acceleration Platform, for example a datetime field cannot receive data from a boolean (ie. 0 or 1) field.

The Mismatch label simply serves as a prompt to double check that the mapping is accurate. If the fields are confirmed as compatible, the Mismatch can remain in place.

Click on Save changes once finished.

 

Mapping multiple Event fields to one Source field

If mapping multiple form fields (not including business card transcription field), the values will be concatenated and sent to the DAP as one comma-separated value.

Mapping field example:

Event form fields
[in the Event Lead Management system]		 Maps to

Source field
[in the Demand Acceleration Platform]

Form question

Area Code
 Maps to 
Phone number

Form question

Phone number
 Maps to


Resulting data flow example:

Event form fields
[in the Event Lead Management system]		 Value sent >

Source field
[in the Demand Acceleration Platform]

Value received
Area Code 
+44
 >

Phone number

 
+44,01234567890
Phone number 
01234567890



Mapping multiple data collection methods

If you are using multiple data collection methods in the Event (eg. business card transcription, badge scanning and manual question response) you can map all of them to one field in the Demand Acceleration Platform, providing the data types are compatible. See A note on Match and Mismatch labels.

For example:

Event form fields
[in the Event Lead Management system]		 Maps to

Source field
[in the Demand Acceleration Platform]

Business card transcribed data

Company Name
 Maps to 
Company

Form question and badge scan response

Company
 Maps to
When using business card transcription as a collection method, leads will be sent to the Demand Acceleration Platform only once the transcription data has been received (not when the lead is first submitted and synced to the dashboard).
  • If your Event form contains a business card transcription field and form field(s) that collect the same value(s) - and they are not hidden by logic - you need to define which should take priority when sending to the Demand Acceleration Platform.
    • For example, if a business card transcription and a form field both contain an Email address value - and they have both been mapped to the same field in the Demand Acceleration Platform, you need to state which should be the output value.
    • This can be determined by the Which data source should take priority? option.

 

 

Testing and confirming successful lead flow in all systems

1. In the Event Lead Management system: register a test lead in the mobile app or a web form and confirm if the data is visible in the Logging page.

  • If the lead has not been received, check that the device is online and has synced.

2. In the Demand Acceleration Platform: navigate to your event Source and check that the lead has been accepted.

3. In your Marketing Automation or CRM system: check that the test lead has been received and routed successfully.

It's advisable to monitor inbound leads regularly to ensure all valid leads are passing through all systems as planned.

Your integration is now set up and you are ready to collect event leads in the Integrate Events mobile app.

These articles will help ensure you and your team are prepared:

Your Pre-Event Checklist

Capturing Leads at Events with the Mobile App

Once leads are being collected in the Integrate Events mobile app, it is recommended to monitor your lead flow to ensure all valid leads are successfully passing through all systems.
For more information, see Managing Event Lead Flow.

 

 

Frequently Asked Questions

How fast will my contacts appear in the Demand Acceleration Platform?
Usually a few seconds after they appear in the Event Lead Management dashboard.
 
How does this feature work when my devices are offline?
Contacts are queued to be added to Integrate as soon as the data synchronizes to the dashboard.
  
Can I import the data that I collected before I set up the integration on an event?
You must setup the integration prior to collecting data. Data collected before setting up the integration must be manually exported and imported using CSV or Excel.
 
How do I disable or remove an integration from an event?
From the Integrations screen for the event, under the Integrate row, select Remove Integration.
If a lead is affected by an error, can I resend the lead to the Demand Acceleration Platform after I've corrected the issue?
Yes, you can resend affected leads to the Demand Acceleration Platform from within the dashboard. See Help Centre article, Resend leads to integrated platforms.

 

Recommended Reading

 

For more help, get in touch with our Support Team or your Customer Success Manager.

Related articles