Skip to content

ETK

Event Ticket Summary#

Occurence: Represents individual ticket types ordered as part of an event ticket purchase.

Key Data: The representation of the order. Each ticket type would have it's own row, with its quantity represented in 'Campaign Data 6'. A simple example: A supporter makes an order for two 'Single' tickets and one 'VIP' ticket. In this case there would be two 'ETK' rows generated: One to denote the two Single Tickets, and one for the VIP ticket.

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#

ETK

Campaign ID#

The reference name given to a ticket.

Example: REGULAR

Campaign Status#

No output for this transaction type.

Campaign Data 1#

The database identifier assigned to a fundraising transaction.

Example: 4913255

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#

The total cost of this ticket order.

Campaign Data 5#

The ISO 4217 code of the currency used for this transaction. Currency support is gateway dependent, so be sure to check with your designated payment gateway that the selected currency is supported.

Example: GBP

Campaign Data 6#

The number of tickets in this order. Note: When passing this as input, the associated details for an equal number of attendees should also be submitted.

Example: 2

Campaign Data 7#

The type of ticket order described.

Allowed values:

Single Group

Campaign Data 8#

The discount code applied to the ticket order.

Example: AUG23

Campaign Data 9#

Sale period order.

Occurs as either:

Not applicable for this order.

Y The ticket order was made during a sale or 'early-bird' period.

Campaign Data 10#

A numerical identifier representing a ticket.

Example: 490

Campaign Data 11#

No output for this transaction type.

Campaign Data 12#

No output for this transaction type.

Campaign Data 13#

No output for this transaction type.

Campaign Data 14#

No output for this transaction type.

Campaign Data 15#

No output for this transaction type.

Campaign Data 16#

No output for this transaction type.

Campaign Data 17#

No output for this transaction type.

Campaign Data 18#

No output for this transaction type.

Campaign Data 19#

No output for this transaction type.

Campaign Data 20#

No output for this transaction type.

Campaign Data 21#

No output for this transaction type.

Campaign Data 22#

No output for this transaction type.

Campaign Data 23#

No output for this transaction type.

Campaign Data 24#

No output for this transaction type.

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 three last 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 three last 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 three last 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 three last 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 three last 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 three last 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 three last 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 three last 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 three last 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 three last characters replaced by '...' to indicate that a string has been truncated <= 100 characters

Origin Source#

The name of this origin source as specified by the user. The available Origin Sources can be managed through the Pages > Components > Origin Source section in the dashboard.

Example: ECF

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

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