Check · C03 · Tracking core

dataLayer audit: initialised, populated, before the container

The dataLayer is the interface between website and tag manager. Without it, or with an empty one, tags hang on CSS selectors and break with the next redesign.

What we check

The check reads the delivered HTML for window.dataLayer being created and at least one push() following it. Both spellings count: the explicit window.dataLayer = window.dataLayer || [] and the w[l]=w[l]||[] from the official GTM snippet. A push without a visible initialisation counts as populated, because without initialisation the browser would throw.

What the scan cannot see: pushes from lazy-loaded JavaScript bundles, events that only exist after clicks, and whether the parameters follow GA4 notation. That needs a browser. The deep scan brings one for view_item on shops; everything else is audit work.

Why it matters

The dataLayer is the contract between website and tag manager. Without it, triggers hang on CSS classes and DOM paths, which works exactly until the next redesign, then conversion measurement breaks and nobody notices, because GA4 simply counts less. With a dataLayer the events stay stable no matter what the frontend looks like. Redesign, new theme, new shop: same events. Structure and naming conventions are covered in the guide What is a dataLayer?

Common causes

GTM was installed without a dataLayer concept, all triggers hang on click selectors instead of events.
The theme initialises the dataLayer after the GTM snippet and overwrites the events already collected.
A shop system ships its own dataLayer under a different name, GTM listens to the standard one.
Events are only pushed on some templates, checkout or forms stay silent.

The fix

Initialise window.dataLayer before the GTM container and never reassign it afterwards. One push() per business event with GA4 names and parameters (event, ecommerce.items, value, currency), written down in a measurement plan. Then verify in GTM preview mode that every event arrives exactly once.

Matching template

GA4 and Google Ads Consent Mapping

Documents which data flows from GA4 to Google Ads and which signal governs each flow.

Get the worksheet →

Check it yourself first

The Tracking Check tests this point along with all the others, in seconds.

Start the Tracking Check →

Asked often

Why does the check report "no dataLayer" although GTM runs?

The scan only reads the delivered HTML. The official GTM snippet creates the dataLayer as w[l]=w[l]||[], which the check recognises since September 2026. If a lazy-loaded bundle (SPA, shop theme) creates the dataLayer later, the static scan cannot see it. Then check the browser console: window.dataLayer.

Is a dataLayer with gtm.js events enough?

No. The events gtm.js, gtm.dom and gtm.load are written by the container itself. What counts are your business events: view_item, add_to_cart, generate_lead, purchase, with parameters in GA4 notation. Whether view_item arrives on product pages is what the deep scan tests on detected shops; the rest is audit territory.

How does this differ from the "duplicate Google IDs" finding?

The dataLayer check asks whether an interface exists. Duplicate Google IDs asks whether the same measurement arrives twice. Both are tracking-core findings with different causes: a missing concept versus a leftover.

The fix, delivered

Wired up in days, not sprints.

Findings from the Tracking Check go into a ranked sequence with effort estimates in the Audit Sprint, every module with an acceptance criterion.

To the service Request an Audit Sprint