First touch issue tags not firing

In this guide

How to see it The usual causes A checklist for first-visit problems Server-side notes A realistic example Frequently asked questions

Check these first

If tags fire on page two but not page one, the cause is timing: consent, a data layer value or the trigger type.
Use Consent Initialization for the consent tag, set the default before the container, and trigger tags on the right event.
Debug with Preview on a fresh visit: private window, cleared cookies.

A frustrating pattern: you test your tracking, it works on the second page and not on the first. New visitors, the ones you most want to measure, are the ones whose first page is lost. This page explains the usual causes and the fixes. It sits with Google Tag Manager errors, consent updates and Google Tag Manager best practices.

How to see it

Open a private window

So there are no cookies or stored consent.

Start Preview and load your site

Use the first page, not a later one.

Read the event list on the left

Container Loaded, Consent Initialization, Initialization, Page View, DOM Ready, Window Loaded.

Check which tags fired at each step

And which show "not fired" with the reason.

For online stores

Orders from your store, back to the ad that earned them

Your store sends the order once. Open Tracked passes it on to each ad platform, cleaned and deduplicated.

The usual causes

SymptomConsent is not ready when the page view fires

Likely causeThe consent platform answers later than the page view trigger.

FixSet wait_for_update, use consent settings on tags, and fire tags again on the consent update event.

SymptomThe consent tag fires too late

Likely causeIt runs on Page View, after other tags have decided.

FixFire it on Consent Initialization – All Pages.

SymptomA tag needs a variable that does not exist yet

Likely causeA data layer value is pushed after the tag fires.

FixPush the value earlier, or trigger on an event after it is set.

SymptomA tag uses the wrong trigger type

Likely causePage View is too early for content that loads later.

FixUse DOM Ready, Window Loaded or a custom event.

SymptomFirst-party cookies are not set yet

Likely causeA tag reads a cookie that is created on this very page.

FixUse a fallback, or fire on a later event.

SymptomSingle-page app

Likely causeThe first load does not push a page view event.

FixPush one on load as well as on route changes. See single-page apps.

SymptomThe banner blocks the tag

Likely causeThe tag is held until consent and never released.

FixFire the tag after the consent update.

A checklist for first-visit problems

0 of 6 done

The consent default is above the container snippetThe consent tool's tag runs on Consent InitializationTags have consent settings, not blockers that never releaseVariables are set before the tags that read themTriggers fit when the data is readyI tested in a clean private window

Ask AI

Ask Ari instead of digging through reports

Ari reads your tracking and ad data and answers in plain words.

Server-side notes

If your first-page events reach the server but tags do not fire there, check the consent state on the incoming request and the trigger conditions in server Preview. If the first request never arrives, check whether the web tag waits for consent. See server container not receiving requests.

A realistic example

A store sees that purchases from new visitors are under-reported compared with returning ones. In Preview on a fresh visit, the Meta page view tag shows "not fired: consent". The consent platform sets the stored choice about 800 milliseconds after the container loads, and wait_for_update is 100. Raising it to 600 and firing the tag also on the consent update event fixes the first page. The change recovers first-page events for visitors who had accepted on an earlier visit, and no more data is collected for visitors who decline.

The short version

3 things to remember

Scroll and the points stack up.

If tags fire on page two but not page one, the cause is timing: consent, a data layer value or the trigger type.

Use Consent Initialization for the consent tag, set the default before the container, and trigger tags on the right event.

Debug with Preview on a fresh visit: private window, cleared cookies.

Frequently asked questions

Why do my tags not fire on the first page?

Usually consent timing, a trigger that is too early, or a variable that is not ready.

What is Consent Initialization?

A trigger type that fires before other tags, meant for consent tools.

How do I test a first visit?

In a private window with cleared cookies, in Preview.

Do single-page apps have this problem?

Yes, if they do not push a page view on first load.

Does it affect server-side events?

It can, because the web tag sends them. Check the web tags first.

Do I need spreadsheets to read my results?

No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.

Is Open Tracked different from Open Track or Open Space Track?

No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.

Fix your tracking at the source

Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.

Start free More in Guides →

Written by

The Open Tracked team

We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?

Write to us Read the docs

Was this article helpful?

Comments

Loading comments...