What is the Meta pixel?
The Meta pixel, formerly the Facebook pixel, is a piece of code on your website that tells Meta what visitors do there: page views, form submissions, purchases. It sees the browser, so for a gym it stops at the form.
Updated
The Meta pixel for gyms
Install the pixel and Meta can see your website the way a browser sees it. A page loads: PageView. Somebody submits the enquiry form: Lead. Somebody lands on a thank-you page after paying online: Purchase. Meta uses those events to report which ads produced them, to build audiences of people who did them, and to optimize delivery toward people likely to do them again.
For a gym, the useful events mostly happen after the browser is closed. The consult is booked by your front desk, the person shows up in the building, and the membership is paid for at the desk or through the billing system. The pixel never sees any of that. So the event Meta optimizes toward is the Lead, and Meta gets very good at finding people who submit forms.
The pixel is still worth installing, because it is how Meta learns which click produced the enquiry, and it is where the fbclid gets its first use. The plan is to pair it with the Conversions API, which carries the front-desk events the pixel cannot see.
Where the pixel misleads: it counts what it can see, on its own terms. Browsers that block it, people who enquire by phone and every stage after the form are invisible, and the Lead count it reports will never reconcile with your CRM.
How Adsu uses the Meta pixel
Adsu does not replace the Meta pixel; keep it on the site. Adsu’s own pixel records the visit alongside it, including the fbclid and the campaign parameters, so the enquiry can be tied to the ad and followed to the front desk. Adsu counts verified stages only: if a stage cannot be verified, it is not counted. Every report is one line per campaign per location.
Booked, showed and paid go back to Google as offline conversions and to Meta through the Conversions API. That is how the stages the pixel cannot see reach Meta. Adsu credits the last eligible touch inside the 30 days before the payment.
Questions, answered.
Yes. Meta renamed the Facebook pixel to the Meta pixel when the company changed its name. It is the same snippet, the same events and the same Events Manager; only the name changed. Older guides and plugins still say Facebook pixel.
Keep both. The pixel reports what happens in the browser, the Conversions API reports what happens everywhere else, and Meta can deduplicate an event it receives from both. The pixel alone stops at the form; the API alone loses the browser context that helps Meta match the click.
Because the pixel counts form submissions it could see, including duplicates, tests and people who never became a real enquiry, and misses phone calls and blocked browsers entirely. Your CRM counts people. The two were never measuring the same thing, and the gap is normal.
Related
The Meta Conversions API, CAPI, is the server-side way to send events to Meta, from your systems instead of a browser. What a gym sends through it.
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.
Conversion trackingConversion tracking is telling an ad platform that something worth paying for happened, so it can credit the ad and find more of it. What a gym counts.
Server-side trackingServer-side tracking sends events to ad platforms from a server, not the browser. Why revenue verified from the billing system beats a browser event.
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.