Push notifications to PWA users
What it is
When someone installs your PWA, the app can ask: "Allow notifications?". Everyone who says yes becomes a subscriber in your Push Base. You can then send them notifications β a reminder, a new bonus, a discount β for free, and every tap on a notification brings the visitor back to the offer, attributed to their original click.
Orbitra does it all on your own server: the subscriber base, the encryption keys, the sending. Google and Apple only deliver the messages to the phones.
Setting it up
1. Keys and contact
Open Push Base.
- Sender contact β
mailto:[email protected](or anhttps://address). Apple rejects notifications with a placeholder contact, so use a real one. Press Save changes. - Generate keys. That is all β the keys (VAPID) are given to every PWA automatically; nothing to paste anywhere.

The strip under the keys shows the state: Keys β, Contact β, Worker (when the sending job last ran) and the number of active subscribers.
Generate the keys once. Replace keys invalidates every subscription; devices re-subscribe the next time they open the app, but until then they receive nothing.
2. Ask for notifications in the PWA
In the PWA builder, step Screens, tick Push notifications and save. After install, the app offers notifications once.
3. Make sure the sending job runs
Notifications are sent by a background job every minute (cli/push_cron.php). The installer sets it up. If Worker says "never ran" on a real server, check the cron:
crontab -u www-data -l | grep orbitra-push
Subscribers
The Subscribers tab lists the base: country, language, click ID, status (active / dead). Subscriptions die by themselves when a phone uninstalls the app β no cleanup needed.
The Send button on a subscriber row sends a test push to that one device instantly, bypassing the queue β the fastest way to test the whole chain on your own phone.
Messages
Messages β New message. Two kinds:
- Manual β you press Send now and it goes out.
- Event β sent automatically after an event: Install, Lead or Sale, with a delay you choose (e.g. 600 seconds after install).

| Field | Tips | ||
|---|---|---|---|
| Title, Text | Short. `{Hi\ | Hey\ | Hello} picks a random variant for every recipient; {subid}` and other click macros are filled in at send time |
| Icon, Image | URLs, conveniently copied from the Content Gallery. The big image shows on Android only | ||
| Link | Where a tap leads. Put a campaign link (optionally with sub_id_5=push to see pushes in reports) | ||
| Segment | All subscribers / no registration yet / registered without deposit / with deposit β built from the conversions of each subscriber's click | ||
| Countries, Languages | Narrow the audience: DE, de |

The message list shows for each message: Sent, Viewed, Push clicks, and what the clicks brought β Regs, FTD, Revenue.

Good practice
- Start with an Install event message ("Thanks for installing! Your bonus is waiting") β it has the best click rate.
- Send manual messages at a sensible local time; do not spam β every unsubscribe is a lost channel.
- "Sent" means the push service accepted the message; only the phone decides whether it is shown. Test on your own device first.
Reference: PWA and Web Push.
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 βGuideYour 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 βGuideConnecting 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 βGuideOffers and affiliate networks
How offers and networks are organized in Orbitra: templates, offer parameters and payout settings.
Read guide βGuidePostbacks: what to tell your affiliate manager
How conversions reach Orbitra: the postback URL, statuses, and what to copy-paste to your network.
Read guide βGuideStreams: how traffic is distributed
What a stream is, schemas, rotation and weights, and how Orbitra decides where a click goes.
Read guide βGuideStream filters
Country, device, ISP, bots and more: every filter explained with examples of common routing setups.
Read guide βGuideCloaking for beginners
Safe page vs money page, filter levels, sensitivity, and how to test your cloak before sending real traffic.
Read guide βGuideLanding pages
Host landings right in the tracker: landing types, the {offer} macro, the JS adapter and tracking pixels.
Read guide βGuidePWA apps
Build an installable PWA from a landing page: icon, screenshots, store listing and limits.
Read guide βGuidePush notifications to PWA users
Collect push subscribers from PWA landings and send them notifications β free re-engagement traffic.
Read guide βGuideContent Gallery
Store icons, screenshots and creatives in the tracker and reuse them across PWAs and landings.
Read guide βGuideCreatives and creative testing
Track which creative a click came from: subid routing, a test campaign and reading the report.
Read guide β