If a newsletter's main button brings more recorded visits than a text link, the difference gives the team something to investigate. It doesn't establish that button placement alone caused the result.
UTM tags can make those routes distinguishable while keeping that limitation visible.
Describe the send and the placement
For a hypothetical release newsletter, use a consistent source and email medium, one campaign value for the send, and a different content value for each placement.
Clics' Overview documents source, medium, campaign, term, and content reporting. Use only fields with a clear purpose. Keep recurring values spelled consistently and exclude personal information from URLs.
The resulting tags should be understandable without reading an internal debate about which link was expected to win.
Test arrival
Follow each link from a delivered test message. Inspect the final URL after redirects and confirm that the landing page loads with tracking installed.
In Clics, choose the relevant project, environment, and period. Overview supports aggregate UTM filters. For one controlled visit, Session Details exposes UTM metadata.
The Sessions list doesn't have UTM filters. Use it to inspect a known visit rather than expecting the same filtering surface as Overview.
Connect a defined outcome
When a configured Goal is selected, Overview switches to conversions and rate. That lets the team inspect the selected outcome in the campaign breakdowns.
Keep the goal rule consistent. A visit to a release page is a different outcome from subscribing, and a matched page goal should retain that label.
Read the visitor and conversion counts beside the rate. Sparse results deserve proportionate conclusions.
State what the comparison measures
The tags identify recorded routes. A forwarded email can retain the original values. A main button and a text link are seen in different contexts, so the groups aren't automatically comparable experimental samples.
Report the difference as an observation about tagged visits and the selected goal. Use it to choose a focused follow-up, such as checking whether the next send's link context is clear.
Retain the exact distributed URLs so a colleague can connect each result to the placement that produced its label.
Top comments (0)