Missing or wrong conversion data
Tags firing on only part of the site, duplicate purchase events, or a consent banner blocking GA4 while the ad platforms still fire.
Numbers that match the money
Working with Google Analytics 4?
Most GA4 properties that reach us were set up in a rush when Universal Analytics was switched off, and nobody has really trusted the numbers since. We work out which events are actually firing, which ones are missing, and why the dashboard disagrees with the ad platforms.
What it is
Google Analytics 4 is Google's analytics platform, rebuilt around an event model to replace Universal Analytics. Where the old version counted page views and sessions as its basic unit, the new one treats almost everything as an event with its own parameters, which is more flexible but much less familiar to anyone who learned on the old reports.
GA4 launched in beta in October 2020 and became the default property type later that year. Universal Analytics stopped collecting new data on July 1, 2024. It works alongside Google Tag Manager, consent mode v2, BigQuery, Google Ads and Search Console, and covers a website and a mobile app in the same property through separate data streams.
The honest version
No technology is all upside. This is where Google Analytics 4 earns its place and where it tends to cause trouble.
Sound familiar?
The Google Analytics 4 problems that bring people to us, and what you have once each one is fixed.
Tags firing on only part of the site, duplicate purchase events, or a consent banner blocking GA4 while the ad platforms still fire.
Numbers that match the money
The tag is in the theme but not in the checkout funnel, or GTM loads after a consent gate that most visitors never click through.
Coverage checked on every template
A GA4 property was created, but goals, audiences, custom dimensions and ecommerce events were never ported across properly.
GA4 rebuilt to match your old KPIs
Purchase events firing twice, items missing their price or currency, or refunds that never make it back into the reports.
Revenue that reconciles to your store
Privacy thresholds hiding small rows, Google signals turned off, or consent mode denying storage for most visitors.
The data that is actually there, shown
A linked project with the wrong permissions, a dataset in a region GA4 cannot write to, or streaming export silently disabled.
Daily and streaming exports landing
A server GTM container deployed without health checks, so when it fails every downstream tag quietly stops reporting.
Server tagging with alerts
What we do
Call us for one missing conversion, or hand us the whole analytics setup.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
The ad platform usually credits a conversion to its own click under its own attribution window, while GA4 applies its own model, its own consent rules and its own deduplication. A gap of twenty or thirty percent is often normal; a gap of eighty percent almost always means tags are not firing on part of the funnel or consent is blocking GA4 while the ad pixels still run.
Universal Analytics stopped collecting new data on July 1, 2024, and historical exports were shut down after that. If you have not already, export whatever historical UA data matters to you from a backup, and audit the GA4 property that replaced it against the goals, audiences and ecommerce events you relied on in the old one.
You need the full set of recommended ecommerce events firing with items arrays, consistent currency and a reliable transaction_id so GA4 can deduplicate purchases. We verify each event in DebugView, reconcile daily revenue against the store, and connect the BigQuery export so the raw data is available when a report looks wrong.
Three usual suspects: a consent banner denying analytics_storage for most visitors, privacy thresholds hiding rows with small user counts, and tags that only fire on part of the site. Each one is fixed differently, so the first job is working out which combination applies to you.
Most sites do not need it. It helps when ad blockers and tracking prevention are eating a large share of your events, when you need to redact data before it leaves your systems, or when page speed has suffered from stacked client-side tags. It also adds real infrastructure to run and monitor, so it is a decision, not a default.
Estimates are free. Tell us what the reports are doing and you get a price before any work starts.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: