Facebook Pixel Integration

Most tour and activity operators put real money behind Facebook and Instagram ads — and without conversion tracking, there is no way to know which of those ads actually sell tickets. The Meta Pixel (still widely known as the Facebook Pixel) closes that loop. It tells the ad platform which visitors went on to book, so you can see the true return on every campaign and let Meta's delivery system find more people like the ones who already buy from you.

Because the TicketingHub booking widget lives on your own website, the whole journey — ad click, browsing, checkout — happens on pages you control. When a customer completes a booking, the widget fires a purchase event on your page that your pixel code can pick up, complete with the order value, the currency, and a unique order ID.

What is the Facebook Pixel?

The pixel is a small piece of JavaScript code from Meta that you place on your website. It records the actions visitors take — viewing a page, starting a checkout, completing a purchase — and reports them back to Meta Ads Manager as events. Meta uses those events for three things: measuring which ads lead to sales, building audiences of people who took (or didn't take) a particular action, and optimising ad delivery towards people likely to convert.

Meta renamed it the Meta Pixel in 2022, but the tool itself is unchanged and most operators still call it the Facebook Pixel. One pixel covers both Facebook and Instagram advertising.

How the integration works with TicketingHub

The TicketingHub widget does not fire pixel events automatically — and that is deliberate. It keeps you in control of exactly what is tracked, under which pixel ID, and how it interacts with your cookie-consent setup. Instead, the widget emits a browser event called th:purchase the moment an order is completed.

That event carries the details a conversion tag needs: the currency, the numeric order value, and a unique order ID. A short snippet on your page listens for th:purchase and passes those values to your pixel as a standard Purchase event. Passing the order ID along means a customer refreshing the confirmation page won't be counted as a second sale.

The result in Ads Manager is proper e-commerce tracking: revenue attributed to the specific campaign, ad set, and creative that produced each booking.

Retarget people who looked but didn't book

Most visitors don't buy on their first visit — they check dates, compare prices, and leave. With the pixel installed, Meta knows who opened your booking pages without triggering a purchase event, and you can build a custom audience of exactly those people. A gentle reminder ad a day or two later is one of the cheapest conversions in travel marketing, because the audience has already shown intent.

Find new customers who look like your buyers

Once the pixel has recorded real purchases, Meta can build a lookalike audience: people who resemble your actual ticket buyers in interests, behaviour, and demographics. For a tour operator this is far more precise than targeting by broad interest categories, and it improves over time as more bookings feed the model.

Judge campaigns on revenue, not clicks

Because the purchase event includes the real order value and currency, Ads Manager can report return on ad spend rather than just click-through rates. A campaign that produces fewer clicks but higher-value private-tour bookings will show its worth — something impressions and clicks alone would hide.

Setting it up

Setup is a one-off task that takes a developer a few minutes, and TicketingHub's help centre includes a worked code example:

• Create a pixel in Meta Events Manager and install the base pixel code on the pages that contain your booking widget — directly or via Google Tag Manager.
• Add a short script that listens for the widget's th:purchase event and reads the currency, value, and order ID from the event details.
• Fire a Purchase event to your pixel with those values.
• Use Meta's Test Events tool to run a test booking and confirm the purchase arrives with the right value.

If you don't have a developer to hand, TicketingHub support can point you to the exact snippet for your site.

Frequently asked questions

Does the TicketingHub widget fire pixel events on its own?

No. The widget emits its own th:purchase browser event, and you connect it to your pixel with a small snippet. This keeps tracking under your control and compatible with your consent management.

What data does the purchase event include?

The currency, the order value as a number, and a unique order ID. It does not include payment details — TicketingHub never stores card data, and none of it is exposed to tracking scripts.

Can I run the pixel alongside Google Analytics or Google Ads tags?

Yes. The same th:purchase event can feed as many tools as you like — many operators fire their Meta Pixel, GA4, and Google Ads conversion tags from the one listener, often managed through Google Tag Manager.

Do I need a developer to set this up?

It helps, but the job is copy-and-paste scale: install the pixel base code, add the listener snippet, test. The help-centre article includes ready-made example code.

How accurate is pixel tracking on iPhones?

Browser-side tracking is subject to Meta's platform-wide limitations around Apple's privacy changes — a TicketingHub-powered site behaves the same as any other e-commerce site in this respect. Meta's aggregated reporting compensates for part of the gap.

Does the pixel work with cookie-consent banners?

Yes. Because you install and trigger the pixel yourself, it slots into whatever consent management you already run — the pixel only fires for visitors who have accepted marketing cookies, and the widget's booking events are unaffected either way.

Book a short demo and we'll show you pixel conversion tracking running on a live booking widget.