The playbook
UTM Tracking: Worked Examples
The following UTM tracking examples illustrate how to move from an observed problem to a practical decision. They are hypothetical operating scenarios, not customer results or performance benchmarks. The central question is whether the work helps improve campaign visits with usable attribution labels without losing the context needed to judge it.
Put the task in context
Use a shared dictionary for source, medium, and campaign names, including capitalization. Keep campaign links valid and test any redirects. Do not add campaign attribution parameters to ordinary internal navigation if that would confuse the measurement system's interpretation.
Example 1: establish a usable starting point
A team begins working on UTM tracking but cannot consistently describe source and medium for the same item. The immediate task is define source medium and campaign naming rules. The team records the current state, identifies the source of each value, and resolves conflicting information before making a broader change.
The useful output is a campaign or conversion record that another person can interpret. This example does not require assuming an uplift. Success at this stage means the next decision can be made using a shared set of facts, with missing information explicitly identified.
Example 2: correct a specific failure
In a second situation, the team observes using inconsistent capitalization and labels for the same campaign. It proposes the correction: maintain a shared naming dictionary and validate links before use. Before applying that correction everywhere, the owner checks whether the same cause is present in other affected items. A common symptom alone does not prove that all items need the same repair.
| Decision | Illustrative reasoning |
|---|---|
| Observation | Using inconsistent capitalization and labels for the same campaign |
| Likely correction | Maintain a shared naming dictionary and validate links before use |
| Verification task | Build links without altering the destination's function |
| Result to inspect | Test that parameters survive the user journey |
After the change, the owner repeats the relevant task and records what happened. If the condition remains, the team returns to the evidence rather than declaring the process complete. The example illustrates a repair cycle; it does not claim a particular commercial result.
Example 3: extend a process after it works
A third team already has reliable records for a small scope and wants to expand. It compares the next group with the first: are source, medium, campaign defined in the same way, and does the intended outcome remain campaign visits with usable attribution labels? Differences are written down before the earlier process is reused.
Expansion is appropriate when the assumptions still hold and an owner can review exceptions. Where the new group has different needs, the team adapts the process and tests again. Reusing the structure is useful; reusing a conclusion without checking its conditions is much less reliable.
Apply the examples to your own work
- Write the current problem in observable terms using source.
- Choose which of the three examples matches the stage of the work.
- Complete this action first: define source medium and campaign naming rules.
- Keep the resulting evidence and review campaign visits with usable attribution labels on a consistent basis.
Choose an observation period that reflects the buying process. Immediate clicks, later inquiries, and completed sales happen at different times. Keep the attribution window and any incomplete outcomes visible when comparing campaigns.
Skip the manual steps. Let AgentixFLO run this for every client.
Start now