Server-side conversion events for every platform - after cookies and ATT broke the pixel.
Recover the signalbrowsers lost.
Here is the RGM Conversions API stack - the practitioner guide to server-side event tracking. Meta, Google, TikTok, Snap, LinkedIn, Pinterest and Reddit, with event deduplication and the match quality that decides how many conversions you actually recover. Start with a pillar, explore the periodic table, or filter the index.
How to read this stack: CAPI is the answer to a broken pixel. Run it alongside the pixel with deduplication, and implement it through server-side GTM feeding GA4 and each ad platform.
The short answers.
Send conversions from your server, not just a pixel.
Cookies and ATT broke browser tracking.
Shared event ID counts each conversion once.
More identifiers means more attributed conversions.
Pixel + server + dedup is the complete setup.
One container forwards to every platform.
Six guides hold the roof.
- F-01CAPI ultimate guideThe full server-side conversions model.
- F-02Meta CAPIThe complete Meta implementation.
- F-03Google Enhanced ConversionsFirst-party conversion enrichment.
- F-04TikTok Events APIServer-side events for TikTok.
- F-05Event match qualityThe score that recovers conversions.
- F-06Cross-platform orchestrationOne setup, every platform.
Every method, filed.
Showing 26 of 26 methods
No method matches that filter. Search the full library — it reads every page.
This is the curated index. Search the complete collection or jump to any family above.
The periodic table of CAPI.
Why server-side pays.
The pixel tells you what the browser still allows. The Conversions API tells you what actually happened.— RGM analysis, 2026
Privacy & measurement signals, 2026 — see the full sourced set in the RGM Benchmarks compendium.
Turn events into decisions.
Detect a real effect.
RGM ToolConversion LiftCVR change to revenue.
RGM ToolIncrementality LiftTrue incremental conversions.
RGM ToolROAS CalculatorReturn on ad spend.
RGM ToolMER CalculatorBlended efficiency.
RGM ToolCAC CalculatorCost to acquire.
RGM ToolLTV CalculatorLifetime value.
RGM ToolBlended CACPaid + organic cost.
RGM ToolAOV CalculatorAverage order value.
RGM ToolChurn RateQuantify the leak.
RGM ToolCPC CalculatorCost per click.
RGM ToolCPM CalculatorCost per thousand.
Browse every calculator on the RGM tools floor, or start with the benchmarks compendium.
How to implement CAPI.
- Choose the platform APIs. Identify which conversions APIs you need - Meta, Google, TikTok, LinkedIn and others.
- Send server-side events. Send events from your server with a shared event ID so they can be matched to the pixel.
- Deduplicate against the pixel. Use the event ID to deduplicate server events against browser events.
- Maximize match quality. Send hashed first-party identifiers to raise event match quality and recovered conversions.
- Orchestrate across platforms. Standardize the schema so one server-side setup feeds every platform.
The deep guides.
The complete Meta setup.
Deep guideEvent Match QualityRecover more conversions.
Deep guideGoogle Enhanced ConversionsFirst-party enrichment.
Deep guideCross-Platform OrchestrationOne setup, every platform.
Deep guideOffline ConversionsImport CRM conversions.
Deep guideEvent DeduplicationCount each conversion once.
Pairs with: server-side GTM to deliver it and GA4 to read it. Search the full CAPI library →
The voices — top 12.
CAPI questions.
What is the Conversions API?
The Conversions API sends conversion events to ad platforms directly from your server, instead of relying only on a browser pixel. It restores signal lost to ad blockers, browser restrictions and Apple's ATT.
Why do I need CAPI?
Browser tracking is degrading - cookies are blocked and ATT cut off most mobile tracking. CAPI sends events server-side so platforms can still attribute and optimize, typically recovering a meaningful share of otherwise-lost conversions.
What is event deduplication?
When you send the same conversion from both the pixel and the server, a shared event ID lets the platform count it once. Deduplication prevents double-counting while the server event fills gaps the pixel misses.
What is event match quality?
Event match quality scores how well a platform can match your server events to a user, based on the identifiers you send. Higher match quality means more attributed conversions and better optimization.
Does CAPI replace the pixel?
No - the best setup runs both. The pixel captures browser context, the Conversions API adds server-side reliability, and deduplication keeps the count correct.
How does CAPI relate to server-side GTM?
Server-side GTM is a common way to implement CAPI - your container receives events and forwards them to each platform's Conversions API from one place.
Sources & provenance
- Privacy and measurement signals (ATT revenue impact, zero-click share, mobile share, MMM adoption, retail-media ROAS, engagement) are drawn from the RGM 2026 Benchmarks compendium, which sources each figure to Zenith, SparkToro, Contentsquare, Sellforte/Google, Skai and Databox.
- CAPI family groupings and the periodic-table layout are RGM's synthesis; every tile links to its full guide.
- Stack census — RGM analysis, June 2026; CAPI guide counts are live totals from the deployed tree.