Campaign URL Parameter Survival Review Framework

Copyable template

Select and copy the complete template below. With JavaScript enabled, you can edit, copy and download it in the interactive workspace.

CAMPAIGN URL PARAMETER REVIEW — WORKSHEET
Decision / launch: [what needs checking?]  Owner / reviewer / date: [roles and time]
Environment / release / route / browser: [record versions and scope]
Test permission and evidence location: [approved synthetic environment and restricted storage]
Selected parameter names: [only names needed for this test]
Expected behaviour: [which values should be present, agreed with owner]
Test ID: [synthetic, not a visitor or ad-click identifier]

OBSERVE EACH STAGE
1. Make a synthetic start URL with approved, non-sensitive values. Do not click a paid ad to test.
2. Record the entry point and each permitted server redirect response and destination, with values redacted from shared notes.
3. Observe the browser after client-side navigation and separately the URL available when the relevant tag actually executes. A final address bar alone does not prove the tag saw the same URL.
4. Compare each selected name: preserved, changed, missing, ambiguous, added or absent at the start. Record where the first observed difference occurred and what was not observed.
5. Give each open issue an owner, next check and retest date. Hold an affected release for review when the owner requires it; do not invent an automatic threshold.

SYNTHETIC ROW
Test S1 | start has utm_source=newsletter, utm_medium=email, utm_campaign=autumn | final has the same source and campaign but medium=Email | two preserved, one changed | inspect first differing hop and tag-time URL | analytics and web owners | retest after agreed fix.

COMPARISON RULE
Names and decoded values are case-sensitive. A start name occurring once with a nonblank value is expected. A missing final name is missing; a duplicated or blank final value is ambiguous. A missing or duplicated/blank start value is excluded from the expected denominator. Preserved share = preserved / expected, unavailable if expected is zero. This describes only selected names in these snapshots, not visits or attribution.

HANDOFF
Observed facts / evidence reference: [without raw URLs or values]
What remains unknown: [for example, tag-time state or an intermediate hop]
Next action / owner / date: [fill in]
Do not copy personal data, click IDs, cookies, credentials, customer URLs or sensitive query values into tickets, AI tools or exports.