Meta's free 1-click CAPI vs Headless (2026)
Meta's free 1-click Conversions API is genuinely enough for some stores. Here is the specific test for whether you need a paid tool on top of it.
Meta's free 1-click Conversions API gateway is enough for a real and growing group of Shopify stores, and pretending otherwise is the fastest way to lose a merchant's trust. It became broadly available in April 2026, it costs nothing, and it removes the developer dependency that used to make server-side tracking an engineering project. If you run a single store, advertise on Meta only, have clean traffic, and are happy reading results in Ads Manager, use the free gateway and keep the $0.
The decision turns on six questions, and the free gateway answers none of them. It forwards what your pixel already saw. It does not enrich events with hashed email, phone, or external ID. Its deduplication only holds when both copies share an event_id — unverified, you can end up counting purchases twice. It does not filter invalid traffic. And it hands you no analytics, so "which campaign is actually profitable" stays unanswerable outside Meta's own dashboard.
What the free gateway actually does
The gateway solves one problem well: it creates a server-side path from your pixel to Meta without you writing code, hosting a container, or wiring a first-party subdomain. Turn it on and browser events reach the Conversions API alongside your pixel events. That is a real improvement over a browser-only setup, and for a store that was running nothing server-side, it is most of the win.
What it does not do is add information to those events. The event that reaches Meta is the event the browser saw. No enrichment layer sits in front of it, so the identifiers Meta can match on are the same ones ITP and ad blockers were already stripping.
The six questions that decide it
Answer these in order and stop at the first "yes" — that is your answer.
| Question | Meta's free 1-click gateway$0 | Headless$0–49/mo |
|---|---|---|
| Delivery | ||
| Basic server-side delivery | Yes | Yes |
| Platforms covered | Meta only | Meta only |
| Data quality | ||
| First-party data enrichment (email, phone, external_id) | No (does not offer this) | Yes (wins this row) |
| Browser/server deduplication | Only if event_ids match — verify | Shared event_id, enforced (wins this row) |
| Bot & crawler filtering | None — forwards what the pixel saw | In the browser, before any request (wins this row) |
| What you can see afterwards | ||
| Attribution history beyond 7 days | No (does not offer this) | 90 days to unlimited (wins this row) |
| Revenue and engagement analytics | None (does not offer this) | 39 metrics, every tier (wins this row) |
The gateway does not filter crawlers either. It forwards the events your pixel already saw,
and its documentation describes no bot filtering in between, so a crawler event that reaches the
pixel reaches Meta. Headless decides earlier: the check runs first thing in the pixel, ahead of
every listener, fetch and cookie, so a rejected page never produces an event for a gateway to
forward. No analytics row, no Meta event, no request cost. The limit is the same as everywhere
else in this table — it is client-side, so a bot that spoofs its user agent and clears
navigator.webdriver still gets through, and because filtered pages are never stored there is no
"bots blocked" number to report.
Where Headless fits
Headless is not an upgrade to the free gateway. It is the same delivery layer plus the three things the gateway does not do: enrichment on every server event, deduplication you don't have to babysit — a shared event_id enforced end to end — and a 39-metric analytics layer that answers the profitability question Ads Manager cannot.
The honest reason to pick it is narrower than vendors usually claim. It is worth it when your Event Match Quality is below roughly 8.0, when you run more than one store or ad account, when you need attribution history past the 7-day cookie window, or when you need to know which campaigns profit after ad spend.
The honest reason not to: if none of those apply, the free gateway is the correct choice and you should not pay us either. Headless has a $0 tier for exactly that store — the delivery layer at no cost — and the paid tiers exist for the stores that have outgrown it.
Where Elevar, Triple Whale and Stape fit
Meta's free gateway is not the only alternative, and it is not always the right one to benchmark against. Elevar ($225/mo entry) bundles multi-platform delivery, agency workflows, and deeper Shopify-native reporting; Triple Whale has a genuinely useful free tier, with paid plans quoted by annual GMV on a 12-month term. Stape ($17/mo) is hosted tagging infrastructure you configure yourself. All three cost meaningfully more than Headless at the paid tiers, and none of them is aimed at a single-store Meta-only merchant.
If you need Google or TikTok delivery alongside Meta, an agency workflow, or client management, you are in a different category entirely and the right comparison is Headless vs Elevar and Headless vs Triple Whale, not this one.
Frequently asked questions
Is Meta's free 1-click CAPI actually free?
Yes. Meta's 1-click Conversions API gateway costs nothing to enable and ships inside the pixel, with no container, developer, or server to maintain. It became broadly available in April 2026 and reset the floor for basic server-side delivery to $0.
What does Meta's free 1-click CAPI not do?
It forwards the events your pixel already saw. It does not enrich them with first-party identifiers, gives you no analytics of its own, and does not filter invalid traffic. Deduplication against the pixel works only when both copies share an event_id — verify it in Test Events before trusting it.
Do I need both the free gateway and a paid tool?
Usually one or the other. The free gateway and a paid CAPI tool solve the same delivery problem, so running both means deduplicating between two systems. Pick the paid tool when you need enrichment, filtering, long retention, or analytics — not as an upgrade to the gateway.
How do I check my Event Match Quality before deciding?
Open Events Manager, select your pixel, and read the Event Match Quality score over the last 30 days. Below roughly 8.0 there is headroom worth paying for. At 8.5 or above on clean traffic, the free gateway is likely enough.