Smeetz sends your booking events to your Meta pixel twice: once from your visitor’s browser (your Meta pixel, on your website) and once from Smeetz’s servers (Meta Conversions API). Both copies carry the same event ID, so Meta counts each action once while getting the most complete data. This guide shows how to set it up, what Smeetz sends, and how to check it with Meta’s Test events.
How it works
Your visitor opens the Smeetz booking widget on your website.
At each step of the booking, Smeetz asks your website’s Meta pixel to send the event (browser event).
At the same moment, Smeetz’s servers send the same event to Meta through the Conversions API (server event).
Meta sees the same event name and event ID twice, keeps one and marks the other as deduplicated.
Server events still reach Meta when the browser event is lost, for example when the visitor closes the page right after paying. That’s why both are needed.
How Smeetz sends booking events to Meta
Before you start
You need:
Access to Meta Events Manager for your business.
A Meta pixel (called a dataset in Events Manager) for your website.
Access to your Smeetz Back Office.
Access to your website, or to the Google Tag Manager (GTM) container installed on it, to install the Meta pixel.
Step 1: Install the Meta pixel on your website
Install the Meta pixel base code on every page where the Smeetz booking widget is embedded. Follow Meta’s guide to add it in your website’s code or through Google Tag Manager.
The pixel has to be on the page because Smeetz uses it in two ways:
Browser events: Smeetz calls your pixel to send each booking event from your website.
Server events: the pixel sets the
_fbpcookie (and_fbcwhen the visitor comes from a Meta ad). The Smeetz widget reads these cookies and adds them to the server events, so Meta can match the two copies and credit your ads.
Install the pixel once per page. If it’s in your website’s code and also in a GTM tag, every browser event is sent twice.
If you use Google Tag Manager: Smeetz also pushes its booking events into your GTM dataLayer (smtz_view_item_list, smtz_add_to_cart, smtz_begin_checkout, smtz_checkout_progress, smtz_payment_info, smtz_purchase). Keep your GA4 tags on these events, but remove any Meta pixel tag triggered by them. Smeetz now sends these events to Meta itself, and a GTM Meta tag has no event ID, so Meta would count those actions twice.
Your Meta pixel firing a PageView
Your Meta pixel sending a PageView from your website, with your pixel ID (seen here in a tag debugging browser extension).
Step 2: Add your Pixel ID in the Smeetz Back Office
In Meta Events Manager, open Datasets, select your pixel and copy its ID (a 15–16 digit number).
In the Smeetz Back Office, go to Integrations > Facebook Pixel ID.
Paste the ID and save.
Pixel ID in Meta Events Manager
Meta Events Manager, Datasets: your pixel ID is shown under its name.
Facebook Pixel ID in the Smeetz Back Office
Smeetz Back Office, Integrations: the Facebook Pixel field.
Step 3: Generate a Conversions API access token and send it to Smeetz
The access token allows Smeetz’s servers to send events to your pixel.
In Meta Events Manager, open Datasets, select your pixel and go to Settings.
Scroll to Set up direct integration and click Generate access token.
Copy the token and send it to your Smeetz contact or to Smeetz support through a secure channel. Smeetz adds it to your account.
Without the token, Smeetz can’t send server events to your pixel and you only get browser events.
Generate access token in Meta Events Manager
Meta Events Manager, Settings: Generate access token under Set up direct integration.
Events Smeetz sends
Event | When it’s sent |
ViewContent | The widget shows the tickets of a product |
AddToCart | The visitor adds a ticket or a seat to the basket |
InitiateCheckout | The visitor opens the checkout (personal details) step |
CheckoutProgress (custom event) | The visitor reaches the payment step |
AddPaymentInfo | The visitor selects a payment method or clicks Pay |
Purchase | The payment is confirmed and the confirmation page opens |
CheckoutProgress isn’t a standard Meta event, so it appears in Meta as a custom event.
Event data (custom_data)
Every event carries:
Field | Content |
| IDs of the tickets (ticket categories) in the event |
| One entry per ticket: |
|
|
| Currency of the booking, for example |
| AddToCart: price of the added tickets. InitiateCheckout, CheckoutProgress, AddPaymentInfo: basket total. Purchase: booking total |
| Number of tickets |
| Purchase only: the Smeetz booking reference |
| ViewContent only: the product name |
Customer information (server events only)
Server events also carry the information Meta uses to match the event to a person. Personal data is hashed with SHA-256 before it leaves Smeetz.
Field | Content |
| Email, hashed (once the visitor has entered it) |
| First and last name, hashed (once entered) |
| Meta browser ID, from the |
| Meta click ID, from the |
| The visitor’s browser |
| The visitor’s IP address |
Each server event also has event_time (Unix timestamp), event_id, action_source: website and event_source_url.
Example: a Purchase
Browser event, sent by your pixel on your website:
fbq('trackSingle', '<your pixel ID>', 'Purchase', { content_ids: ['1234', '1235'], contents: [ { id: '1234', quantity: 2, item_price: 20 }, { id: '1235', quantity: 1, item_price: 10 } ], content_type: 'product', currency: 'EUR', value: 50, num_items: 3, order_id: 'ABC123' }, { eventID: 'purchase-ABC123' });Server event, sent by Smeetz through the Conversions API:
{ "event_name": "Purchase", "event_time": 1762780000, "event_id": "purchase-ABC123", "action_source": "website", "event_source_url": "<address of the booking page>", "user_data": { "em": ["<SHA-256 of the email>"], "fn": "<SHA-256 of the first name>", "ln": "<SHA-256 of the last name>", "fbp": "fb.1.1762779000000.123456789", "fbc": "fb.1.1762779000000.<fbclid>", "client_user_agent": "Mozilla/5.0 ...", "client_ip_address": "203.0.113.10" }, "custom_data": { "content_ids": ["1234", "1235"], "contents": [ { "id": "1234", "quantity": 2, "item_price": 20 }, { "id": "1235", "quantity": 1, "item_price": 10 } ], "content_type": "product", "currency": "EUR", "value": 50, "num_items": 3, "order_id": "ABC123" } }Deduplication
Meta deduplicates a browser event and a server event when they have the same event name and the same event ID, within 48 hours.
Each action gets its own random event ID, shared by its browser and server copies.
Purchase uses
purchase-<booking reference>, for examplepurchase-ABC123. If the confirmation page is opened again for the same booking, Meta still counts one purchase.
You don’t need to configure anything for this. It only breaks if another tool sends the same events without an event ID, such as a Meta tag in GTM (see Step 1).
Test your setup
Meta’s Test events tab shows events in real time, like GA4’s debug view. To make Smeetz’s server events appear there, add Meta’s test code to your website’s address.
In Meta Events Manager, open Datasets, select your pixel and go to the Test events tab. Select Website as the channel, open Confirm your server’s events are set up correctly and copy the test code, for example
TEST12345.In the same browser, open the page of your website where the booking widget is embedded, adding the code to the address:
https://www.your-website.com/tickets?event-test-code=TEST12345If the address already has a
?, add&event-test-code=TEST12345instead.
Accept cookies in your website’s cookie banner, and turn off any ad blocker for this test. Otherwise the pixel doesn’t run.
Open the booking widget and make a complete booking: select a ticket, fill in your details and pay. You can use a low-price ticket and cancel the booking afterwards.
Go back to the Test events tab and check the list.
The test code is kept for the browser tab, including through the payment and the return to your website. To stop sending test events, close the tab.
Test event code in Meta Events Manager
Meta Events Manager, Test events: the test code for server events.
Website address with the test event code
Your website opened with ?event-test-code=… in the address, with the booking widget open.
What you should see
ViewContent, AddToCart, InitiateCheckout, CheckoutProgress, AddPaymentInfo and Purchase.
Each event received from Browser and from Server, with the same Event ID.
One of the two copies marked Deduplicated.
Purchase with the event ID
purchase-<your booking reference>.
In the Setup method column, server events show Manual setup, the label Meta gives a direct Conversions API integration like Smeetz’s. Browser events show how the pixel is installed on your website. Neither affects counting or deduplication.
Booking events in Meta Test events
Test events after a booking: each event received from Browser and Server with the same Event ID, one copy marked Deduplicated.
When the visitor refuses cookies or blocks the Meta pixel, Smeetz doesn’t send that visitor’s events to Meta either. Your Meta numbers can therefore stay below your Smeetz bookings.








