EventsFrame fields synced to integrations
Generally speaking, all custom fields need to be created in your email marketing platform before collecting attendee data (Drip automatically syncs custom fields).
The below table summarises the fields you need to create in your email marketing platform: (please see individual help documents for further info)
Name | Description | Example values |
Email is ALWAYS synchronised, attendees without email are skipped | john@example.com | |
coupon_code | Coupon code used on the ticket order, uppercase | VIP_CODE |
event_id | ID of the EventsFrame Event | qPjmJdRy8 |
event_name | Name of the EventsFrame Event | The Summer Workshop |
order_id | ID of the EventsFrame Order | tBhqvahna |
attendee_id | ID of the EventsFrame Attendee | |
language | ISO code of the primary language from user's browser, lowercase | en, cs, it, es |
orderer | Is this attendee the one who made the order? | yes, no |
payment_method | The payment method used to purchase or order tickets | braintree, braintree-paypal, paypal, stripe, transfer |
tickets | All Attendee's Tickets separated by comma | "Full Conference ticket, Workshop, After Party" |
first_name | First name of the attendee if names are supported | John |
last_name | Last name of the attendee if names are supported | Doe |
full_name | Full name of the attendee if names are supported | John Doe |
checked_in | Whether the attendee was checked in to the event | yes, no |
currency | Currency of transaction | USD |
price | Order value net of VAT/sales tax | 100 |
full_price | Order value inclusive of VAT/sales tax | 102 |
vat_rate | % Rate of VT/sales tax | 0.02 |
vat_tax | Amount of VAT added | 2 |