How to Set Up Meta Conversions API Without a Developer (Step by Step)
Most Conversions API guides assume you have a developer, a server and a free week. Most marketers have none of those. The good news: in 2026 you don't need them. This guide walks through a setup a marketer can do alone in under an hour.
If you're still deciding whether you need CAPI at all, read What Is Meta Conversions API first.
Step 0: Decide where your conversions actually happen
This decides everything else. Write down the path from ad click to money:
- Online store: click → product page → checkout on the website. The sale happens on the site.
- Lead generation: click → form or message → manager calls → deal closes in the CRM. The sale happens in the CRM.
- Mixed: some customers buy online, some through managers.
For an online store on Shopify or WooCommerce, the platform's built-in or plugin integration usually covers the website side. For lead generation, the key is connecting your CRM — that's where the events that matter live.
Step 1: Prepare what you'll need
- Admin access to your Meta Business portfolio, ad account and pixel (dataset).
- Access to your lead source: CRM admin rights, a Google Sheet, or the ability to add a script to your website.
- A list of your sales stages, for example: New lead → Qualified → Meeting → Paid → Lost.
Step 2: Choose which events to send
Don't send everything. Send the few events that tell Meta which people are valuable:
| Your stage | Meta event | Why |
|---|---|---|
| Form submitted / new deal | Lead | Volume signal, fast feedback |
| Meeting or consultation booked | Schedule | A real person who engaged — filters out junk |
| Deal paid | Purchase with value and currency | The signal that matters most, and enables ROAS |
Optionally, send negative stages too — spam, no answer, disqualified — as custom events. They don't train optimization directly, but they let you see in Ads Manager which campaigns bring junk.
Send the customer's email and phone with every event if you have them — they're the main way Meta matches events to people. The integration hashes them before sending.
Step 3: Connect it — the no-code way
Here's how it looks in LeadMe, which was built specifically for this. Other tools follow a similar logic.
- Add a pixel → Meta → Connect with Facebook. Log in, choose the ad account and pick your pixel (or create a new one). No tokens to copy.
- Choose where leads come from: AmoCRM (Kommo), Bitrix24, HubSpot, Pipedrive, Google Sheets, Stripe, Shopify, the LeadMe website script, the WordPress plugin, or any other system through Make, Zapier or a webhook.
- Pick the events from Step 2 and tick the customer fields you have (email, phone, name, city, deal amount).
- Map your CRM stages to events: "Meeting booked" →
Schedule, "Paid" →Purchase, "Spam" →SpamLead. - Add the website script (optional but recommended). It stores ad click IDs (
fbclid, and the click IDs of other platforms) with each form, which noticeably improves matching.
From then on, every time a deal moves to a mapped stage, LeadMe sends the event to Meta within minutes — hashed, deduplicated, with the click ID attached.
Step 4: Test before you trust it
- In Events Manager → Test events, copy the test code (it looks like
TEST12345). - Send a test event from your integration with that code. In LeadMe, it's the Test button on the pixel page.
- Within a minute the event should appear in Test events with the source Server. If it does, the connection works.
- Then move a real test deal through your CRM stages and check that each event arrives.
Step 5: Watch the first week
- Event Match Quality in Events Manager should be at least "OK". Low scores usually mean missing email/phone.
- No double counting: if you also send
Leadfrom the pixel, make sure deduplication works — see Conversions API vs Meta Pixel. - Compare with your CRM: Ads Manager won't match exactly, but purchases attributed to ads should now be in the same ballpark as reality.
Mistakes that waste the setup
- Sending only
Lead. Then CAPI just duplicates what the pixel already did. The value is in later stages. - Sending events in monthly batches. Meta rejects events older than 7 days. Send them when the stage changes.
- Optimizing campaigns for
Purchaseon day one with five sales a month. Meta needs volume to learn; start optimizing for an earlier stage such asScheduleand switch once purchases are frequent enough. - Forgetting the deal value. Without
valueandcurrencyonPurchase, you can't see ROAS.
Quick answers
How long does setup take?
With a ready integration, 20–60 minutes, most of which is deciding which stages map to which events. A custom developer integration usually takes days to weeks.
Do I need to change my website?
Not necessarily. If your leads go into a CRM or a Google Sheet, you can connect that directly. Adding a small script improves matching but isn't required.
What does it cost?
Meta doesn't charge for the API. LeadMe plans start at $11/month. Compare that with the cloud costs of running Meta's own Conversions API Gateway.
Related: How to send CRM sales to Meta · System user and access token