Built to recover the data that shouldn't be missing.
Adblockers routinely drop analytics events for visitors who already consented to be tracked. Introtrace recovers those events without touching anyone who didn't consent.
The problem we saw
Marketers and analysts were making budget calls on GA4 data that was silently incomplete. Adblockers were intercepting analytics requests after visitors had already consented, before the signal ever reached GA4 or any other platform.
Attribution models were missing 25–45% of the consented audience. Conversion rates read low. Channels that looked weak were often just popular with people who block trackers, and budget moved away from them for the wrong reason.
Meanwhile bot traffic was inflating the numbers that did come through — sessions, page views, engagement rates — so the incomplete data also looked healthier than it was.
Introtrace fixes both: it recovers the signals adblockers drop and filters the bot traffic that inflates what's left.
How Introtrace came to exist
A client's GA4 numbers didn't match their server logs
GA4 was reporting 20% fewer sessions than the CDN logs showed, for visitors who had accepted the cookie banner. The consent was recorded. The analytics event never arrived.
Filter lists, not a bug
Comparing network requests across Brave, Firefox, and Chrome with uBlock Origin showed the same thing every time: requests to google-analytics.com and googletagmanager.com were being dropped client-side before they reached the network, exactly as the filter lists intended.
A proxy for just the blocked requests
The first version caught failed analytics requests and re-sent them through a first-party subdomain — nothing else. Traffic that was already getting through stayed untouched.
Running on SaaS, e-commerce, and content sites
The same script now recovers analytics, ad pixel, and CRM signals on sites ranging from indie SaaS products to multi-domain e-commerce stores.
How we approach it
Consent first, always
Introtrace never touches a visitor who hasn't consented. Your CMP runs exactly as before. We only relay signals that were legitimately triggered and then technically dropped by an adblocker.
Zero infrastructure overhead
One script tag. No server setup, no GTM reconfiguration, no migration. Signals that aren't blocked flow through as normal — we only route the ones that fail.
The actual event, not an estimate
Consent mode modelling infers what blocked traffic probably did. Introtrace recovers the real event the real visitor triggered, and sends that to GA4, Facebook Pixel, and GTM.
What Introtrace is not
Introtrace never tracks a visitor who rejected consent, and it doesn't touch your legal obligations under GDPR or CCPA — your CMP and consent banner still do that job.
It's also not server-side tracking. Server-side tracking routes all your traffic through your own server whether or not anything was blocked. Introtrace only acts on the signal that failed; everything else flows through unchanged.
The goal was never to circumvent privacy tools. It was to recover what a visitor already agreed to send, after an adblocker dropped it.
Common questions about Introtrace
Is Introtrace a tracking workaround or consent bypass?
Introtrace only relays signals from visitors who already consented, where the analytics request was technically dropped by an adblocker. It doesn't fire for a visitor who rejected consent, and your CMP or consent banner keeps working exactly as before.
Who is Introtrace built for?
Teams running GA4, GTM, Meta Pixel, or similar tools who've noticed a gap between real traffic (server logs, CDN requests) and reported analytics sessions — typically marketers, growth teams, and engineers responsible for attribution accuracy.
How is this different from consent mode modelling?
Consent mode modelling estimates what blocked traffic probably did, using statistical inference. Introtrace recovers the actual event the real visitor triggered — the signal that was sent and then dropped, not a modeled guess.
Does Introtrace replace server-side GTM?
They can run together. Server-side GTM reroutes all traffic through your own server for broader control. Introtrace is narrower by design — it only intervenes on the requests an adblocker actually blocked, with a fraction of the setup.
See it in practice
The How It Works page walks through exactly what happens for each visitor type. Or start free — no credit card required.