GA4 · Consent Mode v2 · Server-side
I bridge the gap between full stack code and business revenue. Stop losing 30% to 50% of your conversions to ad-blockers and broken tags. Clean vanilla JS, sub-200ms INP, zero tracking debt.
// Consent Mode v2 · analytics_storage: granted
gtag('event', 'click_store', {
content_group: 'app_landing',
store: 'google_play',
link_text: 'Download',
page_locale: 'en',
});< 200 ms
INP
Native code only. Zero heavy third-party tags blocking the main thread.
> 8.0
EMQ Score
Native Web Crypto SHA-256 hashing for Meta CAPI and Google Ads.
100%
First-Party
Data collected under your own domain, immune to Apple ITP cookie drops.
Zero
Lock-In
Open-source CMP wiring with tarteaucitron.js. You own 100% of your code.
Services
The difference between tracking that “mostly works” and data you can actually base decisions on.
Data loss. Missing events, duplicates and ghost sessions skew every report.
Fragile regex. CSS selectors and regular expressions that break at every redesign.
Broken CMPs. Consent wired badly: tags blocked, or worse, fired without agreement.
Ad-blocker noise. A growing share of traffic never reaches your GA4 property.
Pure signal. Deduplicated events, named and documented in a tagging plan.
Native architecture. Events emitted by the application code, not scraped from the DOM.
Consent Mode v2. Consent drives every tag, with modeling for missing data.
Server-side resilience. First-party collection, out of reach of third-party script blockers.
Mapping of your existing tracking, gap detection and delivery of a tagging plan ready to implement.
Native events, content_group and clean conversions, reported in readable Looker Studio dashboards.
First-party collection via Cloudflare or GCP: less signal loss, better control over the data you send.
CMP integration and Consent Mode v2 wiring to measure lawfully, without sacrificing your data.
The Engineer Behind the Code
A typical start: GA4 reports 25% fewer sales than the CRM. Smart Bidding learns from the wrong numbers and spends on the wrong audiences.
I audit the tags, remove duplicate events and fire each conversion from the real server response. Then I move key events to a first-party endpoint. The gap closes. The algorithm gets clean signal again. Budget goes where revenue is.
FAQ
An agency stacks plugins and scrapes CSS classes. When a developer changes the design, the tracking breaks without a warning. Your numbers drift and nobody notices.
A tracking engineer works in your application code. Clean CustomEvents fire when something real happens, such as a successful API response. The tracking survives redesigns, keeps the page fast and stays yours.
Three things cause most of the gap. Timing gaps: the CRM records a sale when it is paid, GA4 when the page loads. Thank-you page reloads: a refresh fires the purchase event twice. Ad-blockers: they delete client-side pixels, so some sales never reach GA4.
The fix is to fire events from the server response, deduplicate with a transaction ID and send critical events from a first-party endpoint.
When a visitor refuses cookies, Consent Mode v2 still sends anonymous, cookieless pings. They carry no user ID and store nothing on the device.
Google's AI uses those pings to model the conversions you cannot see. Smart Bidding gets signal again, so your cost per acquisition stops climbing. You stay compliant because no personal data is collected without consent.
No. Done right, it makes your site faster. With Cloudflare Zaraz or Workers, tags run at the edge, not in the visitor's browser.
There is no extra client bundle, so the main thread stays free and INP stays under 200 ms. Fewer scripts in the browser also means better Core Web Vitals.