[Datalayer](/about/datalayer) November 2, 2026

# dataLayer debugging in GTM: order and timing errors

How to debug dataLayer order and timing errors in GTM: late pushes, an overwritten dataLayer, single-page app routes, and consent-delayed tags.

![](/images/65d75b0ae8d69ef95785a5d6_david-pombar.webp)

**[David Pombar](/authors-guides/david-pombar)** Swiss army knife at Trackingplan

7 min read · 1632 words

When a GTM tag fires but the value is missing, the dataLayer is rarely empty. The value usually arrives, just not in time. Order and timing errors are the hardest dataLayer bugs to see, because the push looks right when you inspect it after the fact, and the tag looks right in its configuration.

This guide is about those errors: how GTM reads the dataLayer, how to read one event in Preview mode, and the four mistakes behind most of them. For the full toolset (Preview mode, extensions, the Network tab, server-side containers), see the [GTM debugging guide](/blog/gtm-debugging-guide); for the dataLayer itself, the [dataLayer guide](/blog/data-layer).

## How GTM reads the dataLayer

GTM does not read the dataLayer whenever a tag needs a value. It processes the array as a queue of messages, in the order they were pushed, and keeps its own merged model of everything pushed so far on the page.

![Timeline of seven dataLayer messages in push order, with gtm.js, gtm.dom, gtm.load and add\_to\_cart marked as event messages where triggers are checked, and the other pushes only merged into the model.](/images/gtm-datalayer-queue-timeline.webp)

Only messages with an event key are moments where triggers are checked. Everything else updates the model and waits.

Three rules follow from that, and they explain every error below:

