The Meta Pixel integration connects your booking site to your Meta (Facebook/Instagram) advertising account so conversions get reported back when customers arrive from your ads and complete a booking. Use it to measure ad performance, build custom audiences, and let Meta optimize delivery against actual conversions.
Getting started
Navigate to Settings > Company groups, open the group, switch to the Integrations tab, and click Configure integration on the Meta Pixel card.
How it works
The Meta Pixel is a small tracking script that loads on your booking site when the integration is active. It fires events back to Meta on key actions (page view, add to cart, purchase) and identifies the customer when possible. Meta uses those events to attribute conversions to the right ad and to optimize your campaigns going forward.
The configuration view is minimal: a single Meta Pixel ID field and an Active toggle.
Step-by-step guide
Find your Pixel ID
| Step | Action |
|---|---|
| 1 | Open Meta Events Manager |
| 2 | Pick your Business Account if you have multiple |
| 3 | In the Data Sources list, click the Pixel you want to use (or create one if you haven't yet) |
| 4 | Copy the Pixel ID — it's a long numeric string at the top of the Pixel's overview page |
If you don't have a Pixel yet, click Connect Data Sources in Events Manager and follow Meta's setup flow. The integration here doesn't create one for you.
Configure the integration
| Step | Action |
|---|---|
| 1 | In the Meta Pixel configuration view, paste the ID into the Meta Pixel ID field |
| 2 | Toggle Active on |
| 3 | Click Save at the bottom of the tab |
Tracking starts immediately on your booking site. Use Meta's Events Manager to verify the Pixel is firing — there's a Test events view that shows incoming events in real time.
Verify with Meta's Test events
| Step | Action |
|---|---|
| 1 | In Meta Events Manager, open your Pixel and go to Test events |
| 2 | Open your booking site in the same browser |
| 3 | Browse, add to cart, and complete a test purchase if possible |
| 4 | Watch the Test events view for incoming events. They typically appear within seconds |
If events don't appear, check that Active is on, the Pixel ID is correct, and you're testing on the actual booking site URL (not a staging environment that the Pixel hasn't seen before).
Reference
Configuration view
| Field | Type | Notes |
|---|---|---|
| Meta Pixel ID | Text input | Numeric Pixel ID from Meta Events Manager |
| Active | Toggle | Enable or disable Pixel tracking |
| Cancel | Button | Discards changes |
| Save | Button | Commits the Pixel ID and Active toggle |
Where to get your Pixel ID
| Source | Path |
|---|---|
| Meta Events Manager | https://business.facebook.com/events_manager → Data Sources → your Pixel |
| Meta Business Suite | Events Manager → Data Sources |
Good to know
- The Pixel only loads on your public booking site. Internal admin actions in the console don't fire Pixel events. The integration is for customer-facing tracking.
- One Pixel ID per group. If you advertise different locations on different ad accounts, configure each location with its own Pixel ID.
- Meta needs a few hours to a few days to start using new Pixel data for ad optimization. Initial conversions may not affect campaign delivery immediately.
- The Conversions API (CAPI) is Meta's server-side companion to the Pixel. It's not part of this integration today; the integration is browser-side Pixel only.
- Active off preserves the Pixel ID. Toggle off to pause tracking during testing or maintenance without losing the configuration.
- iOS 14.5+ tracking restrictions apply to Meta Pixel just like every other ad platform's tracking. Some conversions won't be reported back due to App Tracking Transparency. This is a Meta/Apple-side limitation, not something to fix here.
- Use UTM tracking alongside the Pixel to see channel attribution in your own Reports. The Pixel reports to Meta; UTM reports to you.
FAQ
Q: Do I need a Meta Business account to use this?
A: Yes. You need a Meta Business Suite account with Events Manager access to create a Pixel and get a Pixel ID. The integration only handles the connection from our side.
Q: Can I track conversions from both Facebook and Instagram ads?
A: Yes. Meta Pixel tracks conversions from both platforms since they share the same ad infrastructure. The Pixel doesn't distinguish — Meta does the attribution on its side.
Q: My Pixel says "no events" in Events Manager. What should I check?
A: 1) Confirm Active is on in the integration. 2) Confirm the Pixel ID exactly matches the one in Meta Events Manager (typo-prone — easy to miss a digit). 3) Open your booking site in a browser, then check Meta's Test events view in real time. 4) Disable browser ad blockers that might suppress the Pixel script. 5) Confirm you're testing on the live booking site URL, not a staging URL the Pixel hasn't been registered for.
Q: Can I have multiple Pixels on the same booking site?
A: One Pixel ID per group. To send to multiple Pixels, use Google Tag Manager — GTM can fan out the same events to multiple destinations.
Q: Does this integration support Conversions API (CAPI)?
A: Not today. This integration is the browser-side Pixel only. CAPI requires a server-to-server connection that isn't built into this integration. If you need CAPI, you can wire it up via your own server using transaction webhooks.
Q: How do I track which Facebook ad drove a specific booking?
A: Meta does the attribution server-side based on the Pixel events plus the click data they track. Open the ad in Ads Manager to see the conversions attributed to it. For first-party attribution in your own reports, use UTM tracking and tag your Facebook ad URLs with utm_source=facebook.
Q: Why don't my Instagram Story ads show conversions?
A: They should — Story ads share Meta's ad infrastructure with Feed ads. If conversions aren't appearing, check that the ad's destination URL points to your booking site (not a third-party landing page that doesn't load the Pixel) and verify with Test events that the Pixel is firing on the destination.
Q: Can I have a different Pixel for testing vs production?
A: There's only one Pixel ID slot per group. For testing without polluting your production Pixel, use Meta's Test events feature with a test event code, or set up a separate Meta Pixel for staging and swap the ID temporarily.