Guide

PWA apps

What a PWA is

A PWA (Progressive Web App) is a website that the visitor can install on the phone's home screen. It gets an icon, opens full-screen without the browser bar and looks like an app. Orbitra builds one for you in a few minutes:

  1. The visitor clicks your ad and lands on a page that looks like an app store listing (Google Play on Android, App Store on iPhone): icon, rating, reviews, screenshots, an Install button.
  2. They tap Install β†’ the browser shows its install sheet β†’ the app icon appears on the home screen.
  3. When they open the app, it shows your screen (the money step) and sends them to the offer.
  4. Optionally, the app asks for push notifications β€” and you get a subscriber you can message for free later. β†’ Push notifications

Why bother? An installed app keeps a direct line to the visitor: they come back by tapping the icon, without another paid click, and pushes bring them back again. PWAs are popular for gambling, betting, dating and subscription offers.

In Orbitra a PWA is a special kind of landing, so it goes into campaigns, streams, cloaking and reports like any other landing.

How to build one

Landings β†’ PWA. The builder has four steps and a live phone preview on the right.

Step 1. General

PWA builder, step 1
PWA builder, step 1
Picking the icon from the gallery
Picking the icon from the gallery

The Install readiness block is a checklist: icon, description, screenshots of the right size and push keys. With all green, Chrome shows the big "store-like" install sheet instead of a plain prompt.

Step 2. Screens

PWA builder, step 2
PWA builder, step 2

Step 3. Store

The texts of the store listing: button text, downloads, version, description ({value} puts a growing number in it), tags, rating, and screenshots from the gallery.

PWA builder, step 3
PWA builder, step 3

Step 4. Reviews

User reviews shown on the listing. Edit them or keep the preset ones.

Press Save changes. Open preview at the bottom shows the real page.

Putting the PWA into a campaign

A PWA is used like a landing: in a stream choose Landing + Offer, press Add landing pages, pick the PWA, then Add offers. The visitor goes ad β†’ campaign link β†’ PWA store page β†’ install β†’ app β†’ offer, and every step is attributed to the original click.

A clean domain for the app

You can also bind a domain to the PWA (step 1 β†’ Domain, or in the domain settings). Then https://app-domain.com/ opens the store page directly β€” a short, clean link that installs nicely. Visits without a campaign are recorded as organic clicks; pick an offer next to the domain so the button has somewhere to go. One domain serves one PWA.

Statistics

The Landings list and campaign reports have PWA columns:

ColumnMeaning
PWA IntentTaps on Install (before the browser's prompt)
Real PWA InstCompleted installs by real visitors (bots excluded)
PWA OpensRe-opens of the installed app from the home screen
PWA CRReal installs Γ· clicks
Push subsVisitors who allowed notifications
The PWA in the landing list
The PWA in the landing list

Per-screen numbers (how many saw each funnel screen) are on the PWA's funnel card. β†’ PWA Funnel

Good to know

Reference: PWA and Web Push, PWA Funnel, External PWA and Telegram channels.

← Previous
Landing pages
Next β†’
Push notifications to PWA users
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 β†’