Recall the UTM QA checks that prevent common campaign reporting defects.
battlecard comparison Allowed values What are the two UTM fields that should almost never be free text? Source and medium. These fields drive channel rollups, so variation here creates reporting aliases. Reflex vs move A stakeholder wants a custom source value for one campaign. What is the move? Protect reporting-critical fields first; use exceptions intentionally. Objection "The link opens, so tracking is fine." Launch QA pressure, five minutes before send. Your line Opening is only the first check. I also need to confirm the redirect preserves UTMs and the test click lands in reporting. Treating page load as tracking QA…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in