Meta CAPI: A Practical Setup Guide

Meta's Conversions API sends conversion events from your server to Meta instead of relying on browser tracking alone. When someone fills your form on Safari with an ad blocker, your Meta Pixel might not fire. CAPI catches that event from your backend and sends it anyway.

A pixel working alone captures about sixty-five percent of conversions. Pixel plus CAPI together recover about ninety-five percent. That thirty-point gap is where your optimisation lives.

Here is how that chain plays out in practice.

Someone clicks your ad and fills your form. The pixel fires Lead. Three days later you mark them qualified. You send Meta QualifiedLead. A week later they book a meeting. You send Schedule. Eventually they sign. You send Purchase. Meta now knows the full journey from click to revenue.

You do not need a CRM to do this. You need a place where you track what happens after the form fill, and a way to send it to Meta.

What you need before you start

1. A Meta Pixel configured in Events Manager. Meta calls this a "Dataset" in parts of the interface. The Pixel ID and Dataset ID are the same thing.

2. A CAPI access token from Events Manager. Go to your Pixel → Settings → Conversions API → Generate Access Token. This is a long-lived token specific to one pixel. Do not confuse it with a Marketing API token.

3. A way to detect outcomes and send them to Meta. This can be a Google Sheet with Apps Script, a Zapier flow, a webhook from your form tool, or a simple POST from your website backend. What matters is detecting the outcome, mapping it to Meta's standard event name, SHA-256 hashing the identifier, and sending it.

4. An event_id for deduplication. When the pixel fires Lead in the browser and your backend sends Lead through CAPI for the same submission, Meta needs to know they are the same event. Send the same event_id in both places.

Three ways to set it up without a CRM

Path 1: Google Sheets + Apps Script

Best for no-code teams and small budgets.

Set up a sheet with one row per lead. Add columns for email, phone, stage, and timestamp. Write an Apps Script that triggers when a stage cell changes. In the script, SHA-256 hash the email and phone, build the CAPI payload, and POST it to Meta's endpoint.

The effort is medium but you control every step. Match rate is high because you can capture the fbclid from your landing page URL and format it correctly.

Path 2: Zapier or Make

Best if you already use automation tools.

Trigger on a new row in your spreadsheet or a new record in your database. Use a code step to format the payload — you still need to SHA-256 hash the identifiers yourself, since most no-code tools do not do this automatically. Then send to Meta's CAPI endpoint via a webhook action.

The effort is low but match rate can be medium if you do not hash identifiers or miss the fbclid.

Path 3: Website backend

Best if you have a developer.

Capture form submissions in your backend. Store the lead data. When the stage changes — via an admin action, a webhook, or a scheduled job — build the CAPI payload with full control over hashing, identifiers, and timing. Send via HTTPS POST.

The effort is higher but you get full control over match rate and can implement retry logic for failed requests.

The point is not which tool you use. The point is that you track the outcome and send it.

The events to send

Meta recognises exactly seventeen standard event names. These are the only names the algorithm understands out of the box. Use them exactly as written, case and all.

Lead · QualifiedLead · Schedule · StartTrial · Purchase · AddPaymentInfo · AddToCart · AddToWishlist · CompleteRegistration · Contact · CustomizeProduct · Donate · FindLocation · InitiateCheckout · Search · SubmitApplication · Subscribe · ViewContent

For most lead-generation funnels, you only need the first five. Here is the mapping.

Schedule is Meta's name for a booked meeting. StartTrial is Meta's name for an opportunity. These are not names the ecosystem invented — they are what HubSpot, Salesforce, and every other integration maps to behind the scenes.

Send the event name exactly as shown. QualifiedLead works. Qualified does not. Meta will accept Qualified but the algorithm has no built-in understanding of what it means, and it cannot be used as an optimisation target for Conversion Leads campaigns.

Two types of leads you will handle

Website forms

