Skip to main content

Can I use a Meta tracking pixel?

Yes! Enable custom domains to set up your Meta Pixel ID (Formerly Facebook pixel ID).

Written by Rhio

Ticket Tailor works with Meta pixel so you can track how your social media marketing converts into ticket sales.

šŸ’” In order to set up Meta pixel tracking, you first need to enable a custom domain for your box office. Read more on this here: How do I set up a custom domain?


How to find your Pixel ID in Facebook ads manager

  • You can find your Meta Pixel ID (a 16-digit code) from your Facebook for Business events manager.

  • If you want to add Conversions API tracking (CAPI) manually generate an Access Token inside Meta Business Manager.


How to enable Meta pixel tracking

  • Open 'Box office settings' from the top right navigation menu.

  • Click 'Integrations' from the left-hand menu.

  • Under the 'Ads & analytics' tab, click the 'Configure' button next to 'Track your Facebook ads by adding a pixel'.

Screenshot showing the 'Configure' button for 'Track your Facebook ads by adding a pixel', within the 'Ads & analytics' tab of 'Integrations'.
  • In the pop-up window, enter your Facebook ads Pixel ID in the text box provided.

  • Your Facebook ads account will now be connected to your Ticket Tailor dashboard.

How to add Conversions API

  • When setting up your tracking (as above), you can tick the box called 'Enable conversion API' to add Meta Conversions API tracking.

  • Simply paste your conversions API token into the box to complete the setup.

    • Please note: PageView events are currently not tracked with the Conversion API.


What can be tracked per pixel event?

Data

When it fires

Data to expect

Purchase

(For tracking your funnel to a completed order).

After a ticket buyer completes checkout (i.e., payment is successful).

  1. value (the total amount paid, e.g., "50.00")

  2. currency (e.g., "USD", "GBP")

  3. order_id: A unique ID per transaction.

  4. event_ids: Array of Ticket Tailor event IDs related to the purchase. (Your event ID is shown at the end of your event page URL after the /. This is passed it as a list which comes up as [123] when it's one event and [123,456] when it's 2 events).

AddToCart

(For tracking how many people are adding tickets but not checking out).

When a buyer selects tickets and starts the checkout flow.

  1. value: Total basket value (e.g., 50.00)

  2. currency: e.g., USD, GBP

InitiateCheckout

(To track how many people start checkout but don’t complete it).

When the buyer reaches the payment page of checkout.

  1. Browser details for your buyer

  2. Metadata like timestamp, URL, etc.

ViewContent

(For retargeting visitors who showed interest in a specific event).

When someone views a specific event page.

  1. Browser details for your buyer

  2. Metadata like URL, timestamp, possibly referrer, etc.

PageView

(To help retarget all visitors).

Tracked by meta pixel (but not CAPI).

Every time someone opens a page in your checkout flow, Facebook will get a PageView event.

Even if the visitor doesn’t click anything or buy anything — just viewing the page triggers this.

šŸ’” In a typical order flow, a buyer might go through several pages like:

  1. Event page (select tickets)

  2. Checkout page (enter attendee info/payment details)

  3. Confirmation page (thank-you page after purchase)

Each page loads separately, and the Facebook Pixel fires a PageView each time. Therefore you are likely to have higher event page views than orders.

  1. Browser details for your buyer

  2. Metadata like timestamp, URL, etc.

Did this answer your question?