GA4 audit · debugging · setup

GA4 and GTM ecommerce tracking, audited and rebuilt where it is wrong

Most GA4 properties are installed, not implemented. We put in the standard ecommerce event set, wire it through GTM, and reconcile it against your back office before anyone builds a report on top.

Fixed scope, quoted before we start
Standard ecommerce event setReconciled with your back officeDocumented for your team

GA4 and GTM setup at a glance

Service
GA4 audit, debugging and standard ecommerce implementation
Price
Scoped and quoted after we have seen the property
Covers
Data layer, standard ecommerce events, purchase and revenue, key events, marketing tags
Platforms
Shopify, WooCommerce, Google Tag Manager
You get
One container, the standard event set, and GA4 reconciled against your orders
After the fix
Clean GA4 is the prerequisite for the BigQuery export and everything built on it

What a GA4 audit usually turns up

GA4 rarely fails loudly. It just quietly reports a version of your business that is not quite true.

purchase never arrives, or arrives without revenue
Events fire twice, so sessions and conversions are inflated
add_to_cart and begin_checkout missing, so the funnel has holes
Marketing tags and pixels scattered across theme code instead of GTM
GA4 numbers and store numbers differ by an amount nobody can explain
Reports built on top of events that were never verified

What the GA4 and GTM work covers

Data layer reviewedWe check what your store actually exposes before deciding what GTM can pick up.
Standard ecommerce eventsview_item, add_to_cart, begin_checkout and purchase, with items, value and currency in the shape GA4 expects.
GTM container tidiedTags, triggers and variables organised so the next person can read them, and marketing pixels moved out of theme code.
Purchase and revenue verifiedReconciled against real orders in your back office, not against another analytics tool.
Duplicates removedDouble-firing tags and overlapping installations found and cleaned out.
DocumentationA short written map of what fires where, so your team is not guessing in six months.

How it runs

What a GA4 and GTM setup costs

  1. 01

    Access

    GA4, GTM, store admin and any existing tracking documentation.

  2. 02

    Audit

    We record what the current setup sends on a real purchase journey.

  3. 03

    Implement

    Data layer, events and container structure put right.

  4. 04

    Verify

    Checked against real orders, documented, handed over.

Scoped and quotedGA4 / GTM ecommerce tracking
Describe your case
  • Fixed scope agreed in writing first
  • Data layer review
  • Standard ecommerce event set
  • GTM container structure
  • Verification against real orders
  • Written tracking map

Price depends on the platform, the state of the current container and how many marketing tags need relocating. We look first, quote second, and the quote is fixed.

FAQ

GA4 setup, audit and debugging questions

What does a GA4 audit include?

We check the property configuration, the container, the data layer, the standard ecommerce events, purchase and revenue, key events, consent behaviour and UTM usage, then reconcile what GA4 reports against your back office. You get the list of what is wrong before anything is changed.

Why is my GA4 purchase event not working?

The usual causes are the event firing before the data layer is populated, firing on only one of several routes to the thank-you page, or being blocked for the share of visitors who decline consent. The report looks the same in all three cases.

What are the standard GA4 ecommerce events?

The set Google defines for a transactional store, from product views through add to cart and checkout to purchase. We implement that set rather than a custom naming scheme, because every tool downstream expects it.

Can you fix GA4 without rebuilding my container?

Usually yes. We prefer removing duplicate tags and correcting the ones that exist to replacing a container people already know. A rebuild happens only when the existing one cannot be made to report correctly, and we say so first.

Do you set up GA4 key events and conversions in Google Ads?

Key events are part of this work. Whether they are imported into Google Ads or tracked there natively is a separate decision, and counting both at once is what makes an account report double.

Will historical GA4 data be corrected?

No. GA4 does not restate what it already collected. The fix applies from the day it ships, which is why we reconcile forward against your store rather than backwards against old reports.

How does this relate to the full analytics setup?

It is the first step of it. The same validation runs inside the full setup, so a GA4 fix bought on its own is not repeated work if you continue.

If the whole stack needs standardising

A single fix stays a single fix. But if the analytics underneath turns out to be worth rebuilding, the full system deploys in about a week: validated tracking, all ad spend joined to revenue in your own BigQuery, standard dashboards and conversational analytics.

Describe what GA4 is reporting

Send the symptom, the platform and a screenshot if you have one. We come back with what we think is happening, what it would take to fix, and a fixed price, before any work starts.

We answer with a scope and a fixed price before any work starts. No access needed to reply.