Someone clicks your ad, lands on your site, fills your form. The pixel fires Lead automatically. You later send QualifiedLead, Schedule, and Purchase through CAPI as the lead progresses.

• Best identifier: The fbclid parameter in your landing page URL. Wrap it into an fbc cookie and send it with every CAPI event. Match rate is near perfect when present.
• Fallback: SHA-256 hashed email + phone. Gets you to eighty percent or better.
• Action source: website for the initial Lead event (to match the pixel), system_generated for stage events.

Meta Lead Ads (instant forms)

Someone clicks your ad, a native form opens inside Facebook or Instagram, they fill it without visiting your site. Meta stores the lead and counts it in Ads Manager. No pixel fires. No browser session. No UTM parameters.

The lead count in Ads Manager is not a CAPI event. It is internal tracking because Meta owns the form. If you want the algorithm to learn what those leads turned into — qualified, junk, customer — you have to send those events yourself.

• Best identifier: The fifteen-digit leadgen_id Meta assigns to every instant form submission. If you capture it and send it back through CAPI, match rate is ninety-five percent or better. Meta already knows exactly which lead you are talking about.
• Without it: Email and phone alone give fifty to sixty-five percent match rate. That gap is the difference between CAPI being a meaningful feedback loop and expensive decoration the algorithm half-trusts.
• Action source: system_generated for all events, since there is no browser session.

A lookback window to know about

Meta accepts events up to sixty-two days in the past for offline events with action_source: physical_store. For website forms and instant forms, the limit is seven days. Events older than seven days are rejected with error subcode 2804003.

If you are turning CAPI on for the first time, send events in close to real time from day one. Do not plan to backfill last quarter's leads.

Test your events before going live

Meta provides a test event code in Events Manager for every pixel. It looks like TEST12345. Send your events with test_event_code in the payload and they appear in a dedicated test panel instead of your production data.

Use the test panel to check three things:

1. The event name matches one of Meta's seventeen standard names.
2. The event_id is identical between your pixel event and your CAPI event for the same action.
3. Meta predicts a strong match to a Facebook profile. If the match looks weak, add more identifiers. Email and phone are the highest-impact fields you control.

A test event code takes thirty seconds to generate and saves hours of debugging silent failures.

Getting the most out of CAPI once it is running

Most teams set up CAPI, keep running campaigns the same way, and wonder why nothing improved. Here is how to capture the benefit.

Optimise on the right event. Meta's algorithm needs about fifty conversion events per ad set per week to exit learning and bid efficiently. Start with Lead if you need volume. Once you have fifty QualifiedLead events per week per ad set, switch to that. Once you have fifty Schedule events, switch to that. Do not rush it.

Send value with every event. A raw lead might be worth a hundred rupees. A qualified lead might be worth fifty thousand. The ratio matters more than the exact number. Once values flow, switch from lowest cost to highest value. Now Meta is trying to get you more valuable leads, not just more leads.

Build a junk lookalike and exclude it. Take your last ninety days of disqualified leads. Upload them as a custom audience. Build a one to five percent lookalike. Exclude it in your ad sets. Meta proactively avoids people who look like your bad leads.

Configure the Sales Funnel in Events Manager. After seven days of production data and at least two hundred leads per month, a Sales Funnel panel unlocks. Categorise each event as positive stage or "other" stage. Order positive stages from top to bottom. This tells Meta's algorithm which events represent progress and which represent failure.

Watch your Event Match Quality. Meta scores every CAPI event zero to ten based on Facebook user match. Six is okay. Eight or above is great. To hit eight, send clean email and phone in every event, plus IP and user agent. Email alone is worth up to four points. Phone is worth about three.

The hierarchy of identifiers matters. A leadgen_id from an instant form is nearly exact. A fbc cookie ID is strong if fresh. Email and phone are good. IP and user agent help. Send as many as you have, in every event.

Checklist before you go live

Get these right and CAPI becomes one of the highest-ROI pieces of infrastructure in your marketing stack.