1. Customer setup responsibilities
- Follow the steps below in your Cvent account:
- Whitelist IP addresses in Cvent
- IP addresses can be found in an email sent to your Technical Point of Contact
- Ensure APIs are whitelisted on the correct API username
- Ensure you have granted DoubleDutch API access
- Enter the following information when setting up your integration in the DoubleDutch Studio:
- Account ID (Cvent AccountID)
- API Username (This is not your personal username. This will need to be requested from Cvent)
- API Password (This is not your personal password. This will need to be requested from Cvent)
- eCode (NOT Event Code. See below for instructions on how to find your eCode)
- Click into your event within your Cvent account
- On the overview screen you have a number of difference display boxes. In the display box that says “pre-launch summary” or “event snapshot” (depends on if your event is live or not) click the ‘my settings’ link the right corner
- Pull over the ‘eCode’ into the selected box and click save
2. What content is included
- The following content can be synced from Cvent to DoubleDutch. DoubleDutch requires certain content fields for a Cvent integration, all other fields are considered optional.
Agenda
|
DoubleDutch Field |
Cvent Endpoint |
Cvent Field Name |
|
Name (required) |
Event |
ProductName |
|
Start Time (required) |
StartTime |
|
|
End Time (required) |
EndTime |
|
|
Description |
ProductDescription |
|
|
Location |
ProductCode OR custom field “Room” |
|
|
Session Tracks |
SessionCategoryName OR custom field “Tracks” |
|
|
Unique ID (required) |
ProductID |
Speakers
|
DoubleDutch Field |
Cvent Endpoint |
Cvent Node |
|
First Name (required) |
Speaker |
FirstName |
|
Last Name (required) |
LastName |
|
|
Title |
Title |
|
|
Company |
Company |
|
|
Description |
Biography |
|
|
Image URL |
ProfileImageURL |
|
|
Twitter Handle |
TwitterURL |
|
|
Facebook URL |
FacebookURL |
|
|
Linkedin URL |
LinkedinURL |
|
|
Session IDs |
AssignedSessions.SessionID |
|
|
Unique Speaker IDs |
SpeakerID |
Attendees
|
DoubleDutch Field |
Cvent Endpoint |
Cvent Node |
|
First Name (required) |
Registration |
FirstName |
|
Last Name (required) |
LastName |
|
|
Email Address (required) |
EmailAddress |
|
|
Title |
Title |
|
|
Company |
Company |
|
|
Attendee Groups |
RegistrationType |
|
|
Phone Number |
WorkPhone |
|
|
Address |
WorkAddress1 |
|
|
Address (ext) |
WorkAddress2 |
|
|
City |
WorkCity |
|
|
State/Province |
WorkState |
|
|
Postal Code |
WorkPostalCode |
|
|
Country |
WorkCountry |
|
|
Personal Agenda (Session IDs) |
OrderDetail |
|
|
Unique ID |
ConfirmationNumber |
3. Configuration Options
- Password Options
- Last 6 Digits of Confirmation Code:
- If you want attendee passwords to be the last 6 digits of their confirmation code, enable (check) the "UseConfNumberAsPassword" checkbox.
- Default:
- You can set a global password for all attendees by entering a value in this field. Must be 6 characters or more and is case sensitive (i.e. dd2016).
- Random:
- If field is left blank, a random 6 digit character password will be assigned to unique to each attendee. (NOTE: If this option is chosen, the DoubleDutch Welcome Email must be used to provide each attendee with their password)
- Password Settings
- Enable <storeEncryptedPassword> to include password in DoubleDutch Welcome email (generated via the Studio)
- Session Locations
- How to setup session location info (default: custom field “Room” or product code)
- How to setup session tracks (Default: custom field “Tracks” or “Session Category Name” if “Tracks” is not available)
4. What You Should Know
- Cvent may charge an additional fee to allow client to integrate with DoubleDutch
- Any integration request with Cvent that varies from the documentation here is subject to additional fees and restrictions
Comments
0 comments
Please sign in to leave a comment.