← All articles

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:

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

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 dealLeadVolume signal, fast feedback
Meeting or consultation bookedScheduleA real person who engaged — filters out junk
Deal paidPurchase with value and currencyThe 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.

  1. 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.
  2. 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.
  3. Pick the events from Step 2 and tick the customer fields you have (email, phone, name, city, deal amount).
  4. Map your CRM stages to events: "Meeting booked" → Schedule, "Paid" → Purchase, "Spam" → SpamLead.
  5. 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

  1. In Events Manager → Test events, copy the test code (it looks like TEST12345).
  2. Send a test event from your integration with that code. In LeadMe, it's the Test button on the pixel page.
  3. Within a minute the event should appear in Test events with the source Server. If it does, the connection works.
  4. Then move a real test deal through your CRM stages and check that each event arrives.

Step 5: Watch the first week

Mistakes that waste the setup

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