Conversion API (CAPI)

A server-to-server integration that sends conversion event data directly from a business's server to an ad platform's API, bypassing the browser entirely. CAPI is the industry's primary response to structural signal loss in browser-based conversion tracking — caused by Safari ITP, iOS App Tracking Transparency (ATT), and ad blocker prevalence. As of 2026 the canonical recommendation from Meta, Google, TikTok, and Reddit is to run CAPI alongside the browser pixel in a hybrid dual-track architecture, using deduplication to prevent double-counting.

Why CAPI exists

The browser pixel — a JavaScript snippet that fires on user actions — can be intercepted, blocked, or stripped before it reaches the ad platform. The signal loss drivers in 2026 are, per Digital Applied (Jun 2026):

• Safari Intelligent Tracking Prevention (ITP): caps first-party JavaScript-set cookies at 7 days; affects all Safari users on iOS and macOS.
• Safari 26.0 Advanced Fingerprinting Protection (shipped September 15, 2025): blocks high-entropy device APIs used for browser fingerprinting.
• iOS App Tracking Transparency (ATT): the majority of iOS users opt out of cross-app tracking, removing Meta's visibility into mobile conversion activity.
• Ad blockers: 29.5% globally, 32.5% in the US, ~40% European average (as-of Q2 2025, GWI / DataReportal). Pixel miss rate across ecommerce: 25–50% of conversions untracked (vendor-aggregated estimate; not independently audited).

How it works

CAPI creates a server-to-platform connection. Instead of relying on a browser script to fire an event, the retailer's backend (or a server-side tag container) sends a structured HTTP request to the platform's API when a conversion occurs — typically on server confirmation of a transaction, not on browser page load.

Recommended architecture — hybrid dual-track: Browser pixel and CAPI run simultaneously. Meta officially recommends this approach: the pixel captures browser-native signals (fbclid, fbp cookies); CAPI captures conversions the pixel misses. Neither replaces the other. (Triple Whale, Jan 2026; Meta Developer Docs, updated May 5, 2026)

Deduplication prevents double-counting events that both pixel and CAPI fire. The deduplication key is event_id + event_name:

• Meta: Matching event_id + event_name (exact case — Purchase and purchase will NOT deduplicate, per Digital Applied (Jun 2026)) within 48 hours on the same Pixel/dataset ID.
• TikTok Events API: Same event_id + event_name, 48-hour window, plus a 5-minute minimum gap between pixel and server event arrival when both are active.
• Google Ads: No deduplication support — use web OR server-side conversion tracking, not both simultaneously. (Stape.io, updated Jun 11, 2026)

Platform variants

Meta Conversions API

The most mature and widely adopted CAPI implementation. Server events are linked to a dataset ID and processed equivalently to Pixel, Facebook SDK, or offline data events. (Meta Developer Docs, May 2026)

Required parameters for web events (missing any may cause silent event discard): action_source, client_user_agent, event_source_url. (Digital Applied (Jun 2026))

High-value parameters: hashed email (SHA-256), hashed phone number, IP address, user agent, event_id for deduplication, purchase value, currency, item data.

Recommended events for ecommerce: PageView, ViewContent, AddToCart, InitiateCheckout, Purchase. (Triple Whale, Jan 2026)

April 15, 2026: Meta launched "Meta-enabled Conversions API" — a no-cost, one-click server-side setup that mirrors all Pixel events automatically server-side. Confirmed live April 27, 2026 (Bram Van der Hallen / Edge.be via PPC Land). Limitations: web events only, no mobile app or offline events, no configuration options. (PPC Land, Apr 27, 2026)

May 2025: Meta permanently discontinued the Offline Conversions API. Offline events now use standard CAPI with action_source: physical_store. (Digital Applied (Jun 2026))

Google Enhanced Conversions

Google's server-side supplement sends hashed first-party customer data (email, name, address, phone — SHA-256) alongside conversion events to enable matching against logged-in Google accounts (Gmail, YouTube, Chrome). (Google Ads Help, fetched Aug 2026)

