Short answer: to get reliable conversion tracking from Meta ads, run the Meta Pixel on your site and send the same key events from your server or CRM through the Conversions API, give each matching pair the same event name and event ID so Meta counts it once, pass good customer information (like email and phone) so events match real people, and test everything in Events Manager before you spend. For coaches, the events that matter most are usually Lead, booked call (Schedule) and Purchase, not page views.

This checklist walks through that setup in plain language. It’s written for coaches and women-led service businesses running Facebook and Instagram ads, with notes for medical, dental and wellness practices, where the rules are stricter. You don’t need to write code to follow it, but you will need access to your Meta Business portfolio, your website or funnel builder, and your CRM.

Why the Pixel alone isn’t enough anymore

The Meta Pixel is a snippet of code that runs in your visitor’s browser. When someone opts in to your masterclass or books a discovery call, the Pixel tells Meta. The trouble is that browsers miss things: ad blockers, privacy settings, slow-loading thank-you pages and people closing the tab too early all mean some conversions never get reported.

The Conversions API (often shortened to CAPI) sends events from your server or CRM straight to Meta instead. Meta’s own Conversions API best practices recommend a “redundant” setup: send the same events through both the Pixel and the Conversions API, so if the browser drops one, the server still reports it. The Conversions API can also report things that happen later or off your website, like a lead who becomes a paying client two weeks after the call.

Why it matters for your ads: Meta optimizes delivery toward the people most likely to do the thing you’re tracking. If half your booked calls never reach Meta, it’s learning from half the picture. Meta says an ad set needs roughly 50 optimization events in a week to exit the learning phase, so every missing conversion makes that harder to reach.

The Meta Pixel and Conversions API checklist

1. Confirm you own the assets

Before anything else, make sure your Pixel (Meta now calls it a dataset in Events Manager) and your ad account live in your Business portfolio, with your agency or freelancer added as a partner. If a past contractor created the Pixel in their own account, you can lose your tracking history when you part ways. We cover how to set this up safely in why you should own your ad account.

2. Pick the few events that actually matter

Most coaching businesses need three to five events, not twenty. A typical list:

• Lead: someone opts in for your free training, quiz or guide, or submits an application.
• Schedule: someone books a discovery or strategy call.
• Purchase: someone buys a program, with the value attached.
• A custom “qualified” event if you want Meta to learn from your best leads, for example when a call is marked as a good fit in your CRM.

Page views and button clicks are fine to collect, but don’t optimize your campaigns for them. Optimize for the deepest event you get enough of each week. If you get very few sales, optimizing for booked calls is often more practical than optimizing for purchases.

3. Install the Pixel cleanly, once

A common problem is the same Pixel installed twice, for example once in the theme header and again through a plugin or funnel-builder setting. That double-fires every event and makes your results look better than they are. Install it in one place, then check with the Meta Pixel Helper browser extension that each page fires each event once.

4. Fire events on real completions, not page loads you don’t control

A Lead event should fire when the form is actually submitted, and a Schedule event when the booking is actually confirmed. If your booking calendar is embedded from another tool, the thank-you page may never load on your domain, so the Pixel never sees the booking. This is exactly the gap the Conversions API fills, since your calendar or CRM knows the booking happened.

5. Send the same events through the Conversions API

You have three common routes:

• A built-in partner integration in your website platform or e-commerce tool, often set up in a few clicks from Events Manager.
• Your CRM. If you run your funnels and calendar in GoHighLevel, it has a Meta Conversion API workflow action. Its help center explains that you can send events when a form is submitted, a survey is completed, a customer books an appointment or an order is placed, and send later-stage “lead events” when a Facebook lead moves to a new pipeline stage (HighLevel: sending Meta conversion data; HighLevel: Conversions API in workflows). HighLevel also notes the contact needs Facebook attribution, such as the click ID, for Meta to match the event.
• A server-side tag manager or custom code, usually handled by a developer or your agency.

6. Deduplicate: same event name, same event ID

If you send a booking from both the browser and your server, Meta needs to know it’s one booking, not two. Meta’s deduplication guide says matching events must share the same event name (for example, both called “Schedule”) and the same event ID. According to Meta’s server event parameters, when it finds a match within 48 hours it only counts the first one. If your setup can’t pass a shared ID, ask your developer or integration about it before you trust the numbers. Duplicate counting is how a campaign “gets” twelve booked calls in a week when your calendar shows six.

7. Send good customer information for matching

