The short answer: Meta learns from every booking it sees. The Meta Pixel misses some, because ad blockers and privacy settings can stop it firing. The Conversions API sends the same bookings from your website’s server, so far fewer slip through. Then check Event Match Quality in Events Manager and aim for 8 or more out of 10.
This is episode 4 of Media buying in 60 seconds, James’s series of short, plain English Meta ads fixes for Irish small businesses. The full series sits in our media buying overview.
Why does Meta need to see your bookings?
Every booking Meta sees teaches it who to show your ads to next. Every booking it misses is a lesson lost, and your cost per booking looks worse than it really is. Meta is clear that only matched events can be used for ad attribution and delivery optimisation.
Pixel or Conversions API?
Both. Meta recommends a “redundant” setup: the same events sent from the Pixel in the browser and from the Conversions API on your server.
| Meta Pixel | Conversions API | |
|---|---|---|
| Runs in | The visitor’s browser | Your website’s server |
| Can be stopped by | Ad blockers, browser privacy settings, slow or broken page loads | Far less exposed to any of those |
| Extra it can send | On-page events | Offline events and events that happen later |
| Use it? | Yes | Yes, alongside the Pixel |
Won’t that count bookings twice?
Not if it’s set up properly. Send the same event name from both, plus an event_id, and Meta deduplicates them. On WordPress, most good booking and shop plugins (and Meta’s own integrations) handle this for you. Check it in Events Manager rather than assuming.
How do you check Event Match Quality?
- Open Events Manager and select your Pixel (dataset).
- Click the event that matters, for example Purchase or Lead.
- Open the event’s details and find Event Match Quality.
Meta scores it out of 10: how well the customer information sent with each event lets Meta match it to a real account. 8 to 10 is high, so 8 or more is a good target.
What raises the score?
- Send a hashed email address and phone number with each server event. These usually make the biggest difference.
- Add first and last name and the visitor’s IP address where you have them.
- Keep the
fbpandfbccookie values fresh if you send them.
The rule
Fix the tracking first, then scale the spend. Scaling on bad data just buys more of the wrong thing, faster.
Read the transcript
“Your ads are bringing in bookings, but does Meta know that? Meta learns from results. Every booking it sees teaches it who to show your ads to next. Every booking it misses is a lesson lost. The Meta Pixel on your website tracks those bookings, but ad blockers and privacy settings can stop it firing, so some go missing. That’s why a media buyer adds the Conversions API. It sends the same bookings straight from your website server, so far fewer slip through. Then we check Event Match Quality in Events Manager. It’s a score out of ten for how well Meta matches bookings to real people. Aim for eight or more. Fix the tracking first, then scale the spend.”
Want a hand?
James runs Meta ads and paid media at Pixelated Bubble. See how we do media buying for Irish businesses, or book a free call with James.
Sources
- Conversions API, Meta for Developers. Checked 11 November 2026.
- Conversions API best practices (redundant setup, deduplication, customer information, Event Match Quality), Meta for Developers. Checked 11 November 2026.
- Omni optimal technical setup guide (Event Match Quality scale), Meta for Developers. Checked 11 November 2026.
Previous episode: your creative is your targeting. Next episode: better leads, not more leads. Back to the series overview.