You can add third-party tracking codes to your event. See a section below that's appropriate for your analytics tool.
Google Analytics
We have special integration with Google Analytics.
Find your event, and go to Manage Event > Tag Manager > Properties find the field labelled "Google Analytics."
Enter your Property ID and click Save.
Tags & Pixels
This section is for social media pixels such as Facebook Pixel, Snapchat Pixel or any other third-party tracking code. On each event, there are a few places for tracking codes;
General Page View Tags/Pixels
Adds pixel to:
- Event Page
- All order pages (Items, donations, seat selection, etc.)
Does not add pixel to:
- Receipt/Confirmation page
- Payment/Details page (for PCI security pixel can never be added to the payment page)
Conversion Tags/Pixels
Adds pixel to:
- Receipt/Confirmation page only
Custom Landing Page
Contact us with the landing page URL and tracking code.
Dynamic Order Variables
iTICKETS provides a full set of dynamic order variables that you can use to capture the conversion details you need. These variables can be inserted into your tags and pixels so they automatically populate with real order data at runtime.
Default Variables:
- {{ order.subtotal }} – Items total only (excludes fees)
- {{ order.currency.iso }} – Currency code (e.g., USD)
- {{ order.id }} – Order number
Optional Variables:
- {{ order.total }} – Total order amount (items + fees)
- {{ order.couponCode }} – Coupon code (if applied)
An array of all purchased items can be captured using one of the following:
- {{ order.itemsAw }} — for Google Ads
- {{ order.itemsGa4 }} — for Google Analytics
Items Array Example:
items: [{
id: ‘ticket_ID’, // Ticket ID
name: ‘ticket_name’, // Ticket name
category: ‘Ticket_Type’,// e.g. VIP, GA
quantity: ‘quantity’, // Quantity purchased
price: ‘face_value’, // Item price
coupon: ‘coupon_used’ // Shows only for manual promotions
}]
Customer Information:
Customer data can also be passed, but since it is considered PII (personally identifiable information), it must be encrypted. To encrypt, add _sha256 to the end of the variable name (e.g., {{ order.address.billing.email_sha256 }}). Most pixels and tags will only accept the encrypted version.
Available customer variables:
- {{ order.address.billing.fname }}
- {{ order.address.billing.lname }}
- {{ order.address.billing.address }}
- {{ order.address.billing.city }}
- {{ order.address.billing.state }}
- {{ order.address.billing.zip }}
- {{ order.address.shipping.phone }}
- {{ order.address.shipping.email }}