QA workflow

Review client pages against one dataLayer spec

Keep event definitions, implementation status and captured page evidence in one workflow.

A practical sequence

From inspection to a documented next action.

01

Define the expected events

Document each event and its required parameters. Mark genuine client-specific exceptions rather than forcing every page to emit every event.

02

Track implementation

Record each brand or client’s status against the shared template. A status entry is a project record, not automatic proof of successful tracking.

03

Compare captured evidence

Paste a captured dataLayer or use a configured read-only page capture. Compare events and parameters with the spec for that page.

04

Test the missing journeys

A page-load capture may not include events requiring interaction. Test those journeys explicitly and update the status only after review.

What the result meansA matching dataLayer does not prove that a GA4 request was sent or that a report counted the event. Inspect those stages separately.
Start free. Repeat with Premium.Free lets you work on one account, property or saved configuration per run, depending on the tool. Premium adds batches, CSV/Excel exports, report email and multiple Google accounts.

Start free

Use this workflow on one client account.

Start with Free for Windows. Review the scope and findings before expanding the run.