What is the Meta Conversions API?
The Meta Conversions API, CAPI, is the server-side way to send events to Meta, from your systems instead of a browser. For a gym it is how bookings, shows and payments reach Meta, because the pixel stops at the form.
Updated
The Meta Conversions API for gyms
The Meta pixel lives in the browser, so it can only report what a browser does. The Conversions API lives on a server, so it can report anything your systems know: a consult booked in the CRM, an appointment marked attended, a membership paid in the billing system. Each event is sent with enough about the person, hashed, for Meta to match it to the ad click that started things.
For a gym, that is the difference between Meta optimizing for form fills and Meta optimizing for members. Send only pixel events and the campaign gets judged, and steered, by the Lead event. Send booked, showed and paid through the API and the same campaign is steered by the stages that fill the building. The plan is the same for every gym: keep the pixel for the browser, add the API for the front desk.
The API also survives what the pixel does not. Browser tracking prevention, ad blockers and people who enquire by phone all leave gaps in pixel data; a server-side event does not depend on the browser at all. See server-side tracking for the general idea.
One warning: it only helps if the events are true. Send an appointment as a purchase to make the numbers look better and Meta will find you more people who book and never pay.
How Adsu uses the Meta Conversions API
Booked, showed and paid go back to Google as offline conversions and to Meta through the Conversions API. Each event goes when the stage is verified, not when it is entered: the booking when it lands in the CRM, the show when it is marked attended, the payment when it clears in the billing system. Adsu counts verified stages only: if a stage cannot be verified, it is not counted. Every report is one line per campaign per location.
Adsu credits the last eligible touch inside the 30 days before the payment. There is no developer work at the gym; the connection to Meta is part of the setup Adsu does for you.
Questions, answered.
It is one example of it. Server-side tracking is the general idea of sending events from a server rather than a browser; the Conversions API is Meta’s endpoint for receiving them. Google’s equivalent for a gym’s needs is the offline conversion import. Both carry the stages that happen away from the website.
Not with Adsu. The connection to Meta is part of the setup Adsu does for you, and the events it sends are the verified stages from your CRM and billing system. Wiring it yourself means something on a server that can read those systems and talk to Meta, which is the part most gyms never get to.
No, it works alongside it. The pixel carries the browser context Meta uses to match a click; the API carries the events that happen off the website. Meta can deduplicate an event it receives from both. Keep the pixel and add the API for booked, showed and paid.
Related
The Meta pixel, formerly the Facebook pixel, is a piece of code on your website that tells Meta what visitors do there. Why it stops at the form for a gym.
FbclidAn fbclid is the click identifier Meta adds to your landing URL when someone clicks a Facebook or Instagram ad. Why the pixel must see it.
Offline conversion trackingOffline conversion tracking is sending an ad platform a conversion that happened off your website: a consult, a show, a payment. The front-desk join.
Feedback loopThe feedback loop is Adsu’s name for sending verified outcomes, booked, showed and paid, back to the ad platforms as the wins to optimize for.
The proof
- Net members
- +21
- Lifetime value added
- $67,000+
Bobby & Maria Gasdia, Big Day Fitness, 2 locations
Stop paying for leads. Start paying for members.
Early access is opening in small groups. Applying takes two minutes, and we’ll tell you straight whether your stack is ready to connect.