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, indicating that the transaction outcome should not be associated with a particular page. Default: 0

Example: 10122

Campaign Type#

ETAThe Campaign Type is used to determine the layout of the data columns in the output stream.

Campaign ID#

The reference name given to a ticket.

Example: REGULAR

Campaign Date#

The recorded date [YYYY-MM-DD] of this transaction. If left blank during transactional import, the service will apply the import date. The reference timezone for this service is US/Eastern.

Example: 2024-12-01

Campaign Time#

The recorded time [HH:MM:SS] of this transaction. The reference timezone for this service is US/Eastern.

Example: 13:53:02 Default: 00:00:00

Campaign Status#

The current status of this attendee

Occurs as either:

Attending Attended Refunded

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.