Route approved placement traffic to a configured demand destination using an attributed direct link.
Explore types & examplesA clear plan and a little space to do your best work.
An approved sponsored link routes the visitor’s click to an eligible advertiser destination.
The publisher identifies the link as a sponsored offer. A banner is not required for this route.
A direct link is a delivery and tracking path, not a fixed visual ad format. It can sit behind an approved link or creative and route eligible clicks through the configured XML / JSON demand workflow. The surrounding placement determines what the visitor sees.
A visitor chooses a clearly described publisher link or creative. The configured route evaluates the eligible traffic and directs the visitor to the agreed destination. The publisher source remains associated with the recorded activity.
Direct link is a routing method rather than a fixed creative shape. An approved, identified link can use text, a button or a visual placement, with destination selection governed by the agreed source rules.
A publisher places an approved link within a clearly identified sponsored area. The visitor chooses the link, the configured routing process selects an eligible destination, and the advertiser’s page opens without requiring a separate banner creative to be rendered.
Use wording that matches the permitted offer category. Visitors should understand that the link is sponsored and may lead to an advertiser’s destination.
A clearly labeled button gives the visitor an intentional route to an advertiser offer. The publisher controls the button’s surrounding explanation, while the approved direct-link configuration determines which eligible destination can receive the click for that particular source.
Keep the button separate from downloads, playback and essential navigation. A sponsored destination should not be presented as a necessary website action.
An approved image or recommendation card links into the direct-link route. The visible creative introduces the offer category, while routing selects an eligible destination. The card’s appearance and the routing method are separate decisions that must remain consistent.
Agree which destinations the creative may represent and preserve source identifiers. A changing route must not make the displayed promise misleading.
Illustrative examples, not live advertising. Available inventory, creative requirements and delivery behavior are confirmed for your setup.
An approved placement introduces the destination.
Source context and eligible XML demand determine the path.
Click reporting retains the agreed source identifiers.
Receive traffic through approved placements and configured demand connections. Share destination requirements and tracking expectations so the source and offer fit can be reviewed. A direct-link route should not be confused with an automatically optimized CPA offer.
Plan a direct link campaignUse an approved placement to introduce the destination naturally. Make the purpose of the link clear, maintain source attribution and validate redirects before sending traffic. Eligibility depends on where the traffic comes from and how the user interacts.
Discuss your websiteReview recorded clicks and reconciled commercial results by source. A redirect is not itself a conversion or proof of landing-page engagement.
A direct link does not itself open a popunder. CPA conversion and payout rules belong to a separate offer workflow.
A direct link connects an approved publisher placement with a configured advertising destination. The visible link, routing decision and advertiser outcome form one journey, but each needs its own definition and validation.
A publisher places an approved sponsored link within relevant content. The link describes the destination honestly and remains distinct from essential navigation. Its configured URL carries the agreed source identifiers so the visit can be associated with that placement.
Editorial pages with an intentional offer link.
A button, image or recommendation card can use the same routing connection while presenting a more visual offer. The surrounding copy should explain what opens. Keep the clickable area separate from dismissal controls, downloads or unrelated actions on the page.
Approved offer pages and sponsored recommendations.
Where the offer supports conversion tracking, agree how the click identifier reaches the advertiser and returns with a reported action. A server-to-server postback needs an explicit contract for authentication, event identity, attribution and status handling; receiving it does not establish acceptance.
Performance offers with an agreed reporting connection.
Follow what happens on the device. The integration, placement and browser all shape the experience your audience receives.
A visible sponsored link invites a deliberate action. The routing endpoint can also receive nonhuman requests, so an HTTP request by itself does not prove that choice happened.
The configured source and available demand influence the destination. A redirect records a routing result; it does not show that the page loaded successfully or the visitor engaged.
The destination should fulfil the link’s promise and work on the visitor’s device. A later purchase, enquiry or install remains a separate action with separate acceptance rules.
Map the placement, click record, redirect and reported action before launch. This makes it possible to investigate duplicates or rejected outcomes without turning every endpoint request into a billable human click.
Confirm the website, acquisition method and advertising label. Review the actual button or link on desktop and mobile, including how it behaves beside ordinary navigation and content.
Separate eligible visitor interactions from refreshes, previews, link scanners and speculative loading where evidence permits. Browser prefetch signals can help, but absent headers do not prove a human click.
Carry the agreed click identifier through the route. Define how repeat requests, retries and duplicate clicks are handled without merging unrelated visits simply because they share an address or device.
Verify postback authentication and required fields, match the known click, check replay protection and apply offer conditions. Repeated callbacks must not create additional accepted conversions for the same action.
Active filters, validation criteria and reporting treatment are agreed for the integration.
Use the source, event history and destination together when reviewing traffic quality.
Security scanners and preview systems can fetch links for legitimate reasons while producing unsuitable advertising counts. Review their request evidence separately from deliberate click fraud and normal browser behavior.
Check unexpected redirects, broken pages and changes to the promoted offer. High request volume with poor engagement deserves investigation, but a fast exit alone is not proof of invalid traffic.
A postback from a server is not automatically trustworthy. Use the agreed authentication and identifier checks, and reconcile pending, rejected or reversed actions before reporting an accepted conversion total.
Compare like-for-like events. Use this guide to agree the reporting definitions for your direct link setup before traffic starts.
A working redirect is the start of delivery, not evidence of human intent or an accepted sale. Keep click validation and advertiser acceptance visible in reporting.
Connect the creative, placement and reporting decisions before traffic starts. These are the practical questions to resolve with your team.
A direct link has no single required visual shape: it can sit behind an approved text placement or creative. What matters first is the explanation the visitor sees before choosing it. Identify the sponsored nature of the link and make its purpose understandable, rather than relying on an unexpected destination to introduce the offer.
For an advertiser or demand partner, describe the offer, accepted source types and destination requirements. Confirm how eligible traffic is selected and what happens when no suitable destination is available. The route should preserve a coherent journey from the publisher's proposition to the offer the visitor eventually receives.
Publishers need a stable way to identify the approved website and placement in the configured request. Agree the parameters with the integration team, then check that redirects preserve the identifiers required for reporting. Do not put personal information into tracking URLs or repurpose a source identifier to describe unrelated traffic without review.
Test the path on the browsers and devices that will use it, including an unavailable-destination response. Long or broken redirect chains can create a poor experience even when the initial click is recorded. Review the complete route after any destination or template change, not just the appearance of the first publisher link.
The first recorded click, a successfully opened destination and a qualifying conversion represent different events. Compare the platform's click definition with the destination's available reporting. Verify source mapping, timezones and attribution conditions before drawing conclusions from differences between the two systems.
If the commercial relationship includes action-based payment, define the qualifying event, acceptance status and reconciliation separately. A direct-link route does not by itself establish a CPA agreement or guarantee automatic offer optimization. Evaluate the approved traffic source and the resulting business outcome using the terms of the actual demand connection.
A direct link describes the route a chosen placement uses. Popunder describes a separate-window experience. CPA describes an action-based commercial or measurement model. They should not be used as interchangeable product names. Discuss the visitor interaction, destination logic and payment event independently so both sides understand the proposed setup.
This page describes configured XML direct-link routing. It does not claim an automatic offer-selection engine.
Traffic origin, placement and destination behavior must be approved for the agreed demand connection.
Not necessarily. The surrounding approved placement may be text or another creative treatment. It still needs to explain the sponsored destination clearly and follow the source and interaction rules agreed for the demand connection.
Agree the fallback before sending traffic and test it as part of the integration. The visitor should receive an understandable outcome rather than a broken chain of redirects. Do not assume an unspecified fallback or an automatically optimized offer pool.
Browsers may prefetch a destination, and messaging previews or security scanners may inspect links. These requests need appropriate classification; they should not automatically be counted as intentional advertising clicks.
No. Successful delivery confirms that a callback reached the endpoint. Authentication, attribution, duplicate handling and the advertiser’s acceptance conditions still determine the reported action’s final status.