Meta scores each server event with an Event Match Quality score from 0 to 10, based on the customer information you send and how many events it can match to Meta accounts. Meta rates email and click ID as the highest-priority identifiers, with phone, external ID and browser ID next. Its customer information parameters page explains that details like email and phone must be hashed before sending (most integrations do this for you) and that phone numbers need the country code. In practice: collect email and phone on your opt-in and booking forms, and make sure your integration actually passes them along.

8. Test before you spend

Open Events Manager, choose your dataset and use the Test Events tool. Submit your own opt-in form, book a test call and, if you can, run a test purchase. You should see each event arrive from both the browser and the server, then show as deduplicated rather than doubled. Meta’s best practices suggest using your own real name, email and phone for tests, since events that don’t match an account may be discarded.

9. Check the old “eight events” advice against what you actually see

Many guides still tell you to verify your domain and rank eight events under Aggregated Event Measurement. Meta has been retiring that manual setup for web events, and in many accounts the tab is gone (see Jon Loomer’s summary of Meta’s documentation). If your Events Manager still shows a ranking screen, follow it. Domain verification is still worth doing, because it proves you own the domain and controls who can edit your link previews.

10. Review it monthly

Tracking breaks quietly. A new funnel page, a changed booking form or a plugin update can stop an event without any warning. Once a month, compare the conversions in Ads Manager with what your CRM and calendar show for the same period. They won’t match exactly, since Meta attributes conversions using its own windows, but if Meta shows twice as many bookings as your calendar, or half, something is broken.

What this looks like for a coach, start to finish

Here’s an illustrative setup (not a client result) for a coach running ads to a free masterclass with a discovery-call offer at the end:

• The opt-in form fires a Lead event from the browser, and the CRM sends the same Lead event with the same event ID plus the lead’s email and phone.
• The calendar booking fires Schedule the same way.
• When the coach marks the call as a good fit in the pipeline, the CRM sends a custom Qualified event.
• A program sale sends Purchase with the price as the value.
• The campaign optimizes for Schedule at first, and the coach reviews whether there are enough Qualified events each week to test optimizing for those instead.

Combine this with fast follow-up and you give Meta much better signals to learn from. We go deeper on that side in the SMS follow-up that turns leads into booked calls, and on what a booked call should cost in Facebook ads for business coaches.

If you run a medical, dental or wellness practice, read this first

Practices in health and wellness face extra limits. Meta restricts the data that health and wellness advertisers can share and use for lower-funnel optimization (Search Engine Land’s overview), and HIPAA-covered practices have to be careful about what a Pixel or server event could reveal about a patient. A “booked appointment” event from a page about a specific treatment can say more than you intend. Before you set up either the Pixel or the Conversions API on a practice site, read our guide to HIPAA and online ads. This is general information, not legal advice, so check your setup with your compliance advisor.

Common mistakes to avoid

• Optimizing for page views or link clicks because they’re easy to collect. You’ll get cheap clicks, not clients.
• Sending server events without an event ID, so every conversion counts twice.
• Leaving email and phone out of server events, which keeps match quality low.
• Letting a contractor own the Pixel, so your history walks out the door with them.
• Never re-testing after you change a funnel, form or calendar.

Want us to check your tracking?

She Reigns Creative runs Meta and Google ads for women-led businesses, and tracking is one of the first things we check, because a campaign can only be as good as the data it learns from. We set up the Pixel, Conversions API and CRM events together, then report on booked calls and clients, not clicks. See how we work on our advertising and paid media page, read more about growing a coaching business on our business mindset page, or start with our small business guide to Meta ads.

Not sure your numbers are real? Book a call with our team and we’ll look at what your ads are tracking, what they’re missing, and what to fix first.

FAQ: Meta Pixel and Conversions API

Do I need the Conversions API if I already have the Meta Pixel?

For most businesses running conversion campaigns, yes. Meta recommends sending the same events through both, so the server can report conversions the browser misses and report events that happen later, like a sale after a call.

Will using both the Pixel and Conversions API double-count my conversions?

Only if they aren’t deduplicated. Give each matching browser and server event the same event name and the same event ID, and Meta counts it once when both arrive within 48 hours.

What is a good Event Match Quality score?

Meta scores it from 0 to 10, and higher is better. Rather than chasing a number, make sure you’re sending email, phone and the click ID wherever you have them, since Meta ranks those among the most useful identifiers.

Which events should a coach track?

Start with Lead (opt-in or application), Schedule (booked call) and Purchase (program sale with value). Add a custom qualified-lead event from your CRM if you want Meta to learn from your best prospects.

Can I set up the Conversions API without a developer?

Often, yes. Many website platforms and CRMs, including GoHighLevel, have built-in Meta Conversions API options. You’ll still want to test in Events Manager to confirm events arrive and deduplicate correctly.