
On this page
- What does a small business need set up for Meta ads?
- Which setup route fits your website?
- Which events should you send?
- How do you stop duplicate events?
- What do Meta's docs require that vendor guides skip?
- How do you test the setup?
- What are you allowed to send? Consent and health data
- What does it cost?
- When should you get help?
- Frequently asked questions
- Sources
What does a small business need set up for Meta ads?
You need two things sending the same events: the Meta Pixel in the visitor's browser and the Conversions API from your server, joined by a shared event ID. Meta calls this the Redundant setup and recommends it for advertisers who keep the pixel and can fully adopt the API. Meta says it provides performance "comparable to or better than using only the browser Pixel", because the server can report events the browser misses.
Why it matters is simple. Meta's ad delivery learns from the events you send. If a sale happens and Meta never hears about it, the campaign learns nothing from that buyer. Broken or partial tracking is the first thing we check when someone asks why their Facebook ads get clicks but no sales, and fixing it is the first job of our online ads management. This guide covers the setup itself.
Which setup route fits your website?
Choose the route by how your site is built, not by which tool is most advanced. All of them end in the same place: one browser event and one server event per action, with the same ID.
| Your site | Easiest route | What to check |
|---|---|---|
| Shopify | Facebook and Instagram app, data sharing set to Enhanced or Maximum | Shopify says Enhanced and Maximum use the pixel and the Conversions API; Standard uses the pixel only |
| WordPress or other CMS | A tracking plugin or a tag manager that supports the Conversions API | That it sends the same event ID from browser and server |
| Any site, little developer time | Meta's Conversions API Gateway | You host it in your own cloud account; Meta says the only cost is cloud or hosting fees |
| Custom-built site or a CRM | Direct integration: your server sends a POST to the Conversions API | Everything in the sections below is your job |
| Leads that close offline or on WhatsApp | Server events from your CRM | See our guide to tracking WhatsApp leads from Meta ads |
Shopify's data sharing page states that a browser ad blocker can stop the pixel, while "data sent from server to server can't be blocked by browser-based ad blockers." That sentence is the whole reason the Conversions API exists. Shopify also calls data sharing "a choice" and tells merchants to keep their privacy policy up to date.
Meta describes the Gateway as a self-serve option in Events Manager, run on AWS EKS, AWS ECS Express or GCP. It is aimed at businesses that want the Conversions API without dedicated developers. It is not free of effort: someone has to provision and watch a server.
Which events should you send?
Send the few events that stand for money or a real lead, using Meta's standard names. Meta's pixel reference lists them, including Purchase, Lead, Schedule, Contact, AddToCart, InitiateCheckout and ViewContent.
| Business | Events worth sending | Required detail |
|---|---|---|
| Online store | Purchase, InitiateCheckout, AddToCart | Meta marks currency and value as required for Purchase |
| Service business with a form | Lead | Send it only on a successful submit, not on page load |
| Clinic, salon or any booking | Schedule, or Contact for a call or chat click | Keep the name generic (see the health data limit below) |
| WhatsApp or phone sales | Contact first, then CRM stages from your server | Needs a record of which lead came from which ad |
Two to four events is plenty. Every extra event is one more thing that can silently break, and the campaign can only optimize for one of them anyway. If you are unsure which result to optimize for, read which Meta ads objective to choose.
A common mistake is firing Lead on the thank-you page's load, which counts every refresh and every visitor who lands there from a bookmark. Fire it on the successful submit, once.
How do you stop duplicate events?
Send the same event name and the same event ID from both channels. Meta's end-to-end guide sets the rules:
event_nameon the server must matcheventon the browser.event_idon the server must matcheventIDon the browser, and each unique event needs its own ID.- If Meta sees the same pair on the same pixel ID within 48 hours, it discards the later duplicate.
In practice, build the ID when the action happens, for example from the order number or a lead record ID, and put it in the browser call and in the server call. Without a shared ID, one purchase can appear as two. The 48-hour window also means an ID must not be reused: two different orders with the same ID will be merged into one.
What do Meta's docs require that vendor guides skip?
The top-ranking setup pages are mostly written by companies that sell a tracking tool, and they tend to skip the plain rules in Meta's documentation. These are the ones that break real setups.
Server events must carry browser details. Meta's customer information parameters page says client_user_agent is required for website events sent through the Conversions API. Browser events add it automatically; server events need it configured by hand. Meta also recommends sending the client IP address with every event.
Hash some fields, never hash others. Email (em) and phone (ph) must be hashed after you normalize them. The fbp and fbc browser identifiers, the client user agent and the client IP address must not be hashed. Hashing the wrong field makes it useless for matching.
Speed matters. Meta's guide says to send events in real time or within one hour, that sending more than two hours late can cause a significant performance drop, and that events delayed 24 hours or more may have significant attribution and delivery problems. A nightly batch upload for web events is the wrong design. Separately, Meta's API usage page says an event time can be up to seven days old, and that if any event in a request is older, "we return an error for the entire request and process no events."
Test code stays out of production. The Test Events tool gives you a test_event_code. Meta says to remove it from your production payload. We did not find a vendor page that makes that point as plainly as Meta does.
You will also see statistics online about how many conversions the pixel alone misses. We left them out: none of the pages we read traced the figure to a study we could verify, and your own number depends on your audience and your site.
How do you test the setup?
Test in this order, and stop at the first step that fails.
- Open Events Manager and choose your pixel, then the Test Events tab.
- Visit your site with the test tool open and trigger each event: add to cart, start checkout, submit the form.
- Check the browser event appears, with the right name and, for Purchase, a currency and value.
- Send a server event with your
test_event_codeand confirm it appears beside the browser event. - Confirm de-duplication. The same action should show as one event in your totals, not two.
- Make one real purchase or enquiry with the test code removed, and check that exactly one event is recorded.
- Check again after a plugin or theme update. Updates are when tracking silently stops, so repeat the test after any release.
If your ads send visitors to a landing page you control, the same checks belong in your pre-launch checklist for the website. The tracking row in our Meta Ads vs Google Ads comparison lists what each platform needs before spend.
What are you allowed to send? Consent and health data
Meta's rules limit what you may send, and they apply whether or not your tracking tool lets you. The Meta Business Tools Terms say you must give users "a clear and prominent notice on each web page where our pixels are used." Where informed consent is required for storing or accessing cookies or device information, the terms say you "must ensure, in a verifiable manner, that an end user provides all necessary consents."
The terms also say you must not share business tool data with Meta that includes or is based on health information or financial information, and that event and audience names "must not reflect, imply or be based on any category of information" described there. For a clinic, that means an event named BookedBotox is a problem, while a generic Schedule is not. We build and run SEO for clinics, and we treat this as a hard boundary: generic names, no treatment or condition details in event parameters or page URLs sent to Meta.
Consent law differs by country, so we do not give legal advice here. Check what applies to your visitors, keep your privacy policy accurate, and have a lawyer review any plan to send customer emails or phone numbers.
What does it cost?
Meta does not charge for the pixel or the Conversions API itself. The cost is whoever builds and maintains it. Shopify's integration sits inside the app you already use. A plugin or tag manager has its own fees. The Gateway's software cost, Meta says, is only the cloud or hosting fees. Direct integration costs developer time. We do not publish our own prices; we quote after looking at your site, your platform and your events.
When should you get help?
Get help when the numbers still look wrong after the test above, when you sell through a CRM or WhatsApp rather than a checkout, or when you are in a regulated field such as healthcare. We set up tracking as the first step of ad management, then confirm with a real test purchase or enquiry before any budget is raised. See our online ads service for how that works.
Frequently asked questions
Do I need the Conversions API if I already have the Meta Pixel?
If you run Meta ads and want them optimized for leads or purchases, add it. Meta recommends a redundant setup that sends every event through both the pixel and the Conversions API, and says that setup performs comparably to or better than the browser pixel alone. If you do not run Meta ads, the pixel alone is enough for basic measurement.
How do I stop Meta counting the same sale twice?
Send the same event_name and the same event_id from the browser and the server. Meta says that when it sees the same pair on the same pixel within 48 hours it discards the later one. Generate the ID once per event, for example from the order number, and pass it to both.
What is the easiest way to set up the Conversions API?
Use the integration your platform already has. Shopify's Facebook and Instagram app offers Enhanced and Maximum data sharing, which add the Conversions API. For other sites, a tag manager, a plugin or Meta's Conversions API Gateway are the next options. Writing your own server code is the most work and rarely needed.
What events should a small business send?
Only the ones that match money or leads: Purchase for a store, Lead or Schedule for a service business, and perhaps AddToCart and InitiateCheckout for a store. Meta marks currency and value as required for Purchase. Two to four events are easier to keep correct than twenty.
How do I test that the Conversions API works?
In Events Manager, open your pixel's Test Events tab and copy the test code. Send a server event with that code as test_event_code, then confirm it appears. Meta says to remove the code from your production requests. Then make a real test purchase or enquiry and check that one event, not two, is recorded.
Is the Conversions API allowed for a clinic or health business?
Meta's Business Tools Terms say you must not share health information or financial information with Meta through its business tools, and that event names must not reflect such information. A clinic should send generic events such as a booking click and never the treatment or condition. Ask a lawyer in your market before you send customer details.
Do I need a cookie banner for the pixel?
Meta's terms require a clear and prominent notice on every page where its pixels run. Where the law requires informed consent to store or read information on a device, they say you must be able to show that visitors gave it. What counts depends on your visitors' country, so check the local rule, and see our pre-launch checklist for how we handle consent on ad landing pages.
How long can I wait before sending a server event?
Send it in real time or within an hour. Meta says sending events more than two hours late can cause a significant performance drop, and events 24 hours or more late may have significant attribution and delivery issues. An event older than seven days makes Meta reject the whole request.
Sources
- Meta for Developers, "Conversions API End-to-End Implementation", https://developers.facebook.com/docs/marketing-api/conversions-api/guides/end-to-end-implementation (checked November 17, 2026)
- Meta for Developers, "Using the Conversions API", https://developers.facebook.com/docs/marketing-api/conversions-api/using-the-api (checked November 17, 2026)
- Meta for Developers, "Customer Information Parameters", https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/customer-information-parameters (checked November 17, 2026)
- Meta for Developers, "Meta Pixel Reference", https://developers.facebook.com/docs/meta-pixel/reference (checked November 17, 2026)
- Meta for Developers, "Conversions API Gateway", https://developers.facebook.com/documentation/ads-commerce/gateway-products/conversions-api-gateway (checked November 17, 2026)
- Meta, "Meta Business Tools Terms", https://www.facebook.com/legal/technology_terms (checked November 17, 2026)
- Shopify Help Center, "Facebook data sharing", https://help.shopify.com/en/manual/promoting-marketing/analyze-marketing/meta-data-sharing (checked November 17, 2026)



