Guide

Landing pages

What a landing is

A landing (pre-landing, prelander) is your own page that the visitor sees before the offer: a story, a quiz, a review, a "special price" page. It warms the visitor up, and a warmer visitor converts better. The button on it leads to the offer through the tracker, so Orbitra knows who clicked.

Do you need one? For many offers a direct link works fine. A landing is worth testing when the offer page is cold, when the ad cannot say everything, or when you want to pre-qualify visitors.

Landing types

TypeWhere the page livesWhen to use
LocalYou upload a ZIP; Orbitra serves it from your domainThe usual choice β€” fastest, and the button link is filled in automatically
RedirectOn your own hosting or another domainYou already host the page elsewhere
PreloadAnother URL, fetched by Orbitra and shown under your domainQuick reuse of an existing page
ActionNothing is shown; the tracker does somethingSpecial cases
PWAAn installable "app" built in the panelSee PWA apps

How to add a local landing

  1. Prepare the page: a folder with index.html (and its images, CSS, JS) zipped into one archive. Use relative paths (img/photo.jpg).
  2. Make the button lead to the offer with the {offer} macro:
<a href="{offer}">Get the offer</a>

Orbitra replaces {offer} with a tracked link to the offer chosen in the stream. You do not paste the offer URL into the page.

  1. Landings β†’ Create β†’ type Local β†’ name, folder (optional) β†’ drop the ZIP β†’ Create Landing.
Creating a local landing
Creating a local landing

The files appear in the built-in file manager, where you can edit them without re-uploading.

Several offers on one page (for example, three products): link each button to a specific offer β€” <a href="{offer}&offer_id=10">. To pass a choice made on the page (a product, a quiz answer) to the offer, add sub_id_5=… to the link; the offer URL can use it as {sub_id_5}. Details: Landing pages (reference).

A landing on another site (Redirect)

The landing is on your hosting, so the page cannot use {offer}. Install the tracking script from the landing's Integrations & Code tab into the page's <head>, and link the button to /?_lp=1 as shown there. The script lets the tracker recognise the visitor coming back from your site.

The landing's integration code
The landing's integration code

Putting the landing into a campaign

In a stream choose the schema Landing + Offer, press Add landing pages and Add offers. Several landings are split by weight β€” the easiest way to A/B test landings.

A stream with a landing and two offers
A stream with a landing and two offers

Keep Offer selection: After the click: the offer is chosen when the visitor really presses the button, so the landing statistics are honest.

Landing statistics

The Landings list and the campaign report have landing-specific columns:

ColumnMeaning
LP ViewsHow many times the landing was shown
LP ClicksHow many visitors pressed the button and went on to the offer
LP CTRLP Clicks Γ· LP Views β€” how well the landing pushes to the offer
Time on LP, LP bounce, LP scrollHow long people stay (only visible time), the share who left in under 5 seconds, how far they scroll. Measured automatically on local landings
CR, EPVConversions per click and earnings per visit β€” the final verdict
The landing list
The landing list

Want to see what visitors actually do? Turn on Session recording in the landing editor β€” Clarity-style replays and click heatmaps, stored on your own server. β†’ Session recordings

Reference: Landing pages, Tracking Client (PHP).

← Previous
Cloaking for beginners
Next β†’
PWA apps
View source on GitHub: github.com/fenjo26/Orbitra.link/wiki
All guides
Guide

Beginner's guide: start here

A screen-by-screen tour of Orbitra: what the tracker does, the words you will meet, and the order to read the guides in.

Read guide β†’
Guide

Your first campaign, step by step

From a fresh install to a working campaign link and a test conversion: domain, network, offer, source, campaign, postback.

Read guide β†’
Guide

Connecting a domain

Add a domain, point DNS at the tracker, get a free SSL certificate, and what every switch on the Domains page does.

Read guide β†’
Guide

Offers and affiliate networks

How offers and networks are organized in Orbitra: templates, offer parameters and payout settings.

Read guide β†’
Guide

Postbacks: what to tell your affiliate manager

How conversions reach Orbitra: the postback URL, statuses, and what to copy-paste to your network.

Read guide β†’
Guide

Streams: how traffic is distributed

What a stream is, schemas, rotation and weights, and how Orbitra decides where a click goes.

Read guide β†’
Guide

Stream filters

Country, device, ISP, bots and more: every filter explained with examples of common routing setups.

Read guide β†’
Guide

Cloaking for beginners

Safe page vs money page, filter levels, sensitivity, and how to test your cloak before sending real traffic.

Read guide β†’
Guide

Landing pages

Host landings right in the tracker: landing types, the {offer} macro, the JS adapter and tracking pixels.

Read guide β†’
Guide

PWA apps

Build an installable PWA from a landing page: icon, screenshots, store listing and limits.

Read guide β†’
Guide

Push notifications to PWA users

Collect push subscribers from PWA landings and send them notifications β€” free re-engagement traffic.

Read guide β†’
Guide

Content Gallery

Store icons, screenshots and creatives in the tracker and reuse them across PWAs and landings.

Read guide β†’
Guide

Creatives and creative testing

Track which creative a click came from: subid routing, a test campaign and reading the report.

Read guide β†’