1. Required parameter coverage
Confirm every campaign link includes the minimum keys your reporting stack expects, usually utm_source, utm_medium, and utm_campaign.
A campaign link can route correctly and still break attribution. This UTM checker playbook gives growth and lifecycle teams a repeatable pre-launch gate to catch parameter loss and bad merge behavior before spend scales.
Confirm every campaign link includes the minimum keys your reporting stack expects, usually utm_source, utm_medium, and utm_campaign.
Validate that UTMs survive intermediate redirects, short-link expansion, and app/web fallback decisions.
Inspect the resolved destination URL to ensure no key is dropped, overwritten, or malformed after merge rules apply.
Open one real link from each major source channel to verify production behavior matches debug simulation output.
| Issue | Likely cause | Fix |
|---|---|---|
| UTMs look correct in source URL but missing on final page | Redirect step rewrites query string or strips keys. | Inspect each hop and enforce passthrough at the resolver layer. |
| Inconsistent casing and naming across teams | No shared naming convention for source/medium/campaign. | Adopt a campaign naming policy and lint links before launch. |
| Two values for the same UTM key | Stored defaults and incoming params are merged without precedence rules. | Define merge precedence and validate final output in the checker. |
| Click data does not match ad platform totals | Channel opens are routed differently than expected. | Cross-check source/referrer fields in click analytics per channel. |
Teams that validate links before launch avoid preventable attribution disputes after launch. Build this UTM checker workflow into campaign sign-off so reporting stays trustworthy as spend ramps.