Specific landing page targeting is a powerful feature that allows affiliates to generate tracking links that bypass the automatic redirect cascade and target a specific landing page directly. This gives affiliates more control over which landing page their traffic sees, ensuring consistent user experience and better campaign optimization.
This feature only works with offers using redirect tracking, not direct tracking.
How it works
By default, when someone clicks an affiliate tracking link, Trackdesk runs through an automatic redirect cascade that selects the best landing page based on visitor characteristics like location, device, language, and other targeting criteria. With specific landing page targeting enabled, affiliates can override this automatic selection and force their links to always direct traffic to a specific landing page of their choice.
When you enable this feature and an affiliate selects a specific landing page, their tracking link includes a special target parameter containing the landing page ID. All visitors clicking that link will see the chosen landing page, regardless of their location, device, or other characteristics.
Enabling the feature
Specific landing page targeting can be controlled at two levels: globally and per offer. Network administrators can enable or disable the feature globally for all redirect offers under Settings → Tracking → Redirect Domains. The global setting can then be overridden on an individual offer — an offer can enable the feature even when it's disabled globally, or disable it even when enabled globally.
This flexibility lets you control which offers support specific landing page targeting based on their business needs.
Enforcing the feature
In addition to enabling specific landing page targeting, you can enforce it: making landing page selection mandatory for affiliates when generating tracking links. When enforced, affiliates can no longer rely on the automatic cascade and every generated link must include the target parameter with a chosen landing page ID. This is useful when you need strict control over which landing pages affiliates promote (for example, compliance, brand-approved pages, or controlled campaigns).
Enforcement works the same way as enabling: you can enforce globally for all redirect offers, and override that per offer. Note that specific landing page targeting must be enabled on an offer before it can be enforced — enforcement only applies to redirect tracking offers, since direct tracking already requires landing page selection by nature.
Enforcement vs. optional targeting
Behavior | Optional targeting | Enforced targeting |
Affiliate choice | Can use automatic or specific targeting | Must select a specific landing page |
Redirect cascade | Available as fallback | Not used (except on errors) |
Link generation | Target parameter optional | Target parameter required |
Use case | Flexibility for affiliates | Strict control over promotions |
Affiliate experience
When specific landing page targeting is enabled for a redirect offer, affiliates see additional options in the link generation interface:
Target specific landing page toggle: a switch with a tooltip explaining the feature.
Landing page selection: when toggled on, affiliates can choose from a dropdown of available landing pages for the offer.
Link generation: the generated tracking link includes the targeting information to ensure the selected landing page is always shown.
For direct tracking offers, landing page selection is already required by the integration, so this feature doesn't apply.
Technical details
When an affiliate selects a specific landing page, the tracking link includes a target parameter with the landing page's unique identifier:
Cascade override priority
The system processes specific landing page targeting with the highest priority in the redirect cascade:
Forced landing page (highest priority) — when specific targeting is used.
Offer status checks (inactive, caps reached, etc.).
Standard redirect cascade based on visitor characteristics.
Fallback behaviors.
Fallback behavior
If specific landing page targeting fails for any reason (invalid ID, disabled landing page, feature disabled), the system gracefully falls back to the standard redirect cascade. This ensures tracking links never break, even if configuration issues occur. Keep targeted landing pages enabled — disabled pages trigger this fallback and may send traffic to a different page than intended.