Skip to main content
FHAVI

Free resource

The log that turns 'the numbers are broken' into a date

Tracking fails quietly. Nobody gets an error when a tag stops firing; the first symptom is a report that looks slightly wrong three weeks later. By then the change that caused it is buried in a deploy history belonging to someone else. One line per change, written at the time, turns that investigation into a two-minute lookup.

What to log

Every change that can move a number

01

The categories worth logging

  1. Pixel or tag added, removed, paused, or renamed — including the container, not just the pixel id.
  2. GTM publish: version number, what changed, and who published it. An unpublished import and a published one are different universes.
  3. Checkout or theme deploy — the single most common cause of a step change.
  4. Consent banner change: a new CMP, a change in default state, or a new region rule.
  5. Server-side endpoint change: URL, token rotation, or a deployment of the CAPI service.
  6. Currency, tax, or shipping-setting change on the store — these move purchase value without touching tracking.
  7. App install or removal in Shopify, particularly anything that injects scripts.

Format

Six fields, no prose

02

Per line

  1. Date and time, in one timezone, stated in the header. Mixed timezones are how change logs become useless.
  2. What changed, in the vocabulary of the thing itself — 'GTM v42 published', not 'updated tracking'.
  3. Who did it.
  4. Expected effect: none, more events, fewer events, different value.
  5. Verification: what you checked afterwards and when. 'Checked at 18:00, add_to_cart fires once' is verification; 'looks fine' is not.
  6. Rollback path: the previous version number, or the commit.

Using it

The five-minute investigation this enables

03

When a number moves

  1. Find the date the series changed shape — not the date you noticed.
  2. Read the log backwards from that date for seven days.
  3. If one entry matches, test the hypothesis by reproducing the change in a test environment, not in production.
  4. If nothing matches, the cause is upstream: a platform-side change, a browser update, or an app you did not log. Add that category to the log.
  5. Record the outcome in the same log, so the next person finds the answer instead of the question.

Keep going

The rest of the library

Every checklist here is free and ungated. The research pages carry the reasoning behind them.

All resources · Research library

A number moved and nobody knows why?

Send the date range and whatever change history you have. We will isolate the break and tell you whether it is recoverable.

Prefer email? Write to md@fhavi.com