Skip to content

Tag firing audit

See what each tag in your Google Tag Manager container did during a check, which dataLayer push fired it, the tags the check didn't reach, and the pushes no tag uses.

The tag firing audit compares your Google Tag Manager container with what a Hive Check saw. For each tag in the container, it says whether the tag fired during the check, and what made it fire.

It answers three questions:

  • Which tag fired on which dataLayer push.
  • Which tags the check didn't reach, and the page or journey that reaches them.
  • Which pushes no tag uses: events your site sends to the dataLayer that no tag waits for.

Before you start

The audit needs to know what is in your container. Import it on the site's Tag curation tab, from a container export or the live container. See From a Google Tag Manager export.

The import keeps each tag's triggers and filters, blocking triggers and tag sequencing. After the import, every Hive Check runs the audit against the latest import, including guided checks and the check after a Tag Manager publish.

If your container was imported before Hive read triggers, the report says "The container was imported before we read its triggers. Import it again, then run Hive Check."

Read the audit

Open a check's report and scroll to Tag firing. It lists every tag in the imported container:

ColumnWhat it shows
TagThe tag's name in your container, with its vendor and ID.
Fires onEvery page, Specific pages, Visitor action, Site event or Not running. A tag that records an outcome also shows it, such as lead, booking, sign-up or purchase.
ResultWhat happened in this check. See below.
What the check sawA short note, such as the push that fired the tag or the page that reaches it.
PagesHow many of the checked pages the result covers.

Use the buttons above the table to show only one result, for example Not reached.

The results

ResultWhat it means
FiredThe check saw the tag send its request, and a trigger in the container explains it.
Expected, didn't fireA trigger for the tag surely ran, the container loaded and consent allowed the tag, but the tag sent nothing. This is the result to look into.
Not reachedThe check didn't load the page or do the action the tag waits for. This is not a fault. The note says which page or journey reaches it.
One of several tagsMore than one tag could have sent the same request. Hive doesn't guess which one.
Not runningThe tag is paused or has no firing trigger in the container.

How a request is matched to a tag

A request belongs to a tag when:

  1. the vendor and ID match the tag;
  2. the event and the conversion label match, where both have one;
  3. one of the tag's triggers explains it: its page filters, or the dataLayer push behind it.

A push explains a request that follows it within a short window, a few seconds by default. Your provider sets this window for every check.

When several tags match, the result is One of several tags.

Pushes no tag uses, and hits no tag sent

Under the table, two lists may appear:

  • Events no tag acts on: dataLayer events your site pushes, with no tag waiting for them. They may be events you meant to track, or events you can stop sending.
  • Hits no container tag sent: requests that look like tags but didn't come from your container. They were sent In the page code, or When the page loads by another script.

Reach more tags

Tags that wait for a visitor action or a later page show Not reached until a check gets there. To reach them:

  • add the page under Extra pages to check on the site's Schedule tab, and set What this site is for. See Journeys;
  • add a journey that clicks through to the page;
  • for a site behind bot protection, walk the journey yourself in a guided check.

Where else it shows

The audit's results also appear in:

  • the register's Observed in this check, and the last time drift was seen, on the Tag curation tab;
  • the check's PDF, the tag register workbook and the compliance report;
  • the remediation plan.

Can't find what you need? Contact support