Lander-to-tracker integration — the 5-point wiring check

Lander-to-tracker integration — the 5-point wiring check

A landing page that does not pass parameters back to the tracker breaks optimization. Wire it in this order and verify each.

— Entry parameters: confirm the lander reads the click-id and all custom tokens from its own URL on page load. Test by loading the lander with dummy parameters and inspecting them in the page source.
— Call-to-action link: confirm every outbound button carries the click-id and tokens forward dynamically. A hardcoded offer URL on a button is a silent attribution break.
— Click event: if you track lander clicks separately (lander CTR), confirm the click pixel or link fires to the tracker with the original click-id.
— Multiple CTAs: if the lander has several buttons, confirm every one carries parameters, not just the first. Auditors miss the secondary buttons.
— Page-level tokens: confirm GEO, device, and source tokens you injected into the lander text or images resolve to real values, not literal macros visible to the user.

Validation:
— Load the lander with a test click-id, click each CTA, and confirm the tracker logs a lander click and a forwarded offer click with the matching id.

The button that forgets the click-id is the most common and most expensive lander bug.

Save this SOP. Run this before every launch.