Your agency or developer keeps mentioning the "Conversions API", or "CAPI". Here's what it is, and whether your salon actually needs it.
The short answer: the pixel is a small piece of code on your website that watches what visitors do in their browser. The Conversions API sends results to the ad platform from your systems instead, so it still works when the browser blocks the pixel, and it can report bookings that happen outside your website. For salons whose bookings happen inside a booking widget, it's often the only way the ad platform learns that someone booked.
The pixel: a camera on your shop floor
Think of the pixel as a security camera inside your website. It sees people arrive, look at your services and click "Book Now". It reports that to Facebook, Instagram or TikTok, which use it to measure results and find more people like your clients.
Cameras have blind spots:
- iPhones and browsers block it. Apple's privacy features, Safari and ad blockers stop many pixel reports.
- It can't see into other companies' rooms. If clients book in a widget from your booking software (Boulevard, for example), that widget is the booking company's room, not yours. The camera sees people walk up to it, and never sees them book.
The Conversions API: the receipt sent from the back office
The Conversions API works differently. Instead of watching the shop floor, your back office reports what happened: "an appointment was booked", "this visit was paid, $85".
For salons, it typically works like this:
- When someone arrives from an ad, a note is kept of which ad they clicked.
- When they book, your booking software notifies a server.
- The server tells Meta (and TikTok, Google and others): "this person from that ad booked."
Because it doesn't depend on the visitor's browser, iPhones and ad blockers don't stop it. And because it starts from your booking software, it sees bookings the camera can't.
Why salons need it more than most
An online shop's checkout is usually on its own website, so the pixel sees purchases. A salon's booking usually isn't:
- The booking happens in a widget that belongs to the booking software.
- The real money comes later, when the client shows up and pays, sometimes with add-ons, discounts and tips.
The pixel can't see either of those. A server-side setup can send both: the booking right away, and the real amount when the visit is completed. That's what turns "cost per click" into real return on ad spend. We describe a full example in why your Facebook ads show 0 bookings when you use Boulevard.
Won't it count everything twice?
Not when it's done right. If both the pixel and the server report the same action, each report carries the same event ID. The platform sees the match and keeps one. Meta, for example, drops the second copy when the browser and server send the same event name and event ID within 48 hours.
If your bookings suddenly look twice as good after a tracking change, ask about this first.
When the pixel alone is enough
Be realistic. The pixel alone can be fine when:
- Clients book through a form or page on your own website, which the pixel can see, and
- You spend a small amount on one platform, and you check results against your calendar anyway.
Once bookings happen in a widget, or you run several platforms, the pixel alone leaves you guessing. More on that trade-off in should you build custom tracking or accept the platform's numbers?.
What to ask your agency or developer
- Do we send bookings through the Conversions API, or only the pixel?
- Where do our bookings actually happen: on our site, or in the booking software's widget?
- Do the pixel and the server share event IDs, so nothing is counted twice?
- Do we send the real amount when a visit is completed, or only a booking count?
- Is the same done for TikTok, Google and the other platforms we use?
For the technical details, your developer can read our complete server-side guide.
