Attribution Relay
Follow campaign context through a redirect chain and see where attribution can become incomplete.
TryChange Partner redirect behavior to Preserve tags, then to Drop all tags. Compare what the landing page receives.
Watch forThe default chain loses only campaign at the partner redirect, leaving partial context at the landing page.
Synthetic model of this capability; it does not recreate production.
Interactive model
Skill practicedTrace state across service boundaries
Connection to my workClickTrail documents redirect checks; this synthetic chain explores how campaign context can disappear between services.
Understand the result
A small deterministic model follows source, medium, and campaign values through three example redirect steps. Each step can preserve tags, drop the campaign, replace the source, or remove every tag. It illustrates one class of attribution gap; it does not execute ClickTrail checks or reproduce its implementation.
Controls
- Branded short link behavior
- Choose how the first redirect step treats the three example campaign tags.
- Partner redirect behavior
- Choose how the middle redirect step treats the values it receives.
- Landing page behavior
- Choose how the final step passes campaign context to the landing page.
- Reset redirect chain
- Restore the example chain, including a partner hop that drops the campaign value.
What to watch for
- The default chain loses only campaign at the partner redirect, leaving partial context at the landing page.
- Set each hop to Preserve tags and compare the complete values at arrival.
- Set an earlier hop to Drop all tags. A later hop cannot recover values that it never received.
Why it happens
This model carries three plain strings from one step to the next. A step can remove or replace values before the next destination sees them. Real attribution also depends on URL parsing, privacy and consent behavior, identity, and conversion rules, none of which this deliberately small experiment models.
How this project capability informs the model
This exercise practices tracing state across hops, locating partial loss, and explaining why a later service cannot restore values it never received. It does not run ClickTrail checks or reproduce its production redirect path.
See the broader engineering brief