PWA Funnel
Renderer v16 Β· migration 51. The in-browser visit to a PWA landing is now a configurable funnel: an ordered list of screens where the first enabled step is what a cold visitor sees first, every screen activation is beaconed and reported, and each screen can carry its own tracking script.
The funnel model
The landings.config_json gains one key, funnel β an ordered array of steps:
"funnel": [
{ "id": "scr_k3x9_2a", "type": "screen", "enabled": true,
"template": "lobby", "title": "...", "text": "...",
"button": "...", "image": "...", "custom_html": "...", "custom_js": "..." },
{ "id": "store", "type": "store", "enabled": true },
{ "id": "instructions", "type": "instructions", "enabled": true },
{ "id": "push", "type": "push", "enabled": true }
]
Step types:
| type | what it renders |
|---|---|
store | The Google Play / App Store listing (existing markup; UA picks the layout) |
screen | An operator screen: template lobby / slot / wheel / custom HTML β the same templates the installed-app screen uses. Up to 5 per funnel |
instructions | A full-page install-instructions screen. Both platform lists render; CSS keyed on data-store (the UA sniff in <head>) shows the Safari steps on iOS and the Chrome-menu steps elsewhere |
push | The push opt-in card placed in the browser flow. Only when Push enabled β without the VAPID key or browser support the step would be a dead end, so the flow skips it at runtime too |
Rules (PwaLanding::normalizeFunnel() is the whitelist, the editor only produces shapes it accepts):
- ids match
^[a-z0-9_]{1,32}$, are unique, and never collide with the
builtin ids; invalid ones are regenerated server-side;
- one
store/ oneinstructions/ onepushper funnel (duplicates drop); - max 5
screensteps; - absent or invalid
funnelβ[store]. **Every pre-funnel config renders
exactly what it rendered before** β the store is still the first screen, ios_flow still governs the install-click overlay, the push card still belongs to the installed app.
Flow semantics (page JS)
- The first enabled step shows on a cold visit; a non-store first step
hides the store layouts from the very first paint (data-flow-first, set by the <head> script before the body exists).
- Any
.install-triggerCTA inside the flow **advances to the next enabled
step**; when the flow is out of steps the CTA falls through to the legacy install attempt (native prompt / iOS overlay / redirect per config). The operator decides where the install prompt fires by ordering the funnel.
- The flow's push card: Allow runs the standard permission machinery (the
handover to sw.js is untouched), Not now answers the step and advances. When the flow runs out after a push answer, the visitor goes to the offer (flowExhausted); with app_action = screen the installed-app screen shows instead.
- The installed app (standalone open) is not part of the flow: the
standalone branch β open beacon, iOS install confirmation, push sync, then app_action β behaves exactly as before.
auto_redirect/decline_redirect/install_redirecttimers keep their
global meaning and fire into the offer regardless of the visible step.
Per-screen tracking
Every activation of a flow screen beacons /pixel.gif?action=pwa&kind=screen&screen=<id>&subid=<click>:
clicks.pwa_entry_screenβ first screen the click ever saw (NULL-guarded;
the click row is the dedup gate like every pwa_* column);
clicks.pwa_last_screenβ the step the click was last on (last-write-wins);pwa_screen_viewsβ the raw 1:N event log
(click_id, landing_id, screen, created_at), capped at 100 rows per click so a parked tab cycling screens cannot pump the table. Migration 51 creates it; the always-on self-heal DDL guarantees it exists on every schema version because the report SQL references it unconditionally.
Each screen step can also carry custom_js (the "Screen tracking script" field in the editor). It executes on the screen's first activation, not at page parse β an ad pixel must not fire for a screen the visitor never reached. The template's interactive engines (slot reels, bonus wheel) were refactored into per-container factories so several copies of the same template can coexist on one page; element ids are prefixed per step (fs<id>_β¦). Helpers available to custom scripts: window.orbitraFlow.next(), window.orbitraFlow.goto(id), plus the existing orbitraRedirect / orbitraBeacon.
Statistics
pwa_screen_viewsmetric β total flow-screen views, aggregated in the
dashboard cards, the campaigns list, campaign_report, and the Landings and Offers tables (report == campaigns parity). A click legitimately contributes several views; there is no derived ratio on top.
pwa_entry_screen/pwa_last_screendimensions β plain clicks
columns registered in $allowed_dimensions (api.php, campaign_report), so both work as Group By layers and as filters. NULL (pre-feature rows, non-PWA traffic) groups as Unknown.
pwa_funnel_statsendpoint β per-landing funnel card on the Landings
page (the bar-chart button on PWA rows): views/uniques per screen, entry and exit distributions (an exit = the click's last screen with no offer transition), and the screenβscreen transition matrix walked from the ordered event log. Screen order mirrors the funnel config first.
Editor & preview
The PWA constructor's step 1 gained the Visit funnel section: a reorderable step list (grip drag, β/β buttons), enable toggles, the first-screen badge, per-screen editors (template, title/text/button, hero image via MediaPicker, custom HTML + tracking JS), and a cap meter (0/5). The live preview can open the funnel at any enabled step β pwa_preview accepts a step id as view and forces it via window.__PWA_FORCE_SCREEN.
Renderer version & self-heal
RENDERER_VERSION bumped 15 β 16: the lander route and the domain-root server regenerate statics written by the older renderer on the next view, so already-created PWAs pick up the flow boot (and the store screen-view beacon) without a re-save. Legacy configs regenerate with the [store] funnel and stay visually identical.
Tests
tests/pwa_funnel_http_test.phpβ the funnel config model, flow markup,
beacon dedup/cap/attribution, and the funnel-stats endpoint (HTTP, harness sandbox).
tests/report_metrics_test.phpβ hand-computed pins for
pwa_screen_views on the dashboard, landings and offers SQL (1:N views: a click contributes every screen it saw, revisits included).
Quick start: your first campaign
The short path: install the tracker, create a campaign, and get your first clicks and conversions in under an hour.
Read guide βDocsInstallation and updates
Install Orbitra on a fresh Ubuntu or Debian server with one command, and update to new versions safely.
Read guide βDocsMigrating from Keitaro
Move campaigns, offers, sources and domains from Keitaro to Orbitra in one click β what transfers and what to check.
Read guide βDocsMigrating from Binom
Move campaigns and streams from Binom to Orbitra: what transfers automatically and what to set up by hand.
Read guide βDocsFeature overview
Everything Orbitra can do: campaigns and streams, cloaking, landings, PWA, postbacks, costs, reports and integrations.
Read guide βDocsCampaigns and streams
The complete reference: campaign settings, stream types, schemas, rotation, filters, test links and every option explained.
Read guide βDocsCloaking
Full cloaking reference: detection layers, global settings, per-stream filters, verdicts and reports.
Read guide βDocsBrowser check
How the JS check catches bots, VMs and emulators through contradictions in the browser environment.
Read guide βDocsLanding pages
Landing types, the {offer} macro, the JS adapter, LeadForge and multi-offer landings β the complete reference.
Read guide βDocsPWA and Web Push
Build installable PWA apps and collect push subscribers: settings, icons, events and notifications.
Read guide βDocsPWA Funnel
A multi-step PWA funnel: install prompts, event tracking and re-engagement notifications.
Read guide βDocsConversion popups
Show real conversion events as on-page popups: setup, triggers and placement.
Read guide βDocsSession recordings and heatmaps
Replay real visits and see click and scroll maps. Storage limits and privacy notes.
Read guide βDocsContent gallery
Central storage for icons, screenshots and creatives used across PWAs and landings.
Read guide βDocsCreatives library
Store creatives with subid tracking and test them across campaigns.
Read guide βDocsExternal PWA and Telegram channels
Publish PWAs to external domains and run Telegram channels as a traffic source.
Read guide βDocsPostbacks and conversions
Incoming postbacks, conversion statuses and types, and outgoing S2S postbacks to your traffic source.
Read guide βDocsCosts
Import spend from Facebook, TikTok and Google Ads, or update it via API and cron β and how the revenue aggregator works.
Read guide βDocsPush and pop networks
Working with push and pop traffic sources: feeds, zone optimization and the zone killer.
Read guide βDocsFacebook / Meta
Cost import from Meta Ads and the Conversions API: server-side events with deduplication.
Read guide βDocsDolphin / Fbtool
Receive Facebook costs through the Dolphin (Fbtool) API in real time.
Read guide βDocsFB comment cleaner
Bulk-moderate comments under Meta ads: hide, delete and filter by keywords.
Read guide βDocsTraffic sources and affiliate networks
Catalog of 50+ traffic sources and 440+ networks: templates, parameters and postback URLs.
Read guide βDocsReports, logs and metrics
The report builder, saved reports, click logs and every metric explained.
Read guide βDocsDomains and SSL
Add domains, DNS, free Let's Encrypt certificates, redirects, parking and every switch on the page.
Read guide βDocsCloudflare
How to run campaign domains through Cloudflare: DNS, SSL modes and what to turn off.
Read guide βDocsAdministration
Users, roles and permissions, security settings, geo databases, updates and system health.
Read guide βDocsTelegram bot
Manage the tracker from Telegram: stats, conversions and alerts in chat.
Read guide βDocsMCP: an AI assistant in the tracker
Connect Claude or any MCP client to Orbitra and manage campaigns with plain-language commands.
Read guide β