Meta CAPI, Google Enhanced Conversions, and TikTok Events API: three separate systems
These solutions send data to different advertising platforms. They are not interchangeable APIs: implement only the channels the business uses, then validate consent, deduplication, and data quality for each integration.
Decision criteria
| Parameter | Meta CAPI | Google Enhanced Conversions | TikTok Events API |
|---|---|---|---|
| Destination | Meta Ads | Google Ads | TikTok Ads |
| Primary role | server, web, app, offline, and CRM events | supplement measurement with first-party data | web, app, offline, and CRM events |
| Browser + server | Meta recommends Pixel with CAPI for web events | supplements a conversion tag; method varies | TikTok recommends Pixel + Events API for websites |
| Deduplication | for duplicate browser/server events | transaction ID and method-specific rules | for duplicate Pixel/API events |
| Hashed data | parameters under Meta rules | first-party customer data, SHA-256 | parameters under TikTok rules |
| Validation | Events Manager and diagnostics | Enhanced Conversions diagnostics | Events Manager and diagnostics |
| Consent | applicable law and Meta terms | Google customer data policies and consent parameters | applicable law and TikTok terms |
A different transmission path, not a bypass
Server/API connections rely less on browser JavaScript and can supplement browser events. ATT, platform controls, consent choices, connectivity, and data-processing rules still affect what can be collected and used.
Deduplication is for actual duplicates
When one purchase is sent from browser and server, use the same event identifier under platform guidance. Otherwise one event may count twice. Mechanically merging different events also creates errors.
Hashing is not anonymization
An email or phone hash is still used for matching. A lawful basis, clear notice, consent configuration, and data minimization may be required. This is technical information, not legal advice.
Validate after launch
Reconcile Purchase count and value with the backend; inspect duplicate rate, missing parameters, currency, event time, and consent state. Do not judge the integration from a single platform score.
Frequently asked questions
Do I need all three systems?
Only if the business advertises on all three platforms and has relevant events to send. A single channel needs only its own measurement system.
Does Meta CAPI replace the Pixel?
For website events, Meta recommends considering CAPI alongside the Pixel. Architecture depends on the website platform and event source; duplicates need deduplication.
Is Enhanced Conversions fully server-side?
Not always. Google supports tag, Data Manager, and API methods. Enhanced Conversions supplements existing measurement with hashed first-party data.
Do these APIs bypass ad blockers and ATT?
Server requests rely less on browser code, but 'bypass' is misleading. Consent, platform controls, and applicable law still apply, and full signal recovery is not guaranteed.
What EMQ score should I target?
Do not set a universal score without context. Use platform diagnostics, then separately reconcile Purchase, value, duplicates, and missing events with the backend.
How much does implementation cost?
It depends on CMS, checkout, CRM, consent platform, event count, and available integrations. Start with a data map and technical audit; a universal hour or price estimate would be inaccurate.
Need a tracking-stack review? A read-only audit can check events, value, consent, and deduplication, separating confirmed loss from assumptions.
Telegram →