Find out whether your GA4 and GTM setup is working as intended.
A structured investigation of the tags, events and consent behaviour on one Shopify or WooCommerce store. You get written findings, the evidence behind them and a clear recommendation. The audit identifies problems; it does not include fixing them.
Symptoms that usually lead here
This audit is for stores where something looks wrong but nobody is sure what. Typical starting points:
- GA4 shows fewer purchases, or less revenue, than your store's order report, and the gap has changed recently.
- Purchases appear twice in GA4, or some days show no data at all. See GA4 not tracking.
- A theme change, app install, agency handover or checkout update happened, and the numbers moved at the same time.
- Your Tag Manager container has grown over the years and nobody can say which tags still matter.
- You see two or more GA4 measurement IDs, or old Universal Analytics code, and don't know whether it is intentional.
- A consent banner was added and reported traffic dropped, or nothing changed at all, which can also be a warning sign.
If one of these is a clear, single fault, a defined tracking fix may be the better starting point. If you're not sure, the audit is designed for exactly that.
Systems inspected
Within the agreed scope, and subject to the access you give us, the audit covers:
| Area | What we look at |
|---|---|
| Storefront pages | Which Google tags, GTM containers and third-party pixels load, from where (theme code, app, plugin, GTM) and in what order |
| Google Tag Manager | Tags, triggers, variables, consent settings, paused or orphaned tags, the published version and its history |
| GA4 property | Data streams, measurement IDs, key events, ecommerce reports, filters, internal-traffic rules, cross-domain and referral settings |
| Platform integrations | Shopify customer events and app pixels, or WooCommerce plugins and theme snippets that send analytics data |
| Consent | The consent banner, default and updated consent states, and whether tags wait for them |
| Checkout and purchase path | Where the purchase event is generated and what it sends, using a test order where you agree to one |
We work with read or edit access that you grant through your own accounts (for example a GTM user and a GA4 viewer role). We never ask for passwords.
Event and configuration checks
The detail depends on your setup, but these are the checks that most often find the real problem:
- Tag deployment. Is each GA4 measurement ID loaded once, from one place? A Google tag in the theme plus the same ID in GTM, or in an app, is a common source of duplicate page views and events. See why the same GA4 tag loads twice and multiple GA4 IDs on one store.
- Legacy code. Universal Analytics stopped processing data on 1 July 2023, according to Google. Leftover UA tags do no useful work and can hide where GA4 is really installed. See Universal Analytics code on your store.
- Event names and parameters. GA4's recommended ecommerce events (
view_item,add_to_cart,begin_checkout,purchaseand others) only populate the ecommerce reports when the names and parameters follow Google's GA4 ecommerce documentation. We compare what is sent with what is expected. - dataLayer mapping. Where GTM reads values from a dataLayer, we check that variables point at the right keys, that
itemsarrays are structured as GA4 expects, and that values are numbers rather than formatted strings such as "£49.99". - Purchase payload consistency.
transaction_id,value,currency, tax, shipping and items are checked against the order they describe. A missing or repeatedtransaction_idis one of the first things we look for. See why GA4 revenue doesn't match your store. - Consent behaviour. We check what fires before a visitor chooses, what changes after they accept or reject, and whether the Consent Mode signals (
ad_storage,analytics_storage,ad_user_data,ad_personalization) are set and updated. See Consent Mode v2 checks. - Property settings. Data filters, internal-traffic rules, unwanted referrals (payment providers appearing as traffic sources) and reporting time zone and currency.
How findings are validated
Every finding is labelled with the evidence behind it, so you can tell an observation from a confirmed fault:
- Observed in code or configuration. For example, two Google tags with the same ID in the published GTM version.
- Observed in browser requests. We inspect the network requests sent to Google and other platforms, using browser developer tools, GTM Preview and Tag Assistant.
- Observed in the platform. GA4 DebugView and Realtime, and the ecommerce reports, to see what actually arrived.
- Confirmed end to end. Only possible for checkout and purchase events with a test order you approve. Without one, purchase findings are reported as unconfirmed.
Some things can't be settled by an audit. Ad blockers, browser privacy features and visitors who decline consent all reduce what GA4 can record, so a gap between GA4 and your store's order count is expected to some degree. We explain which part of a gap the evidence can account for and which part it can't.
Report deliverables
- A written findings report: each issue, its evidence, its likely effect on your data, and a severity (high, medium, low).
- A list of what was checked and what could not be checked, with the reason.
- Recommended actions in priority order, written so your developer, agency or we can act on them.
- An estimate or defined scope for any follow-on implementation. Fixing is quoted separately and only starts if you agree.
Pricing
GA4 and GTM audit
From £399
One store, one selected measurement problem or a coherent group of closely related symptoms. Written findings, severity and recommended actions.
Book a tracking diagnosticDefined tracking fix
From £495
Implementation of an agreed, contained correction, with testing evidence and a handover summary.
About tracking fixesNot included at the £399 starting scope: code or container changes, unrelated account-wide audits, Merchant Center appeals, several independently configured stores, or ongoing monitoring. A broader problem is quoted in writing before any paid work begins. See full pricing.
Introductory pricing. These are introductory prices for our current service packages. We agree the scope and price with you before work starts. Future prices may change, but an accepted quote won't change without your agreement.
FAQ
Does the audit include fixing what it finds?
No. The audit identifies and documents issues. If you want them fixed, we quote a defined fix from £495, or your own developer can use the report.
What access do you need?
Usually a user on your GTM container and viewer access to the GA4 property, added from your own accounts. For Shopify, staff access limited to the settings involved. For a purchase check, your agreement to place and refund a test order.
Will the audit make GA4 match my store's revenue exactly?
No audit can promise that. Consent choices, ad blockers, refunds, time zones and attribution all create legitimate differences. We show which differences come from faults that can be corrected.
Who does the work?
Mikael, who has worked in digital advertising and ad technology for 15 years, including seven years of GA, GTM and tagging work. See About.
How is this different from the free check?
The free check is a short look at your public pages. It can't see inside GTM or GA4 and can't confirm whether purchase tracking works. The audit can, with your access.
Not sure what's wrong?
Send us your store address. Mikael will look at the public pages and tell you what he can see, and what he can't.