QA Ultimate Stack

Track each brand's dataLayer implementation status

Record, per brand and per event, whether the spec is not started, in progress, implemented, verified or not applicable, with a note and a date, so the rollout has one source of truth.

One matrix for the whole rollout

Rolling a dataLayer spec out across brands takes weeks and many people. The Brand status tab keeps one matrix: brands across the top, events down the side, and a status in each cell. Status is tracked per event rather than per parameter, because the question it answers is "has this brand implemented this event correctly?". The field-by-field detail comes from parity and form tests.

Brands across, events down, a status in every cell.

A grid of four events against four brands with statuses from not started to verified and N/A.

From not started to verified

  • Not started: agreed in the spec, nothing built yet.
  • In progress: a developer is working on it.
  • Implemented: the developer says it's done.
  • Verified: a parity check or a form test proved it on the live site.
  • N/A: deliberately not part of this brand's site.

Keep the difference between Implemented and Verified strict. One is a claim; the other is a test result.

Implemented is a claim. Verified is a test result.

Four status steps from not started to verified, with verified carrying evidence.

N/A is a decision, not a gap

Marking an event N/A for a brand does more than tidy the matrix: every parity check for that brand skips it. A lead-generation site marked N/A for purchase never reports purchase as missing, so the real gaps aren't buried in noise. Use it for genuine decisions, and leave a note saying why.

Marked N/A, the event stops showing as missing. Left as not started, it becomes noise.

Two panels comparing an event marked N/A, which is skipped, with one left as not started, which shows as missing.

A note and a date on every change

Each status change records a note and the time it was made. Use the note for the evidence or the blocker, such as "deployed 6 Oct; parity pending" or "waiting on checkout rebuild", so anyone opening the matrix can see why a cell says what it says.

Status, a note, and when it changed.

A status update form with the status set to implemented, a note and the update time.

ODDVX for Windows

From the page to the hit, proved.

Start free with one saved form, one page and one parity check. Premium adds batch runs, exports and scheduled QA.