What is a prelander? A practical guide for affiliates

A prelander (also called a pre-sell page or pre-lander) is a short page a visitor sees after clicking an ad and before reaching the advertiser’s offer. Its job is to warm the visitor up: explain the product, answer the first objection, or qualify the visitor with a question or two, so that the people who continue to the offer are more likely to convert.

What is a prelander used for?

An ad has a few words and a picture. An offer page is built by the advertiser for every traffic source at once. The prelander fills the gap between the two: it continues the promise of the ad and frames the offer for one audience, one angle and one language.

In practice affiliate teams use prelanders to:

• Pre-sell. Tell the story or show the benefit that the offer page takes for granted.
• Qualify. Ask a question or two (age, country, interest) so only relevant visitors continue.
• Localize. Match the visitor’s language and market when the offer page does not.
• Collect a lead. Capture an email address before the visitor leaves for the advertiser.
• Test angles. Change the message without asking the advertiser to change the offer.

Prelander, landing page, sales page: what is the difference?

The three names describe where the page sits in the journey, not how it is built.

What are the common types of prelander?

• Advertorial. An article-style page that tells a story around the product.
• Quiz or survey. A few questions that end with a tailored recommendation.
• Video page. A short video with a button that appears at the right moment.
• Review or comparison. Why this product, compared with the alternatives.
• Lead form. A short form in exchange for the next step.

Whatever the type, a claim on the page must be true and allowed where it is shown. A prelander that promises what the offer does not deliver costs you the advertiser, not just the click.

What happens to tracking on a prelander?

This is where most prelanders fail. A click arrives with parameters that say which affiliate and which click it belongs to, often called sub-IDs, a click ID or a transaction ID. If the button on the prelander sends the visitor to the offer without them, the sale cannot be credited to its source.

Two things make this harder than it sounds:

• Every tracker names things differently. One expects s1 and s2, another sub1 and sub2, another aff_sub. The prelander has to receive the names of one system and hand over the names of the next.
• Values need encoding. A product name with a space or an image URL inside a sub-ID breaks the link unless it is URL-encoded.

Before sending traffic, click through the page yourself with test values and check that each one arrives at the offer URL under the right name.

Who should be able to see the page?

A prelander is built for the visitors of one campaign. In reality it is also opened by crawlers, automated scanners, competitors and people who share the link. None of them convert, and every one of them adds load, noise in your numbers and attention on your domain.

The usual controls are simple:

• show the page only to clicks that carry valid tracking IDs;
• limit how many times one click or one visitor can open it;
• send everyone else to a neutral fail redirect;
• give your own team a signed preview link instead of the public one.

These controls are for traffic quality. They do not replace the rules of the ad platforms and networks you work with, which you still have to follow. See our Acceptable Use Policy for what PLCloaker does and does not allow.

Why do prelander domains need looking after?

A prelander lives on a domain, and a domain has a reputation. Browsers and security services keep lists of unsafe sites; Google Safe Browsing is the best known, and a domain that lands on such a list shows a warning instead of your page. Domains also fail for ordinary reasons: an expired certificate, a DNS mistake, a registrar problem.

Teams that run many offers handle this the same way:

1. Keep several domains per category of offer, not one.
2. Group them in a pool and spread the traffic across them.
3. Check each domain on a schedule, and skip one that fails.
4. Retire a burnt domain for good so it is never used again by accident.

A short checklist before you send traffic

1. The page loads fast on a phone, including any video.
2. Every button leads to the offer with all tracking parameters intact.
3. The message matches the ad and the offer.
4. Claims are accurate and allowed in the target market.
5. Access rules and a fail redirect are set.
6. The domain is healthy and has at least one backup in its pool.
7. If you collect leads, the page says what happens to the data.

How PLCloaker helps

PLCloaker (“Prelander Cloaker”) puts these pieces in one workspace: an AI builder for the page, access rules for who sees it, domain pools with health checks, and sub-ID mapping for your tracker. You can see how each part works on the features overview, check which trackers are covered, or create a free workspace and build your first page.