Landing-page experiments often fail quietly. The page loads, the form works, and dashboards receive events, but the records cannot reliably connect a conversion to the variant that produced it.
GTM is not the whole evidence chain, but it is where assignment context, event definitions, consent behavior, and conversion triggers often meet. Audit those mechanics before reading the lift chart.
1. Define the measurement contract
Before opening the container, write the minimum data contract for the experiment. Names should be stable, values should be unambiguous, and the same contract should apply to every variant.
| Field | Purpose | Example |
|---|---|---|
| experiment_id | Identifies the test | pricing_page_message_2026_08 |
| variant_id | Identifies the assigned experience | control or concise_copy |
| assignment_time | Shows when assignment became known | ISO timestamp or event time |
| page_context | Scopes the affected page or funnel | /pricing |
| conversion_name | Names the measured outcome | demo_request_completed |
2. Prove assignment exists before dependent tags fire
A conversion event with no reliable variant context cannot support a variant-level claim. Use GTM Preview and the browser data layer to inspect the real event sequence, not just the tag configuration.
- Experiment and variant values are available before the exposure event.
- Dependent GA4 events receive the intended experiment parameters.
- A route change or redirect does not erase assignment context.
- Single-page application navigation does not reuse stale variant values.
- Control traffic is explicitly identified rather than inferred from a missing value.
3. Inspect conversion triggers
A trigger should represent the business action named in the report. Button clicks are useful diagnostics, but they are rarely equivalent to a successful lead or purchase.
- The trigger fires on the intended success state, not every click or form attempt.
- Client-side validation errors do not count as conversions.
- Repeated renders, history changes, and retries do not duplicate the event.
- The trigger behaves the same way on every variant.
- The event name and parameters match the GA4 reporting definition.
- Where possible, the browser event can be reconciled with a backend or destination-system record.
4. Check consent and sequencing
Consent settings can change whether tags run, when they run, and which population is visible in analytics. The experiment may still assign a variant while GA4 remains unavailable.
- Default consent state is set before tags that depend on it.
- Consent updates occur once and are visible in Preview.
- Experiment exposure and conversion behavior is understood for denied and granted states.
- The report does not silently mix observed analytics users with all assigned visitors.
5. Compare GTM versions with the test window
A current container preview does not prove that the same configuration ran last week. Review published versions and note every relevant change during the experiment window.
| Change | Reporting consequence |
|---|---|
| Conversion trigger changed | Split the window or explain which dates use each definition. |
| Experiment parameter renamed | Reconcile both parameter names before aggregating. |
| Consent configuration changed | Expect a population shift and compare pre/post periods. |
| Tag duplicated or removed | Treat affected counts as suspect until independently reconciled. |
| Landing-page route changed | Confirm the new route still receives assignment and conversion context. |
6. Capture browser evidence
Configuration screenshots are not enough. Record at least one controlled path through each variant and preserve the event sequence that supports the audit.
- GTM Preview event timeline for control and treatment.
- Data-layer values at exposure and conversion.
- GA4 DebugView or equivalent event receipt where appropriate.
- Network request evidence for critical events.
- Container version, test URL, timestamp, consent state, and browser context.
- A negative check proving the conversion does not fire on a failed or incomplete action.
Turn the audit into a reporting decision
The output should tell the reporting team what the evidence permits, not merely list tags.