June 15, 2026 (breaking change): Offline conversions import and Enhanced Conversions for Leads migrated to the Data Manager API; the legacy Google Ads API path is now retired. June 2026: Enhanced Conversions for Web and Leads unified into a single feature with a simple on/off switch. (Google Ads Help, fetched Aug 2026)

Benchmark (as-of article update, [ProfitMetrics.io](https://profitmetrics.io/blog/conversion-booster-google-ads-serverside-tracking)): Client-side gtag captures ~80% of ecommerce conversions on average; server-side offline conversion import adds ~12% more attributions; Enhanced Conversions adds ~5% on web, up to ~17% on YouTube ads.

TikTok Events API

Same conceptual model as Meta CAPI. ttclid (TikTok click ID) must be captured from URL parameters and stored manually — no automatic capture. TikTok ships a Payload Converter to transform Meta CAPI payloads into TikTok's format. (Digital Applied, Jun 2026)

Reddit CAPI

Reddit launched an official Reddit for WooCommerce extension in November 2025 handling pixel + CAPI. rdt_cid click ID must be captured from the landing page URL and stored server-side. Benchmark (as-of 2026-06): Reddit's own published data — CAPI + pixel vs. pixel-only = 25% CPA reduction, 35% more unique attributed converters. (Seresa.io citing Reddit) Reddit's audience carries the highest ad-blocker overlap of any major ad platform.

Implementation paths

Path	Cost	Dev effort	Scope	Notes
Meta one-click (Apr 2026)	Free	None	Web events only	No config options; ad blockers can still detect Meta-hosted endpoint
Partner integrations (Shopify, WooCommerce, Wix, BigCommerce)	Typically free	Low	Web + platform events	Shopify via "Facebook & Instagram by Meta" app; WooCommerce via "Facebook for WooCommerce"
Server-Side GTM (sGTM) + first-party subdomain	$20–300/month infrastructure	Medium (2–4 hours setup)	Multi-platform fan-out	One stream to Meta CAPI, Google, TikTok, Pinterest simultaneously
Direct developer integration	Infra cost only	High (2–4 weeks)	All event types including mobile + offline	Most flexible; required for offline and CRM events

sGTM cost entry threshold (practitioner rule of thumb): sGTM infrastructure spend is typically justified above ~USD 5,000/month in paid media. Below that, client-side GTM + selective direct CAPI is more cost-effective. (Digital Applied, Jun 2026)

sGTM hosting costs (as-of June 2026):

• Google Cloud Run: ~$120–300/month (3-instance production minimum)
• Stape managed: from $20/month
• Self-hosted Docker (Hetzner/OVH): ~$10–30/month (highest maintenance burden)

Key architecture insight (Simo Ahava / Piwik PRO Day 2024): sGTM's primary value is data stream consolidation — a single GA4 client-side stream fans out to Meta CAPI, Google, Piwik PRO, TikTok, Pinterest, Amplitude simultaneously without additional client-side tags. sGTM transformations can selectively strip or add parameters per vendor. (Simo Ahava, Piwik PRO Day, transcript published 2025-01-23)

Benchmarks

Metric	Figure	Source	As-of
Lower cost per result, CAPI + web vs. no CAPI	17.8%	Meta official (April 15, 2026 announcement)	2026-04-15
Advertisers reporting improved ROAS post-CAPI	2/3	IAB CTV guide (October 2025)	2025-10
More tracked conversions with server-side tracking	37%	JENTIS Server-Side Tracking Report 2026 (vendor data)	2026
Conversion lift across 6 ecommerce clients (sGTM + EC)	8–33%	ProfitMetrics.io case studies	~2026
Google EC for web adds vs. client-side	+5% conversions; +17% on YouTube	ProfitMetrics.io citing Google	~2026
Additional conversions from GCLID server-side import	+12%	ProfitMetrics.io	~2026
Estimated pixel-only miss rate (ecommerce)	25–50%	Vendor-aggregated (not independently audited)	Q1–Q2 2026

Event Match Quality (EMQ)

Meta's internal score (1–10) reflecting how well server-side events can be matched to known users. Higher EMQ gives Meta's algorithm better signal for campaign optimisation. Practitioner-reported bands (Digital Applied, Jun 2026):

• Pixel-only: typically 3–6
• Hybrid + hashed email: 7–8.5
• Adding phone number: 7+ (phone number commonly available on Shopify orders but often under-sent)

What practitioners report

Deduplication failure is the #1 real-world gotcha. Shopify stores report 1.5x–3x overreporting in Meta when deduplication silently breaks — typically caused by a second pixel source (hardcoded snippet in theme.liquid, or a third-party tracking app) running alongside the native Shopify Meta app. (Shopify Community, multiple threads 2024–2026)

Shopify checkout sandbox: GTM Preview mode does not reach Shopify's sandboxed checkout. To inspect purchase events, switch the browser console to the web-pixel-sandbox-CUSTOM-[id] environment — standard dataLayer in the main console will not show checkout events. (Analytics Mania / Julius Fedorovicius, updated Aug 2026)

sGTM does not reliably bypass ad blockers. Standard sGTM container URLs are already on major filter lists (EasyList, uBlock Origin). Near-zero improvement from standard setup. Custom first-party domain + custom loader + encoded requests: 20–40% more captured events; reduces blocker exposure 60–90%. Server-hook event capture (events fired server-side before any browser script): architecturally invisible to blockers. (Seresa.io citing DataUnlocker 2025 and Conversios 2025) sGTM's genuine ROI is cookie longevity (Safari ITP bypass), data enrichment, and centralised tag management.

WordPress 6.8 speculative loading (as-of mid-2026): WordPress 6.8 introduced speculative loading that fires GA4 and Meta Pixel ghost visits on pages users haven't actually loaded — a new source of inflated view data. (Seresa.io, Jun 2026)

Clean implementation target: ±5–10% reconciliation between Shopify order count, GA4, Meta CAPI, and Google Ads. Most stores are not close to this. (ask-luca.com synthesis)

GDPR considerations

Dresden Higher Regional Court ruling (February 3, 2026): Meta's Business Tools infrastructure — covering both Pixel and CAPI — was ruled to violate GDPR when operated without a valid legal basis. Meta ordered to pay €1,500 per affected user; appeal to the Federal Court of Justice was blocked. Advertisers bear joint controller responsibility under Article 26 GDPR. Meta's one-click CAPI (which mirrors all Pixel data automatically) raises specific data-minimisation concerns for EU advertisers. (PPC Land, Apr 2026)

Server-side collection does not bypass consent requirements. CAPI can maintain measurement coverage, but must honour consent signals and documented legal purposes under GDPR/CCPA. Hashed PII (SHA-256 email, phone) is required before transmission to both Meta and Google. (IAB Post-Cookie guidance)

Standards horizon

The W3C Privacy-Preserving Attribution Working Group (chartered to November 30, 2026) is developing a browser API for aggregate, privacy-safe attribution that could eventually provide an alternative to direct server-to-platform pipelines. Privacy-Preserving Attribution: Level 1 Working Draft was updated July 25, 2026. Browser implementation at scale is not expected before 2027. (W3C PAT WG, fetched Aug 2026)

Key terms

Term	Meaning
CAPI	Conversion API — generic term for server-to-platform conversion data delivery
Meta CAPI	Meta's specific implementation; events link to a dataset ID
Enhanced Conversions	Google's server-side supplement sending hashed first-party data
Deduplication	Mechanism to prevent double-counting events from both pixel and CAPI; requires matching event_id
EMQ	Event Match Quality — Meta's 1–10 score for how well CAPI events match known users
ITP	Intelligent Tracking Prevention — Safari's cookie-limiting technology
ATT	App Tracking Transparency — Apple's iOS opt-in framework
sGTM	Server-side Google Tag Manager — container running on cloud infrastructure that receives events and fans them to multiple vendor endpoints
Dataset ID	Meta's unified identifier linking CAPI events to a single ad account source
action_source	Required CAPI parameter specifying where the event originated (website, physical_store, etc.)