Even before registrants become attendees, you can export their information from Accelevents to Marketo and track the status of their request directly in Marketo.
How Does it Work?
When someone submits a registration request through the Attendee Approval workflow, Accelevents immediately sends their information to Marketo — even before they’re approved.
As soon as the form is submitted, a new record is created in Marketo. If the email address already exists, the existing record is updated instead. The record will also be added as a member in the Marketo program event and will have a "Pending" status, which will continue to update in Marketo automatically as it changes in Accelevents.
In addition to their name and email address, other details from the registration form — like job title, organization, and any custom questions — can be synced.
Before You Begin
Before you begin make sure you've already done the following:
✅ The Accelevents and Marketo integration is connected and working
✅ The attendee approval feature is enabled for the ticket types
✅ Custom properties for the fields you want to map are created in Marketo
Enable the Registration Approval Mapping
Go to Settings > Integrations
Click Configure under Marketo
Enable the toggle for Registration Approval
Map the Fields
By default, the potential attendee's Email, First Name, and Last Name are the fields that will be exported from Accelevents to Marketo. If you want other order form answers to be included in the data transfer, you can map those fields in the Registration Approval Mapping menu and the Contact Field Mapping menu (first part of the configure menu).
Map the fields in the registration approval mapping - You'll need to map the registration approval fields so the data will be captured in Marketo when the request is submitted, even before the request is approved. For example, if a registration request includes a job title and organization, this data will populate into the matching Marketo record even before the request is approved. There is no update policy field here, so the default is "always update" unless you also map the field in the contact field mapping section, then the update policy in that section will also apply in this section.
Map the fields in the contact field mapping - You'll need to map the contact fields if you have tickets for regular registrations (not through the approval process). If everyone will go through the approval workflow, you may not need to map these fields, unless you have a specific Update Policy for the field. If it's not mapped in the contact field mapping section and it's mapped in the registration approval mapping, the update policy that would apply is "always update."
Map the auto-generated registration approval fields (optional) - aside from order form fields, you can also map a couple of fields from the approval workflow in the Registration Approval Mapping menu.
Registration Request Id - this is the numeric identifier for the request (must be mapped to an Integer Marketo field)
Registration Request Status - this will update depending on the request status (Pending, Waitlisted, Denied, Approved and Registered (when approved and ticket is assigned). You don't really need to map this since you'll see the updates in the Marketo Status.
Registration Approval Mapping | Contact Mapping |
| 
|
Important Note: We can only map to text / string, number/integer, phone number, date picker, and dropdown / picklist Marketo fields. It will not work if the Marketo field is a radio button, checkbox, etc.
Test If Marketo Records Will be Created
Do a test registration request from the event landing page, try it with new and existing Marketo records. After submitting your request, check in the Marketo program event if a new record is created or updated. Change the status of the request to see if it will also update in Marketo.
