Your Meta Pixel loses data to ad blockers and iOS restrictions. The Meta Conversions API via your own server container fills that gap — with Enhanced Matching, event dedup and full EU data residency.
Meta's own data shows it: shops with CAPI + Pixel measure 15-30% more conversions than shops with the Pixel only. The server-to-server route fills the gap left by browser blocking.
Server-side, you have access to hashed email, phone, externalID and IP — all data the Pixel can't always send. Meta's EMQ score often goes from 5-6 to 8-9.
Signed Pixel Events alone cover just 8 events. CAPI server-side has no such limit — every event is included.
The CAPI payload passes through your server in Amsterdam first. You decide which fields get sent on to Meta — PII filtering, consent check, GDPR-compliant.
We deliver a ready-to-go CAPI guide with your own GTM server container as the endpoint.
ads_management + business_management. The token is stored in your dashboard (encrypted).
event_ids that match between client and server. Meta then deduplicates automatically. No double attribution.
Meta's new EU requirements (as of March 2026) call for consent signals in every CAPI call. We handle that automatically.
All events flow through as normal. Enhanced Matching active. Full attribution.
Events are still sent, with data_processing_options set. Meta can count the event (in aggregated reporting) but can't use it for targeting or Enhanced Matching.
Your cookie banner determines which status applies. We provide a standard Consent Mode v2 integration — works with all common CMPs. Or use our own Consent Mode V2 Banner — free from Business onwards.
CAPI is included in every plan as standard. No upsell, no separate module.
No — and that's exactly the point. Running Pixel + CAPI in parallel is Meta's official recommendation. With event_id dedup, duplicate events are automatically counted as one. The Pixel covers the cases where it works (fast, real-time), CAPI fills the gap for blocked sessions.
All Meta events: Purchase, AddToCart, Lead, CompleteRegistration, Search, ViewContent, InitiateCheckout, AddPaymentInfo. Lead-gen campaigns often see the biggest gain from CAPI — that's where iOS tracking loss has the most impact.
We hash (SHA-256) email, phone and other identifiers server-side, before they go to Meta. Meta matches those hashes against its user database. Your raw PII never leaves your server. The EMQ score in Meta Events Manager shows how well the matching is working.
Each website can have its own Pixel ID + Dataset ID + Access Token. Manage every site from one dashboard.
Yes — and that's the standard. All tags run through the same GTM server container. See also Google Ads server-side for Enhanced Conversions + Dynamic Remarketing.
Enhanced Matching, Consent Mode v2, EU data residency. From €20/mo.
Start now