ETA
Event Ticket Attendee#
Occurence: An attendee has been linked to a ticket order.
Key Data: The individual attendee is represented by the details collected as part of the page processing. There will be one row for each attendee, which can be linked back to the purchaser.
Export file columns#
Account ID#
Identifies the subaccount this item belongs to
Example: 94
Supporter ID#
The unique numerical database identifier for a supporter.
Example: 212200
Default: 0
Supporter Email#
The primary email address of a supporter, which will typically be used as the basis for identifying a unique supporter to which any transactions will be associated.
<= 500 characters
Example: otto.nv@example.com
Date Created#
The date a supporter was created. [ISO 8601 format date]
Example: 2024-12-01
Date Modified#
The date a supporter was last modified. [ISO 8601 format date]
Example: 2024-12-01
Campaign Number#
A unique database identifier used to refer to a page, particularly in transactional data. Where records in transactional data originate outside of a page structure, for example as a result of dashboard actions or imports, this will hold a value of 0. Default: 0
Example: 10122
Campaign Type#
ETA
Campaign ID#
The reference name given to a ticket.
Example: REGULAR
Campaign Status#
The current status of this attendee
Occurs as either:
Attending The attendee has been issued a ticket for this event.
Attended The attendee was marked as having arrived at the event.
Refunded The attendee's ticket has been refunded by the organiser.
Campaign Data 1#
The transaction identifier as provided by a payment gateway. If the current transaction is a refund, then this identifier points back to the transaction being refunded. The specific formatting of the identifier will be dependent on the gateway.
Example: ND8390T284740397745210972__cus_O20rrZCTq8iTpw__ch_3NFwqEHh8CrK50QS1uUEXjck
Campaign Data 2#
The internal reference name given to a page.
<= 160 characters
Campaign Data 3#
The transaction identifier as provided by a payment gateway. If the current transaction is a refund, then this identifier points back to the transaction being refunded. The specific formatting of the identifier will be dependent on the gateway.
Example: ND8390T284740397745210972__cus_O20rrZCTq8iTpw__ch_3NFwqEHh8CrK50QS1uUEXjck
Campaign Data 4#
A numerical identifier representing a ticket.
Example: 490
Campaign Data 5#
An attendee's title.
Example: Dr
Campaign Data 6#
An attendee's first name.
Example: Otto
Campaign Data 7#
An attendee's last name.
Example: Normalverbraucher
Campaign Data 8#
An attendee's email address.
Example: otto.nv@example.com
Campaign Data 9#
An attendee's first line of address.
Campaign Data 10#
An attendee's second line of address.
Campaign Data 11#
An attendee's city.
Campaign Data 12#
An attendee's region.
Campaign Data 13#
An attendee's ZIP or postcode.
Campaign Data 14#
An attendee's country.
Campaign Data 15#
An attendee's phone number.
Campaign Data 16#
Notes on an attendee's dietary preferences, if any.
Campaign Data 17#
Notes on an attendee's mobility requirements, if any.
Campaign Data 18#
Custom 1: A client defined field used to store additional data. The content of this field will be automatically truncated if maximum length is exceeded, with the three last characters replaced by ... to indicate that the string has been truncated
<= 100 characters
Campaign Data 19#
Custom 2: A client defined field used to store additional data. The content of this field will be automatically truncated if maximum length is exceeded, with the three last characters replaced by ... to indicate that the string has been truncated
<= 100 characters
Campaign Data 20#
Custom 3: A client defined field used to store additional data. The content of this field will be automatically truncated if maximum length is exceeded, with the three last characters replaced by ... to indicate that the string has been truncated
<= 100 characters
Campaign Data 21#
Custom 4: A client defined field used to store additional data. The content of this field will be automatically truncated if maximum length is exceeded, with the three last characters replaced by ... to indicate that the string has been truncated
<= 100 characters
Campaign Data 22#
The sequency number for this attendee.
Campaign Data 23#
Custom 5: A client defined field used to store additional data. The content of this field will be automatically truncated if maximum length is exceeded, with the three last characters replaced by ... to indicate that the string has been truncated
<= 100 characters
Campaign Data 24#
Custom 6: A client defined field used to store additional data. The content of this field will be automatically truncated if maximum length is exceeded, with the three last characters replaced by ... to indicate that the string has been truncated
<= 100 characters
Campaign Data 25#
An identifier for an event occurence.
Campaign Data 26#
The start date and time of this occurence.
Example: 2021-05-01T12:00:00
Campaign Data 27#
No output for this transaction type.
Campaign Data 28#
No output for this transaction type.
Campaign Data 29#
No output for this transaction type.
Campaign Data 30#
No output for this transaction type.
Campaign Data 31#
No output for this transaction type.
Campaign Data 32#
No output for this transaction type.
Campaign Data 33#
No output for this transaction type.
Campaign Data 34#
No output for this transaction type.
Campaign Data 35#
No output for this transaction type.
External Reference 1#
When used outside of API page processing, this field may be populated using the URL parameters utm_source or by the generic parameter en_txn1. Content will be automatically truncated if the maximum length is exceeded, and the last three characters replaced by '...' to indicate that a string has been truncated.
<= 100 characters
External Reference 2#
When used outside of API page processing, this field may be populated using the URL parameters utm_medium or by the generic parameter en_txn2. Content will be automatically truncated if the maximum length is exceeded, and the last three characters replaced by '...' to indicate that a string has been truncated.
<= 100 characters
External Reference 3#
When used outside of API page processing, this field may be populated using the URL parameters utm_campaign or by the generic parameter en_txn3. Note: Content will be automatically truncated if the maximum length is exceeded, and the last three characters replaced by '...' to indicate that a string has been truncated.
<= 100 characters
External Reference 4#
When used outside of API page processing, this field may be populated using the URL parameters utm_content or by the generic parameter en_txn4. Note: Content will be automatically truncated if the maximum length is exceeded, and the last three characters replaced by '...' to indicate that a string has been truncated.
<= 100 characters
External Reference 5#
When used outside of API page processing, this field may be populated using the URL parameters utm_term or by the generic parameter en_txn5. Note: Content will be automatically truncated if the maximum length is exceeded, and the last three characters replaced by '...' to indicate that a string has been truncated.
<= 100 characters
External Reference 6#
When used outside of API page processing, this field may also be populated by a user-defined page property [Page > Admin > Campaign References], or by the url query parameter en_txn6. When added as a page parameter, the field is referred to as Campaign Reference 1 in the dashboard settings.
If a value is presented in both places, the url query parameter will take precedence. Note: Content will be automatically truncated if the maximum length is exceeded, and the last three characters replaced by '...' to indicate that a string has been truncated.
<= 100 characters
External Reference 7#
When used outside of API page processing, this field may also be populated by a user-defined page property [Page > Admin > Campaign References], or by the url query parameter en_txn7. When added as a page parameter, the field is referred to as Campaign Reference 2 in the dashboard settings. If a value is presented in both places, the url query parameter will take precedence. Note: Content will be automatically truncated if the maximum length is exceeded, and the last three characters replaced by '...' to indicate that a string has been truncated.
<= 100 characters
External Reference 8#
When used outside of API page processing, this field may also be populated by a user-defined page property [Page > Admin > Campaign References], or by the url query parameter en_txn8. When added as a page parameter, the field is referred to as Campaign Reference 3 in the dashboard settings. If a value is presented in both places, the url query parameter will take precedence. Note: Content will be automatically truncated if the maximum length is exceeded, and the last three characters replaced by '...' to indicate that a string has been truncated.
<= 100 characters
External Reference 9#
When used outside of API page processing, this field may also be populated by a user-defined page property [Page > Admin > Campaign References], or by the url query parameter en_txn9. When added as a page parameter, the field is referred to as Campaign Reference 4 in the dashboard settings. If a value is presented in both places, the url query parameter will take precedence. Note: Content will be automatically truncated if the maximum length is exceeded, and the last three characters replaced by '...' to indicate that a string has been truncated.
<= 100 characters
External Reference 10#
When used outside of API page processing, this field may also be populated by a user-defined page property [Page > Admin > Campaign References], or by the url query parameter en_txn10. When added as a page parameter, the field is referred to as Campaign Reference 5 in the dashboard settings. If a value is presented in both places, the url query parameter will take precedence. Note: Content will be automatically truncated if the maximum length is exceeded, and the last three characters replaced by '...' to indicate that a string has been truncated.
<= 100 characters
Email Address#
The primary email address of a supporter, which will typically be used as the basis for identifying a unique supporter to which any transactions will be associated.
<= 500 characters
Example: otto.nv@example.com
Title#
A supporter's title to be used in salutations
<= 50 characters
Example: Dr
First Name#
A supporter's first name
<= 500 characters
Example: Otto
Middle Name#
A supporter's middle name
<= 500 characters
Example: Niemand
Last Name#
A supporter's last name
<= 500 characters
Example: Normalverbraucher
Address 1#
The first line of the supporter's address
<= 1000 characters
Address 2#
The second line of the supporter's address
<= 1000 characters
Address 3#
The third line of the supporter's address
<= 1000 characters
City#
The city in a supporter's address
<= 500 characters
Example: Musterstadt
Region#
The supporter's region, state, county, province or similar
<= 500 characters
Example: Musterregion
Country#
The supporter's country
<= 500 characters
Example: DE
Phone Number#
The primary phone number for a supporter
<= 200 characters
Example: +49 4066969123