Conversion popups
A popup with an offer button on your landings. Every campaign owns its popup: it is switched on and tuned on the editor's Popup tab (a dot next to the tab name glows while it is on) and saves with the campaign's usual Save button. A copied campaign carries its popup along. Settings β Plugins is the overview page: which campaigns run a popup and how it is doing (template, shows, clicks, CTR over 7 days, a Configure button that opens the campaign straight at the Popup tab), plus the template for new popups β the starting point a campaign's popup is pre-filled from the first time you enable it.
Upgrading from a pre-v1.8.0 install: the old global switch is gone. If it was on, every campaign that relied on it has its popup switched on after the update; otherwise popups stay off everywhere.
Where the popup works
| Where | How |
|---|---|
| Landing uploaded to Orbitra, or a "Show HTML" stream | Automatic |
External site with tracking.js or kclient.js | Automatic β the script reads the popup config from the Click API response |
External site with kclient.php | Automatic β a current kclient.php appends the popup tag itself when the campaign has the popup on. Sites still running an old copy of the file need it updated once; the manual <?php echo $client->popupScript(); ?> line still works too |
| A campaign that redirects straight to the offer | Not possible β there is no page to show a popup on |
Bots and safe-page visitors never see the popup at all: the server decides before a single byte of popup code ships. A redirect-only campaign can still have the popup on β an external page of yours with tracking.js is a valid stage; the tab only explains where the popup can appear.
The Popup tab
- A checkbox β Show a popup to this campaign's visitors β and under it a plain-language readiness line: "Ready: the popup will appear on this campaign's landing", or the reason it has nowhere to appear, with an Open Integrations button.
- A live preview of the popup as you tune it.
- Four steps:
- Template β one of seven vertical cards (Universal, Nutra, Gambling, Betting, E-commerce, Finance, Crypto): sets the wording, the default amount and the illustration.
- Text & amount β your own headline, body and button label; the
{amount},{currency}and{country}macros resolve from the click's geo. The amount is set in US dollars for bonus verticals and converted to the visitor's currency with a "nice" rounding (250 β 200 β¬ / 7 500 000 β«); discount verticals treat it as a percentage. - Image β the vertical's picture by default, or any Gallery image.
- When to show β delay, once-per-N-hours frequency, scroll-depth and exit-intent triggers, and the activity gate: two different actions, one of them pointer/touch (mouse move or tap). Scroll or keyboard alone never qualifies β a bot scripted to scroll still never sees the popup.
- Advanced (collapsed): designs β Card, Gift (bottom sheet), Alert, a random enabled one per show; animation, position, accent color, the language mode (auto / forced / whitelist of the 11 built-in).
- Reset to template β undo everything the template didn't ask for.
The button is a real funnel step
The popup button is the tracker's signed landing β offer transition β the same one a CTA on the landing uses. A press continues through the tracker (offer_at, conversions, the popup CTR metric all land on the same click) and carries sub_id_30=popup, so the network side can tell popup traffic apart.
Statistics
Available from day one in the report customizer:
| Metric | Definition |
|---|---|
| Popup shown | Visitors the popup actually rendered for β after the delay/activity gates, bots excluded |
| Popup CTR | Popup clicks Γ· Popup shown Γ 100% |
| Popup clicks | Visitors who pressed the offer button |
| Popup closed | Visitors who dismissed the popup without clicking |
| Popup conversions | Conversions on clicks that came through the popup button |
The report builder also gains the Popup variant dimension (design Γ text) β group by it to compare variants. The Settings β Plugins list shows the short version (shows, clicks, CTR) per campaign.
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 β