MANTISTracking specialist
ServicesResourcesGet in touch
MANTIS

MANTIS: Measurement and Tracking Infrastructure SystemMeasurement and Tracking Infrastructure System

Tracking and attribution infrastructure for businesses running paid ads, so your CRM, ad platforms, and reporting all tell the same story.

Services

  • Tracking Audit
  • Tracking Architecture
  • Offline Conversions
  • Lead Automation
  • Audience Suppression

More

  • Resources
  • Get in touch
  • Privacy Policy
© 2026 MANTISTracking & Attribution InfrastructureZagreb, Croatia
Tracking & Attribution

Tracking & Attribution Infrastructure: Meta says 20 leads.
Your CRM shows 16.

The gap hides in a layer nobody owns, and the ad algorithm is learning from numbers you don't trust. I find the cause and build the tracking layer that feeds real sales back to Google and Meta, so your campaigns find customers, not just form fills.

For lead-gen businesses spending real money on Google and Meta ads, with a CRM that's supposed to agree with the ad platforms.

Get in touchSee my services

Tracking & Attribution

Server-side GTM, Meta CAPI, and Google offline conversions, built so your ad platforms see the full picture.

CRM Automation

Make.com and n8n pipelines that route leads and closed-sale data where it needs to go, without manual work.

What I work with

The platforms the work is actually built on.

Server-Side GTM
Meta CAPI
Google Ads OCT
Consent Mode v2
Google Analytics 4
Make.com & n8n
How I work

My process

01

Diagnostic Audit

I map where your data is breaking: mismatches between Meta, GA4, and CRM, deduplication errors, attribution gaps.

02

Infrastructure Design

I design a GTM container and DataLayer structure that fits your CRM and ad platforms specifically.

03

Implementation

Server-side GTM, Meta CAPI, Google offline conversion tracking, and any automation pipelines between systems.

04

Revenue back to ad platforms

CRM closed-sale data routes back to Google and Meta so the algorithms learn from actual buyers, not just form submissions.

Is this for you?

  • Meta, GA4, and your CRM each report a different number for the same campaign
  • Your team thinks leads are being lost or forms are broken
  • Your ad algorithms optimise for form fills, not closed deals
  • CRM data never makes it back to Google or Meta
  • Numbers dropped after iOS 14 and never recovered
  • You run ads across multiple brands or markets
  • Converted customers keep seeing your acquisition ads
Get in touch

Common questions

Why do Meta and my CRM show different lead counts?+

Usually a deduplication issue: the browser pixel and server-side CAPI both fire for the same event without a shared event_id, so Meta counts it twice. The fix is generating one event_id per conversion and passing it to both events, through server-side GTM or whatever CAPI setup you already run.

What is offline conversion tracking?+

Sending your CRM's closed-sale data back to Google and Meta so the ad algorithms know which clicks actually became customers, not just leads. It shifts optimisation from cost-per-lead to cost-per-sale.

Why do ad algorithms optimise for leads instead of customers?+

Ad platforms optimise toward whatever conversion signal you send them. If you only send lead form submissions, they find more people likely to fill out forms, not necessarily buyers. Routing closed-sale data from your CRM back to Google and Meta via offline conversion tracking shifts the algorithm to optimise for actual revenue.

Why is my conversion data incomplete even though the pixel is installed?+

Browser-based tracking gets stripped in transit: ad blockers stop the pixel from loading, Safari limits cookie lifetime, iOS removes identifiers, and consent banners block tags before they fire. The conversions still happen; the ad platform just never hears about them. Server-side tracking sends events from your own server instead of the user's browser, which recovers part of that loss. Advanced Consent Mode v2 can add modelled conversions for users who decline, once Google's eligibility requirements are met. Neither recovers everything, but together they close a meaningful share of the gap.

Why did my ad tracking numbers drop after iOS 14?+

Two separate Apple changes reduced the signal available to ad platforms: App Tracking Transparency, enforced from iOS 14.5, limited app-level tracking identifiers like the IDFA, and Safari's tracking protections separately limit cookies and browser identifiers. A first-party, server-side setup improves signal durability, data control, and event delivery, but it cannot recover every conversion or identifier removed by browser, device, or consent restrictions.

Why do converted customers keep seeing my acquisition ads?+

Because your CRM data isn't syncing back to the ad platform fast enough to exclude them. Automating a CRM-to-Meta Custom Audience or Google Customer Match sync means converted customers are moved out of acquisition targeting the moment they close, and into retention or upsell segments instead.