Record what each identifier is meant to do
For every placement, record the issued destination, the account it belongs to, its campaign identifier and any associated promo code. Ask which identifiers are supported and which reports can distinguish them. Use the programme’s issued structure; inventing a query parameter does not make that parameter available in reporting.
Clarify how the code is entered, where it is valid and how code-based activity is attributed. If a visitor sees a code in one place and follows a link from another, ask how that situation is handled instead of assuming a universal priority rule.
Test an actual placement journey
Check the link from the real environment in which it will appear, such as a mobile browser or an app’s built-in browser. Record redirects and the final destination. If copying and pasting changes the link or removes part of it, fix the published placement before scaling.
- Placement identifier: article-sidebar-v1.
- Issued link and approved destination.
- Language and audience country used for the check.
- Time of test and an agreed non-personal identifier.
- Observed result and remaining question.
This is an illustrative log, not a required tracker format.
Keep link changes controlled
A new creative, destination or code can change the journey you are trying to measure. Save the previous version and the time of each change. When several publishers are involved, agree who can edit the placement and who records those changes.
If a code or a link appears not to work, send Ilya the affected placement, the issued version and the specific observation. Avoid sharing user identities or private account credentials. Code creation and attribution need confirmation through the programme; a promise in a message from an unverified contact is not a substitute for that confirmation.