1.  **A message with an `event` key is a moment in time.** GTM evaluates every trigger against it and fires the tags that match. A push without one only updates the model.
2.  **Variables read the model as it is at that moment.** A Data Layer Variable on a tag fired by Window Loaded sees what was pushed before Window Loaded, never what comes after.
3.  **The model lives as long as the page.** Google’s [dataLayer documentation](https://developers.google.com/tag-platform/tag-manager/datalayer) states that each variable persists only while the visitor stays on the current page. In a single-page app, that page can last the whole visit.

## Reading one event in Preview mode

[Preview mode](https://support.google.com/tagmanager/answer/6107056) opens Tag Assistant connected to your site, with a summary of every event on the left. Most debugging sessions go wrong by looking at the tag and not at the event. Pick the event first, then read three tabs in order.

![Schematic of Tag Assistant: the event summary on the left with add\_to\_cart selected, and three panels for the Tags, Variables and Data Layer tabs with the question each one answers.](/images/gtm-preview-reading-an-event.webp)

A schematic of the reading order, not a screenshot. Pushes without an event key appear in the summary as “Message”.

-   **Tags.** Did the tag fire on this event? If it fired on an earlier one, it never saw this push. If it did not fire, open it and check which trigger condition failed.
-   **Variables.** What did each variable resolve to on this event? `undefined` on the right event means a wrong key or path; a value from the previous page means the model was not updated.
-   **Data Layer.** The message itself and the merged model after it. If the key is in the message but the variable is `undefined`, compare the path character by character: the dataLayer is case-sensitive.

When Preview is not enough, the console can tell you which script pushed and when. Run this before the push happens, for example right after the page loads:

```js
(() => {
  const push = window.dataLayer.push;
  window.dataLayer.push = function (...args) {
    console.groupCollapsed('[dataLayer]', Math.round(performance.now()), 'ms',
      args[0] && args[0].event);
    console.log(args[0]);
    console.trace('pushed by');
    console.groupEnd();
    return push.apply(this, args);
  };
})();
```

The timestamp tells you whether the push came before or after the tag’s event; the trace points at the file that sent it.

## Error 1: the push lands after the tag fires

The most common one. The page loads, the tag fires on Page View or Window Loaded, and the order data arrives a moment later, pushed without an event of its own.

![Two timelines. Broken: Container Loaded, Window Loaded, tag fires and reads undefined, then the ecommerce data is pushed. Fixed: Container Loaded, Window Loaded, a purchase push with event and ecommerce, then the tag fires and reads the order ID.](/images/gtm-push-after-tag-fires.webp)

The same push and the same tag. Moving the trigger to the push’s own event is the whole fix.

In Preview, the symptom is a tag that fired on Window Loaded with an empty variable, followed by a “Message” that carries the value. The fix is to give the push an `event` key and fire the tag on that Custom Event. Waiting for a later page event, or adding a delay, only moves the race somewhere else.

The opposite case also happens: a push that goes out before GTM loads, then a page template that pushes again with an incomplete object. In the Data Layer tab, the second message overwrites every key it repeats, empty values included.

## Error 2: something overwrites the dataLayer

Google’s documentation is direct about this one: never overwrite or re-assign `window.dataLayer`. Yet `dataLayer = []` survives in old snippets, CMS plugins, and copied examples.

![Side-by-side code: dataLayer = \[\] marked as breaking, with what happens before and after GTM loads, and window.dataLayer = window.dataLayer || \[\] marked as safe.](/images/gtm-datalayer-overwrite.webp)

What the assignment does depends on when it runs. Neither case throws an error.

If the assignment runs before GTM loads, it erases what was pushed earlier: consent defaults, page data, user state. If it runs after, it replaces the array GTM is listening to, and every later push goes to an array nobody reads. In Preview, the second case looks like events that never appear, from one point of the page on.

To find it, search the site’s scripts for `dataLayer = [` and `dataLayer=[`, including third-party plugins. A quick tell in the console: once GTM has loaded, it handles `window.dataLayer.push` with its own function, so if `window.dataLayer.push.toString()` shows `[native code]`, the array was most likely replaced. The fix is one line at the top of every script that touches it: `window.dataLayer = window.dataLayer || [];`.

## Error 3: route changes in single-page apps

In a single-page app, the URL changes without a page load. GTM loaded once, the Container Loaded event fired once, and the model still holds the first page’s values.

![Sequence of a single-page app: load of a category page with page data pushed, a route change to a product page with no reload where page tags do not fire or read stale values, and the fix of pushing new page data with a virtual\_page\_view event.](/images/gtm-spa-route-change.webp)

The route changes, the model does not. Every route change needs its own push.

Two symptoms follow. Tags triggered on page view do not fire on the new route. Tags that do fire, on a click or a custom event, read values from the previous route: a `pageType` of `"category"` on a product page, or an `ecommerce` object from a product the visitor left.

The fix is a push on every route change, with its own event and every key the previous route set, reset or replaced. GTM’s [History Change trigger](https://support.google.com/tagmanager/answer/7679322) fires on `pushState` and fragment changes and is useful as a fallback, but it carries no page data: if the app has not pushed the new values yet, the tag reads the old ones.

## Error 4: tags waiting on consent

Consent adds a second clock to the dataLayer. The consent state changes when the visitor answers the banner, which can be before, during, or long after the events that matter.

![Sequence: consent default with ad\_storage denied, a purchase pushed on load, a Meta tag blocked for lack of consent, the visitor accepting, and no purchase sent because nothing re-fires the trigger.](/images/gtm-consent-delayed-tags.webp)

An illustrative sequence. Accepting later does not replay the triggers that already fired.

GTM [consent settings](https://support.google.com/tagmanager/answer/10718549) make the timing explicit. A tag that requires additional consent fires only if every listed consent type is granted when the tag is triggered. If the visitor has not answered yet, the tag is blocked on that event, and granting consent afterwards does not replay it. Tags with built-in consent checks, such as Google’s, behave differently: they adjust what they send to the consent state.

Two order problems are common. The banner sets its defaults after other tags have already fired, instead of on the Consent Initialization trigger, which exists to apply consent settings before any other trigger. And conversion events fire on the page load while the banner is still open. Whether a conversion from before consent should ever be sent is a legal decision, not a GTM one. The debugging question is narrower: does each path (accept before, accept after, decline) behave as designed?

## A debugging order that works

When a value is missing in a tag, go through these in order. Each step rules out one of the errors above.

1.  **Find the event the tag fired on** in Preview’s summary, not the event you expected.
2.  **Check whether the value was in the model at that event** in the Data Layer tab. If it arrived later, it is Error 1.
3.  **Check whether later events appear at all.** If they stop at some point of the page, look for Error 2.
4.  **Change route or step without reloading** and repeat. Stale values point to Error 3.
5.  **Repeat with each consent answer.** A tag that only works after a reload with consent is Error 4.

Then make it stick. Every fix is a change to the order of a page, and the next release can undo it. The checks to keep on every release are in the [dataLayer validation guide](/guides/datalayer-validation). After release, Trackingplan watches the hits of real visitors and catches missing properties, dead tags, duplicate fires, and broken triggers in the wild, with links to the affected hits; more on the [monitoring page](/landings/monitoring).

## Frequently asked questions

### Why does my GTM tag fire but the dataLayer value is empty?

Almost always because the tag fired on an event that came before the push. A Data Layer Variable reads the value GTM has at the moment of the event that fires the tag. Give the push its own `event` key and fire the tag on that Custom Event.

### Is it wrong to write dataLayer = \[\] on my site?

Yes. Before GTM loads, it erases anything pushed earlier, such as consent defaults or page data. After GTM loads, it replaces the array GTM listens to, so later pushes are never processed. Use `window.dataLayer = window.dataLayer || []` instead.

### How do I track route changes in a single-page app with GTM?

Push the new page data with its own event on every route change, for example `virtual_page_view`, reset the keys the previous page set, and fire page tags on that event. The History Change trigger fires on `pushState` and fragment changes, but it carries no page data of its own.

### Why does a tag not fire after the visitor accepts cookies?

A tag that requires additional consent fires only if every listed consent type is granted when its trigger fires. If the trigger fired before the visitor accepted, the tag was blocked then, and accepting later does not replay that trigger.

Part of[Unlocking Your Data Layer A Guide for 2026](/blog/data-layer)

On this page

1.  [*01*How GTM reads the dataLayer](#how-gtm-reads-the-datalayer)
2.  [*02*Reading one event in Preview mode](#reading-one-event-in-preview-mode)
3.  [*03*Error 1: the push lands after the tag fires](#error-1-the-push-lands-after-the-tag-fires)
4.  [*04*Error 2: something overwrites the dataLayer](#error-2-something-overwrites-the-datalayer)
5.  [*05*Error 3: route changes in single-page apps](#error-3-route-changes-in-single-page-apps)
6.  [*06*Error 4: tags waiting on consent](#error-4-tags-waiting-on-consent)
7.  [*07*A debugging order that works](#a-debugging-order-that-works)
8.  [*08*Frequently asked questions](#frequently-asked-questions)

**Stop babysitting tags**

Trackingplan audits your real user data around the clock and flags issues before they cost you.

[Start free trial →](https://app.trackingplan.com/signup)

![](/images/65d75b0ae8d69ef95785a5d6_david-pombar.webp)

**David Pombar** Swiss army knife at Trackingplan

Read more from David, a Senior Product Strategist with 18+ years in digital product development and an atypical error detection knack.

Share Copy link [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.trackingplan.com%2Fguides%2Fdatalayer-debugging-gtm) [X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.trackingplan.com%2Fguides%2Fdatalayer-debugging-gtm&text=dataLayer%20debugging%20in%20GTM%3A%20order%20and%20timing%20errors)

Read next

[All Guides →](/guides)

-   [
    
    16 minAnalytics ImplementationOctober 14, 2026
    
    ### GTM debugging: manual methods vs continuous monitoring
    
    How to debug Google Tag Manager with Preview Mode, extensions, the Network tab and server-side preview, and when continuous monitoring takes over.
    
    by **David Pombar**](/blog/gtm-debugging-guide)
-   [
    
    7 minDatalayerNovember 2, 2026
    
    ### dataLayer validation: what to check before every release
    
    What to check in the dataLayer on every push, and how to catch renamed keys, type changes, and missing fields before they reach GA4, ads, or the warehouse.
    
    by **David Pombar**](/guides/datalayer-validation)
-   [
    
    7 minDatalayerNovember 2, 2026
    
    ### GA4 ecommerce dataLayer, event by event
    
    The dataLayer push for each GA4 ecommerce event, from view\_item\_list to purchase: items, currency and value, the fields that go missing, and the tests.
    
    by **David Pombar**](/guides/ga4-ecommerce-datalayer)

Trackingplan

## See everything. Miss nothing.

Your implementations audited around the clock with real-time, real-user data. Real-time alerts about errors or changes in your data, campaigns, pixels, privacy and consent. Let AI flag issues before they cost you.

[Start free trial →](https://app.trackingplan.com/signup) [Book a demo](/demo)