On this pageJump to a section
Open your ad account and look at one setting: which event is this campaign optimizing for?
If the answer is "Lead," or "Landing Page View," or "Purchase" and you have never asked why, this article is for you. In most coaching accounts I look at, the optimization event is not a strategic choice. It is whichever event happened to be firing when the campaign was built.
That is a quiet and expensive mistake, because the event you choose is the instruction you give Meta about what a good result looks like. Here is how to choose it on purpose.
What do Meta's standard events actually mean?
Meta defines a set of standard events with official descriptions. The ones that matter for a coach are these.1
- Lead: "When a sign up is completed."
- SubmitApplication: "When a person applies for a product, service, or program you offer."
- Schedule: "When a person books an appointment to visit one of your locations."
- Purchase: "When a purchase is made or checkout flow is completed."
For Purchase, both currency and value are required parameters.1
A note on Schedule
Meta's description of Schedule mentions visiting one of your locations. Many advertisers use it for booked calls anyway, and it is a reasonable choice if you are consistent. What matters is that the same step always fires the same event, so the data stays comparable over time. If you prefer, you can use SubmitApplication for an application form and a custom event for a booked call.
Custom events
The Conversions API documentation points to both standard and custom events.4 Custom events let you name a step Meta has no standard event for, such as "call attended."
Why does "the only event firing" cause trouble?
Because the system optimizes for exactly what you give it.
The Lead trap
If your only event is Lead, Meta learns to find people who fill out forms. Some of those people are exactly who you want. Many are not. They give an email for a free resource, never book and never buy. The campaign looks healthy at the top of the funnel and empty at the bottom.
The Purchase trap
If your only event is Purchase, you are asking Meta for the deepest result. That is the right instinct, but if purchases happen a few times a month, there may not be enough events for the system to learn from. Meta's guidance is that an ad set unlikely to get around 50 optimization events in the week after its last significant edit will show Learning Limited.5 The rules behind that are in Scaling Meta Budgets Without Resetting Learning.
| Single-event setup | Mapped funnel |
|---|---|
| Optimizes for whatever fires | Optimizes for the deepest event with enough volume |
| No visibility between click and sale | Each step measured |
| Cheap leads that never book | Leads, bookings and sales compared |
| Hard to diagnose problems | Easy to see where the funnel breaks |
How do you map events to a coaching funnel?
Walk the path a buyer takes and decide what fires at each step.
- Opt-in or webinar registration: Lead.
- Application submitted: SubmitApplication.
- Call booked: Schedule (or a custom event, used consistently).
- Call attended: a custom event sent from your booking tool or CRM. This is the step most accounts skip, and it is the best quality filter you have (see Show Rate Is a Revenue Metric).
- Enrollment paid: Purchase, with the real value and currency.
Choosing the optimization event
Start with the deepest event that gives you enough volume to learn. For many accounts that is Schedule or a qualified application. If Purchase volume is high enough, optimize for it. If not, optimize one step up and keep Purchase flowing back so you can judge quality.
Do not climb down the funnel to a cheaper event just to make cost per result look better. Check lead quality downstream, because a cheap shallow event can hide expensive problems.
How do you send events through both Pixel and Conversions API?
Meta recommends a redundant setup that sends events through the Meta Pixel and the Conversions API together.2 I covered the basics in Meta Conversions API in 2024. The Conversions API connects your marketing data, including website events and CRM data, from your server to Meta, and server events are processed like events sent by the Pixel.4
Why both
The browser can miss events: blockers, failed loads and slow pages. Your server can send events the browser never sees, such as a payment confirmed or a call attended. Used together, they give a more complete record. The risk is counting the same action twice, which is why deduplication matters.
How does deduplication work?
Meta deduplicates events when the Pixel's eventID matches the Conversions API's event_id and the event name matches the event_name.2
The rules to know
- Action happensCreate one unique event ID
- Browser PixelSends eventID and event name
- Conversions APISends the same event_id and event_name
- MetaKeeps one and discards the duplicate
- Same ID and same name. Use one unique ID per action, and send it from both sources.
- 48 hours. Meta discards later events with the same key combination that reach the same Pixel ID within 48 hours of the first.2
- Which one wins. If the server and browser events do not differ meaningfully, Meta generally keeps whichever arrives first.2
A practical setup
- Create the event ID once. When the action happens, generate a unique ID.
- Pass it to the browser event as the eventID.
- Pass the same ID to your server event as event_id, with the same event name.
- Test with Meta's tools, and check that each real action shows up once, not twice.
What customer data should you send?
The more accurate identifying information that goes with an event, the better Meta can match it to a person. The Conversions API accepts customer information parameters such as email, phone, name, location and browser identifiers. Meta says to hash fields like email and phone before sending, and not to hash client IP address, user agent, fbc and fbp.3 It also says sending client IP address and user agent may help improve event matching.3
Handle personal data carefully
Only send what you have consent and a lawful basis to send, follow the privacy rules that apply to your audience and never send sensitive information. Use your own policy and a professional's advice. I am not a lawyer, so treat this as a prompt to check, not a ruling.
The pattern I see most is the same: the creative gets the credit and the blame, while the data underneath is quietly wrong. Clean events are the foundation under every campaign decision.
You do not tell Meta what you want with your headline. You tell it with your events.
If you want your funnel's events mapped and your signal cleaned up, I can help.
Keep building.Ekai
Questions people ask
Which Meta pixel events should a coach track?
At minimum: Lead for opt-ins, SubmitApplication if you use an application, Schedule for booked calls and Purchase for paid enrollments, with value and currency on Purchase. Add a custom event for calls that actually happen.
How does Meta deduplicate Pixel and Conversions API events?
Meta deduplicates when the Pixel's eventID matches the Conversions API event_id and the event names match, for events received within 48 hours. If the events do not differ meaningfully, Meta generally keeps the first one received.
Should I optimize for Lead or Purchase?
Optimize for the deepest event that fires often enough for the system to learn, which Meta's guidance puts at around 50 optimization events after the last significant edit. For many coaching accounts that is a qualified lead or booked call, with Purchase as the signal to report on.
Do I need the Conversions API if I have the Pixel?
Meta recommends a redundant setup that sends events through both the Pixel and the Conversions API. Done correctly, with deduplication, it gives the system a more complete picture than the browser alone.
Sources
- 1
- 2
- 3
- 4
- 5
