Conversion API & Pixel Tracking Implementation for Google, Meta, TikTok, LinkedIn, Criteo and Outbrain
Browser pixels lose signals to ad blockers and consent failures; platforms count twice or not at all. We build the hybrid path of pixel plus conversion API, deduplicated and consent-aware.
- GTM Server-Side
- stape.io
- Meta Conversions API
- Google Enhanced Conversions
- TikTok Events API
- LinkedIn Conversions API
Every ads platform accepts conversions on two paths: a browser pixel and a server-side API. Most setups use only the first and wonder about the gap: ad blockers and ITP filter signals, consent failures tear holes, and the platform optimises on a remainder.
The second mistake is the opposite: both paths active but without a shared event ID. Then every conversion counts twice, lead quality cannot be enriched, and the ROAS in the dashboard has little to do with the books. Smart Bidding optimises on those numbers anyway. Expensive.
kaputt
Pixels only
- One pixel per platform, maintained separately
- Ad blockers and ITP filter signals
- Consent failure means total failure
- Double counting once an API is bolted on
- Click IDs die in redirects
- PII leaves unhashed
resilient
Hybrid (Datascale)
- One event stream, all destinations
- Pixel + conversion API in parallel
- Deduplication over event IDs
- Click IDs persisted server-side
- Consent signal gates both paths
- Hashing in your own container
Architecture: one event stream from the GTM server container serves all ads destinations, deduplicated over event IDs, filtered by consent signal, PII hashed only.
What we build
Browser pixels, set up cleanly
Pixels for all relevant platforms from one GTM web container: consistent events, consistent parameters, consent-gated. No copy-paste snippet zoo in the template.
Server-side GTM as the distributor
One GTM server container, usually hosted via stape.io in the EU region, receives the event stream first-party and distributes to all destinations. A first-party endpoint instead of third-party domains.
Conversion APIs per platform
Meta CAPI, Google Enhanced Conversions, TikTok Events API, LinkedIn CAPI, plus the server paths of Criteo and Outbrain, each following that platform's pattern.
Deduplication
Shared event IDs on the browser and server paths, so every platform merges duplicate reports. Where a platform does not deduplicate, we deliberately pick one path.
Click-ID capture
gclid, ttclid, li_fat_id, fbclid, and ob_click_id are persisted server-side and survive redirects, consent banners, and long B2B cycles all the way to the conversion.
E-commerce events
Product, cart, and purchase events with the parameters catalogs and optimisation actually need: content_ids, value, currency, consistent across all platforms.
CRM and offline conversions
Closed deals flow back from the CRM into the platforms via click ID or hashed email. Lead quality becomes part of the bid signal instead of a spreadsheet footnote.
Monitoring
Event volume, match quality, and dedup rates per destination in a dashboard, with alerts on failure. Tracking that breaks silently is the most expensive state there is.
Platforms
The six core destinations are documented publicly in the ad platform hub, with event schema, identifiers, and typical mistakes per platform: Google Ads, Meta, TikTok, LinkedIn, Criteo, and Outbrain.
Microsoft Ads, Pinterest, and Snap follow the same pattern: secure the click ID, build the server path, gate it behind consent. The server container turns every further destination into an extension instead of a project.
How we work
From audit to monitoring
Audit. Inventory across all destinations: what fires, what is missing, what double-counts, what bypasses consent. The result is a prioritised fix list with effort estimates.
Architecture. Event map and consent map: which events, which parameters, which identifiers, which path per platform. Building starts only once that document stands.
Implementation. GTM web and server containers built to spec: tags, clients, transformations, hashing. Your dev team delivers dataLayer events per the tracking plan; we review.
Validation. Event-by-event QA against the event map, dedup checks per platform, consent-flow tests in both states. Sign-off with a documented QA report.
Monitoring. Dashboard and alerts go live with the sign-off. Platform changes like new consent requirements arrive as a change, not as a surprise.
Deliverables
Concept
- Event map across all platforms (events, parameters, identifiers, path)
- Consent map: which signal gates which tag on which path
- Tracking plan for your dev team, directly implementable
Implementation
- GTM web container setup (tags, triggers, variables)
- GTM server container setup including the hosting decision
- Conversion-API connection per platform with deduplication
Operations
- QA report with event-by-event sign-off
- Monitoring dashboard with alerts per destination
- Handover documentation for team and privacy officer
Related integrations
Every destination has its own setup page with event schema, identifier reference, and debugging checklist: Google Ads, Meta, TikTok, LinkedIn, Criteo, Outbrain. The infrastructure behind them: GTM Server-Side and stape.io.
Engagement depths
Three depths. Clear scopes.
No retainer trap.
Audit Sprint
We audit what is wrong. Prioritised report + action plan.
plus statutory VAT
Included
- Full analysis of the existing setup
- Prioritised report with concrete actions
- 90-minute walkthrough with your team
Not included
- Implementation (follows in the Build Sprint)
- Code in your app or website
When it fits
When the setup runs but the numbers are questioned internally.
Cross-service entry point. Fixed price depends on scope.
Request an Audit Sprint →Build Sprint
Fresh build or restructure, built to spec.
plus statutory VAT
Included
- Tracking and data architecture to a blueprint
- Server-side setup + Consent Mode V2
- QA, handover and support from Munich
Not included
- Campaign execution, media buying, creative
- Tool licences (billed directly, no markup)
When it fits
When a clean rebuild beats patching in production.
Typical builds €8,500–50,000 depending on service and scope.
Discuss a Build Sprint →Managed Evolution
Ongoing partnership. Analytics as a product.
plus statutory VAT
Included
- Monthly development + roadmap
- QA on every release deploy
- Slack support, < 4 h response (Mon–Fri)
- Monthly report + executive summary
Not included
- 24/7 on-call rotation
- Campaign operations
When it fits
When analytics has to keep growing with you.
Monthly cancellation after the minimum term.
Request Managed Evolution →All prices net, plus statutory VAT. For companies in Germany, Austria and Switzerland.
Why do our conversions count twice?
Almost always because pixel and conversion API run in parallel without carrying the same event ID on both paths. The platform cannot deduplicate and counts both reports. That shared event ID is the first checkpoint in every tracking audit.
Do you also cover Microsoft Ads, Pinterest, or Snap?
Yes, following the same pattern: secure the click ID, send events from the server container, gate everything behind the consent signal. The six core platforms are documented publicly in the catalog; further destinations join per project.
What does the entry cost?
The tracking audit runs as an Audit Sprint at a fixed price from €2,400 net, delivered in 10 working days. The result is a prioritised finding across all ads destinations: what fires, what double-counts, what bypasses consent. Then you decide on the build.
Do you run the campaigns too?
No. We build the measurement and data layer your campaigns run on; media buying and ads operations stay with your team or media agency. Exactly that separation keeps our numbers credible.
Next step
Do your conversions arrive in the platforms?
Tracking audit as an Audit Sprint: fixed price from €2,400 net, delivered in 10 working days. Pixels, APIs, and deduplication checked across all destinations, with a prioritised fix list. No follow-up contract, no retainer.