See below for the different tracking events via the Line-Up Purchase Flow
KEY TERMS & TIPS:
How can Line-Up help with our tracking?
We provide a universal tracking layer via our purchase flow. See the different tracking events below.
If it's specifically tracking and analytics you would like help with, then we would suggest hiring a digital marketing agency or freelancer who can implement marketing tags for you. See our recommendations for digital partners here.
For more information regarding specific marketing tags, go here.
What is the universal tracking layer?
Our tracking layer pushes events into Google Tag Manager which allows you to implement tags for platforms such as Meta, TikTok, Twitter, etc. You can then pick up and listen to those events for your tracking.
What do I need in order to track from the Line-Up purchase flow?
You will need to set up Google Tag Manager in order to track the below events. Once you have it installed, please send us your GTM ID (e.g. GTM-1234TLE) and we can add it to your checkout flow.
The conversion tracker then needs to be set up on GTM to fire with the correct conversions.
We also recommend using Preview Mode on GTM, which tells you all the actions/Tags that are getting fired in Tag Manager and what is available in the Data Layer. All this data is available for you to use in any pixels.
For more info on Google Tag Manager, see here.
---
TRACKING EVENTS:
1. view_item
A view_item event is triggered whenever a user views an item’s details screen. This contains information of the item that has been viewed.
Example payload:
event: "view_item",
purchase_flow: "New Purchase",
ecommerce: {
currency: {{ TRANSACTION.CURRENCY }},
items: [
{
item_id: {{EVENT_ID}},
item_name: {{EVENT_NAME}},
item_category: {{NEXT_PERFORMANCE_DATE}},
item_category4: "browser",
item_list_name: "calendar",
item_variant: "",
quantity: {{QUANTITY}}
}
]
When it fires: when a user looks at the calendar for a specific event:
2. add_to_cart
An add_to_cart event is triggered when an item is added the basket. This contains information about the item that has been added to the cart. The quantity value will be the quantity that has been added.
Example payload:
event: "add_to_cart",
purchase_flow: "New Purchase",
ecommerce: {
currency: {{ TRANSACTION.CURRENCY }},
value: {{ ticket.NET }}
items: [
{
item_id: "",
item_name: {{EVENT_NAME}},
currency: "GBP",
item_category: {{ ticket.PERFORMANCE_START_DATE }}/{{ ticket.PERFORMANCE_START_TIME }}
item_category4: "browser",
item_category5: "",
price: {{ ticket.NET }},
quantity: {{QUANTITY}}
}
]
When it fires - Reserved Seating: when a user adds items to their cart/bag by clicking on any coloured dots:
When it fires - General Admission: when a user adds items to their cart/bag by clicking on the + button next to a ticket:
3. add_to_cart - upsell items
An add_to_cart event is also triggered when an upsell item is added the basket. This contains information about the item that has been added to the cart. The quantity value will be the quantity that has been added.
Example payload:
event: "add_to_cart",
purchase_flow: "New Purchase",
ecommerce: {
currency: {{ TRANSACTION.CURRENCY }},
value: {{ product.NET }}
items: [
{
item_id: "",
item_name: {{PRODUCT_NAME}},
currency: "GBP",
item_category: {{ ticket.PERFORMANCE_START_DATE }}/{{ ticket.PERFORMANCE_START_TIME }}
item_category4: "browser",
item_category5: "",
price: {{ product.NET }},
quantity: {{QUANTITY}}
}
]
When it fires: when a user adds items to their cart/bag by clicking the + button next to a product item:
4. remove_from_cart
A remove_from_cart event is triggered when when a user removes items from a cart. This contains information about the items that have been removed. The quantity value will be the quantity that has been removed.
Example payload:
event: "remove_from_cart",
purchase_flow: "New Purchase",
ecommerce: {
currency: {{ TRANSACTION.CURRENCY }},
value: {{ ticket.NET }},
items: [
{
item_id: "",
item_name: {{EVENT_NAME}},
currency: {{ TRANSACTION.CURRENCY }},
item_category: {{ ticket.PERFORMANCE_START_DATE }}/{{ ticket.PERFORMANCE_START_TIME }},
item_category4: "browser",
item_category5: "",
price: {{ ticket.NET }},
quantity: {{QUANTITY}}
}
]
When it fires - Reserved Seating: when a user removes an item from the cart either completely or individually:
When it fires - General Admission: when a user removes an item from the cart either individually by clicking the - button next a ticket or 'Remove' on the basket line, or completely by clicking 'Clear Basket:
5. begin_checkout
A begin_checkout event is triggered in the first step of a checkout process. This contains information about the items in the bag.
Example payload:
event: "begin_checkout",
purchase_flow: "New Purchase",
ecommerce: {
currency: {{ TRANSACTION.CURRENCY }},
value: {{ ticket.NET }},
items: [
{
item_id: ""
item_name: {{EVENT_NAME}}
currency: {{ TRANSACTION.CURRENCY }},
item_category: {{ ticket.PERFORMANCE_START_DATE }}/{{ ticket.PERFORMANCE_START_TIME }}
item_category4: "browser",
item_category5: "Musical",
price: {{ ticket.NET }},
quantity: {{QUANTITY}}
}
]
}
});
When it fires: when a user clicks on the “Book Now” button on the cart/basket page, that begins the checkout:
6. add_payment_info
An add_payment_info event is triggered when a user submits their payment information. This contains the items array and their selected payment information (e.g Credit/Debit Card, Klarna, Gift Card or PayPal etc).
Example payload:
event: "add_payment_info",
purchase_flow: "New Purchase",
ecommerce: {
currency: {{ TRANSACTION.CURRENCY }},
value: {{ ticket.NET }},
payment_type: {{ payment.TYPE }},
items: [
{
item_id: "",
item_name: {{EVENT_NAME}},
currency: {{ TRANSACTION.CURRENCY }},
item_category: {{ ticket.PERFORMANCE_START_DATE }}/{{ ticket.PERFORMANCE_START_TIME }},
item_category4: "browser",
item_category5: "Musical",
price: {{ ticket.NET }},
quantity: {{QUANTITY}}
}
]
}
});
When it fires: when a user is in the checkout and clicks on the button after they have chosen their preferred payment method:
7. purchase
A purchase event is triggered when a payment is submitted. This contains the items array and all relevant information related to the purchase.
Example payload:
event: "purchase",
purchase_flow: "New Purchase"
ecommerce: {
transaction_id: "",
affiliation: "Marvel",
value: {{ ticket.NET }},
currency: {{ TRANSACTION.CURRENCY }},
tax: {{ ticket.TAX }},
shipping: {{ payment.GROSS }},
items: [
{
item_id: "",
item_name: {{EVENT_NAME}},
currency: {{ TRANSACTION.CURRENCY }},
item_variant: {{ ticket.VARIANT_NAME }},
item_category: {{ ticket.PERFORMANCE_START_DATE }}/{{ ticket.PERFORMANCE_START_TIME }},
item_category2: {{ ticket.SEAT_GROUP_AREA }},
item_category3: {{ ticket.BAND_NAME }},
item_category4: "browser",
item_category5: "Musical",
price: {{ ticket.NET }},
quantity: {{QUANTITY}}
},
{
item_id: "",
item_name: {{ product.TITLE }},
currency: {{ TRANSACTION.CURRENCY }},
item_category2: {{ ticket.SEAT_GROUP_AREA }},
item_category3: {{ ticket.BAND_NAME }},
item_category4: "browser",
item_category5: "", //labelled Up-sell when an add on item to a show
price: {{ ticket.NET }},
quantity: {{QUANTITY}}
}]
}
});
When it fires: when a user is in the final stage of checkout and has entered their payment details, clicks on the "Confirm & Pay" button or equivalent and the Payment is successfully completed:
Comments
0 comments
Please sign in to leave a comment.