How to use the Campaign Tracking QA Checker.
Validate tracking against a written specification. A syntactically valid URL can still send traffic into the wrong reporting category.
Make the workflow fit your task.
Start with the tracking specification and inspect each destination, parameter and event against it. Report the expected value, observed value and correction, then test whether the resulting link still reaches the intended page.
- What you provide
- Tagged destination URLs and tracking specification.
- What you get
- Inconsistent parameters and missing tracking values.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Approved tracking: utm_medium=email. Supplied URL: https://example.com/report?format=csv&utm_medium=EmailNewsletter&utm_campaign=october.
Completed example
Finding: utm_medium uses EmailNewsletter instead of the approved email value. Corrected URL: https://example.com/report?format=csv&utm_medium=email&utm_campaign=october Preserved: destination path, functional format=csv parameter and campaign name.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Can a URL be valid but tracked incorrectly?
Yes. It may use an unapproved medium, wrong campaign label or missing event mapping while still loading normally.
Why does fixing campaign tags break the destination?
Check whether functional query parameters were removed or overwritten. Tracking edits must preserve the parameters the page needs to work.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