Foundation · 2 min
What you need to know
How should advertising pixels be migrated?
Inventory every pixel, its owner, trigger, consent rule and identifiers, then redeploy it once through the approved tag path. Test it with controlled sessions and conversions.
How should campaign tracking be validated?
Create test visits with known campaign parameters and follow them through landing, session, and conversion records. Confirm parameters are retained through redirects and cross-domain journeys.
How should conversion tracking be tested?
Run controlled conversions for each important channel and compare browser or server events with the advertising platform. Validate value, currency, identifiers, consent, and attribution fields.
How do I prevent duplicate conversion tracking after migration?
Give each conversion a stable transaction or event identifier and ensure browser, server and platform events deduplicate against it. Confirm a refresh or retry cannot create another conversion.
How do I prevent marketing tags from being forgotten?
Maintain a tag inventory with owner, purpose, consent category, location and validation status. Include it in release acceptance so an untested or unowned tag cannot silently disappear.
A quick store check
Use a known campaign parameter and transaction ID to verify attribution, value, consent and deduplication end to end.
Foundation · 2 min
Frequently asked questions
Should every historical marketing tag return?
No. Restore only owned tags with a current purpose, consent rule and validation plan.
Can browser and server tracking run together?
Yes, when stable identifiers and platform rules deduplicate the two event paths.