Landing page tracking
How to track an affiliate prelander from ad click to sale
A hands-on prelander tracking setup for media buyers: keep the ad context, measure page-to-offer intent, and connect sales to the original page visit.
A prelander is only useful if you can see what happens after the visitor reads it. Track the ad visit, the prelander's offer CTA, the selected offer, and the eventual conversion as one journey. Otherwise a page with strong click-through can look like a winner while sending low-quality buyers to the offer.
Tracked puts the campaign route, hosted or proxied page, offer click, and postback in one workflow. You can edit a hosted page, create variations, and compare their downstream results without stitching together unrelated page and tracker reports. Start free and build your prelander funnel.
What to measure at each handoff
Ad click → prelander visit → CTA click → offer visit → sale postback
| Question | Signal to inspect |
|---|---|
| Did the ad deliver the intended audience? | Campaign visits by source, creative, placement, geography, and device parameters you captured. |
| Did the prelander create intent? | Prelander visits and click-through to each /click/N CTA slot. |
| Which destination received the buyer? | Offer selected from the slot's eligible pool and its configured weight. |
| Did the buyer convert? | A postback joined by the original Tracked click ID, with event and payout where verified. |
Do not optimize only for prelander CTR. If Page A gets 40 offer clicks from 100 visits and Page B gets 25, A has better click-through. But if B generates more approved sales or profit under comparable traffic and sufficient sample, the better business choice may be B. These numbers are an illustration, not a benchmark or a promise of performance. The split-testing guide covers how to avoid treating a small sample as a winner.
Set up the prelander in Tracked
Create a campaign route for the ad destination. Use a hosted HTML/ZIP page if you control the prelander files and want to edit the page in the same workspace. Proxy a page that must stay on its current origin after testing links and forms; use redirect mode if the page should remain entirely outside the Tracked-hosted page flow. The hosting modes guide details those options.
Preserve the source values your ad platform sends—campaign, creative, placement, and its own click identifier where available. This context helps you diagnose which ad brought a buyer, but it is not a substitute for the Tracked offer-click ID used by the sale callback.
Wire the prelander's primary CTA to its Tracked click slot, such as /click/1. If the page has a comparison table with a second offer path, wire that separately to /click/2 and assign its own eligible offer pool. Give repeated buttons that mean the same action the same slot. Test every CTA, including sticky buttons and mobile-only elements; a visually correct page can still send one button around the tracker.
Carry the click ID to the offer and back
In the Tracked offer URL, put {{click.id}} in the affiliate network's field for an external click ID. For a network whose field is called sub1, the pattern is:
https://offer.example/landing?sub1={{click.id}}
The field name above is illustrative. Follow your network's actual contract. When a visitor clicks the prelander CTA, inspect the final offer URL and confirm the macro became a real ID. Then configure the network to return that ID to the Tracked /postback endpoint as click_id. The postback URL guide provides a full callback test. If the network never stores the value, the later sale cannot be joined to the prelander click by adding a parameter only to the callback.
Once an approved test conversion appears, compare the full funnel by page variation and source segment. Check lander-to-offer CTR, offer-to-conversion rate, payout, cost, and profit using consistent event windows. Separate a delayed or rejected sale from a page failure. If a postback is absent, inspect the conversion troubleshooting checks before changing page copy.
Make the page relevant without breaking attribution
Tracked's page macros can render known campaign context on the landing page—for example, a source-specific label or a passed parameter—when your page uses the supported dynamic macro pattern. Keep fallback copy for missing values and never print a raw untrusted parameter as if it were a product claim. The dynamic macros guide shows the syntax and guardrails.
Create a variation when you want to test a different headline, comparison section, offer framing, or CTA placement. Change one meaningful hypothesis at a time and keep the same downstream postback mapping so the outcome remains comparable. Weighted routing distributes traffic; it is not itself automatic winner selection.
A prelander launch checklist
- Open the campaign URL on desktop and mobile with representative ad parameters.
- Check the page content, assets, form fields, and every CTA or sticky bar.
- Verify each CTA reaches its intended
/click/Nslot and offer, with a real{{click.id}}in the network's click field. - Trigger an authorized test conversion and confirm the event and payout appear on the expected click and page.
- Compare the page-to-offer and offer-to-sale steps before increasing spend. Preserve the original variation long enough to make a fair comparison.
Frequently asked questions
Can I track a prelander hosted outside Tracked?
Yes, if you configure a suitable proxy or redirect flow and verify that its CTA links still pass through the Tracked offer-click path. Hosting the page in Tracked is the most direct route to editing page copy and tracking its offer clicks in one workspace.
Is a high prelander click-through rate enough to call it a winner?
No. It measures movement to the offer, not approved sales or profit. Compare downstream conversion and payout under comparable traffic, and allow for delayed events.
Do I need a thank-you page pixel for affiliate sales?
Not when the affiliate network can return the stored Tracked click ID through a server-to-server postback. You still need to verify the network's field mapping, event semantics, and callback delivery.
Can multiple CTAs on one prelander go to different offers?
Yes. Assign distinct intent paths to separate click slots and configure each slot's eligible offers and weights. Repeated buttons for the same destination choice can share a slot.
Start free and connect your prelander, offers, and sales in Tracked.