Get approved campaign information to the point that needs it.
A campaign link can be correct while a later redirect loses its information. ImbaHub can scope and implement handoff through a defined website route. We inspect parameters at each transition and separate preserved evidence from later platform attribution.
- Arrival
Approved campaign fields appear in the incoming address.
- Transition
Agreed values survive redirects and navigation.
- Receipt
The correct point may read the permitted information.
Preserved in a URL is technical evidence rather than an attributed business result.
The marker reaches the page but also goes to an external booking link without approval. Pass?
No. Recipient boundaries are part of the policy. Limit forwarding and test the intended route and an external negative control.
Choose parameters and the receiving point first
List the campaign information needed and the system that actually reads it. Google Ads auto-tagging and manually chosen UTM values are different evidence. Establish what the current implementation uses rather than collecting every incoming value.
Purpose, permitted information and storage need prior decisions. Do not copy identifiers into every external link or visible contact message without a need. Free text and personal information do not belong in campaign names simply because the parameter accepts them.
Map transitions that can change a value
A route may run from an advertised address through host normalisation and an old campaign URL to a language-specific landing page. Define approved fields to retain and fields to reject at each step. Copying everything can spread information to the wrong recipient.
In a fictional example, a campaign address reaches an English service page with an existing functional parameter. Adding campaign information must not replace that query string or break the page. Test function and transfer together.
| Transition | Decision | Test |
|---|---|---|
| Incoming URL | Allowed campaign fields | Fictional markers recognized |
| Redirect | Which values continue? | Compare first and next address |
| Language change | Which context remains? | Correct language and agreed values |
| Measurement point | Which information may be read? | Actual receipt inspected |
| External link | Which values must not continue? | No unintended onward transfer |
Preserve meaning without altering identifiers
Decide how duplicate keys, empty values and encoded characters are handled. Do not automatically lowercase an opaque click identifier as if it were an editorial label. Manually named campaigns need a consistent naming rule.
Review the actual receiving route where browsers or approved preferences limit collection. A missing signal must not be replaced with an invented identifier. A preserved value does not guarantee platform matching or attribution of a later outcome.
Deliver a traceable handoff route
A first scope can cover one campaign type, one URL chain and one receiving point. Test valid markers, existing parameters, language choices, absent values and prohibited forwarding with fictional information. Do not buy real ad clicks merely to test a URL transition.
The delivery records field policy, transitions, observed values and limits. Advertising accounts, CRM imports and later business reporting are separate scopes. Pricing and scope follow the actual technology and approved data requirements.
Sources and further reading
Questions, answered
Should every parameter always be retained?
No. Define approved fields and recipients. Functional parameters and prohibited onward transfer need consideration too.
Does a preserved click identifier prove attribution?
Not alone. Platform receipt, processing and attribution need separate checks.