Skip to content

Ads and tracking

Add your own Meta Pixel and Google Analytics 4 IDs to measure your ads. What each tag gets, where it runs, and how buyers choose.

Updated View as Markdown

Add your Meta Pixel and Google Analytics 4 IDs in Settings › Ticket site to measure your ads. Add your privacy policy link first. The tags stay off until you add an ID, and clearing every ID turns them off again.

What we send

Your tags get the same five moments on event, season and run pages.

Moment Google Analytics 4 Meta Pixel With
Page opened page_view PageView the tag’s own
An event, season or run page shown view_item ViewContent the event, season or run key and name
Seats added to the cart add_to_cart AddToCart value, currency, number of seats
Checkout form started begin_checkout InitiateCheckout value, currency, number of seats
Order confirmed purchase Purchase total with fees, currency, a coded order reference

Use purchase / Purchase as your conversion. It is sent once per order. Seats added is sent when seats are held, and again only when more are added. On season and run pages it carries the number of seats and the currency, with no value. On run pages, checkout started carries the number of seats only.

Checkout started is sent the first time the cursor is in the checkout form, before anything is typed. On a wide screen, the event and season checkout opens with the cursor in the email field, so it is sent as the checkout opens. On a phone, it is sent when the buyer first taps into the form. After that the page sends nothing more.

A paid order is reported once, from the page the buyer comes back to after paying, and nothing is sent after it. Reloading that page sends nothing more. A free booking confirmed on the same page is not reported.

The purchase carries an order reference: a code that is the same in Meta and Google Analytics, never the order number.

Where your tags run

  • Your Website pages, and your event, season and run pages, on your free address and your own domain.
  • Never on ticket, account, guest-link or renewal pages.
  • Never on test events, seasons or runs.
  • Pages that open on app.seatlayer.io carry no tags.
  • Buyers in the EU, UK and Switzerland are asked first. Nothing loads until they choose Allow, and Reject sends nothing.
  • Buyers elsewhere are not asked: the tags load with the page.
  • Cookie choices sits in the checkout small print, so a buyer can change their mind.
  • A browser that sends Global Privacy Control or Do Not Track gets no tags and no question.

Check your setup

Test events send nothing, so use a live event. Open it in a private window, choose Allow if you are asked, and add a seat. Watch Test events in Meta Events Manager, or Realtime in Google Analytics.

A free booking never shows a purchase. To see one, pay for one ticket on a live event, then refund it.

On your own website

This setting covers your SeatLayer pages only. Where the widget sits on your own site, your site’s tags and cookie banner apply. Your developer can use the widget’s signals: see Buyer analytics.

Privacy

  • Never a name, email, phone number or ticket code.
  • Your tags stop at the checkout form and after the purchase. So they never see what a buyer types, or the confirmation that follows.
  • Pages that carry your tags never show a buyer’s details. The page a buyer comes back to after paying shows the seats, without the buyer’s email or the ticket holders’ names. On a season page, the account menu of a signed-in buyer leaves out their name and email.
  • Still keep Automatic advanced matching off in Meta Events Manager, and automatically detected user-provided data off in Google Analytics. Both let the vendor’s script read a buyer’s details from a page.
  • Your tags are your own, not SeatLayer subprocessors.
  • Your privacy policy should name Meta and Google.
Navigation

Type to search…

↑↓ navigate↵ selectEsc close