Push and pop networks
Spend import from push and pop advertiser networks, plus Zone Killer β rules that find (and, if you allow them, block) the zones burning money. Everything lives in one place: the Push/Pop networks card in β β Integrations, in the ad networks group next to Facebook / TikTok / Google costs.
Networks
| Network | Spend level | API key |
|---|---|---|
| AdMaven | campaign Γ zone | Advertiser panel β API section β API token |
| PropellerAds | campaign Γ zone | SSP β Profile β API token |
| Kadam | campaign Γ zone | Advertiser account β API section β API token |
| Galaxion | campaign Γ zone | E-mail + password of the account (the tracker gets a token itself), or a ready API token |
| HilltopAds | campaign only | My Account β API tab β API key |
| Adsterra | campaign only | Settings β API tab β Generate new token (only the newest token works) |
| Clickadu | campaign only | Advertiser account β API section β API key |
Networks marked campaign only do have a zone breakdown in their API, but its rows carry no campaign id β a zone there cannot be tied to the campaign whose clicks it bought. Their spend is spread over the campaign's clicks, and the connection card warns about this before you connect.
Connecting
Pick a network tile, paste the key, press Check connection β it shows the account's real balance β then save. Each connection has its own update interval; the buttons in the list: Update spend (now), pause, edit, delete. Already imported spend stays in the reports after a delete.
Sync runs in the same aggregator_cron.php pass as the other cost connections (see Costs): every pass re-reads the last 5 days, the first pass 30. Re-syncing a day is safe β spend is recalculated, not accumulated.
How spend lands on a click
The main requirement is the same as for Facebook or TikTok: the campaign must use the network's traffic source template, so the link passes the network's campaign id (into ad_campaign_id) and the zone id (the Keitaro source templates write it into source, the built-in PropellerAds template into zone). Without the zone macro spend still lands β but per campaign only, never split by zone.
Matching, from the most specific level to the broadest:
- campaign Γ zone β a zone row is attributed only to clicks of the same day that carry both the zone id and the network campaign id. A bare zone id is not enough: zone ids are not unique across networks.
- campaign β a zone row whose zone matched no clicks sums onto the campaign's clicks without a zone (it never climbs onto clicks already priced by their own zone rows β several unmatched zones add up instead of overwriting each other).
The click parameter keys that count as "the zone": zone, zone_id, zoneid, sub_source_id.
If a sync answers "records received, but none could be attached to clicks", the campaign most likely does not use this network's source template β the link brings no campaign id to match on. The "Received N, matched 0" diagnostics from Costs apply here too.
Zone Killer
A card on the campaign editor's General tab (the campaign must be saved first). A rule binds the campaign to one push/pop cost connection and decides which zones are candidates:
- window β how many days back to judge (spend and conversions are summed per zone over the window);
- min spend β a zone that spent less is not worth touching;
- zero conversions and/or max ROI β the kill conditions;
- mode β
dry_run(default) orautowith a per-run block cap.
Candidates are computed from clicks.cost / clicks.revenue per zone β the same distributed numbers the reports show, with the same zone keys the cost import matched on, so a rule can never judge a zone the importer priced differently.
- Dry-run lists the candidates; you select and press Block selected.
- Auto lets
zone_rules_cron.phpexecute the candidates itself (capped per run) and sends a Telegram notification about what it blocked.
Blocking goes through the network's write API for AdMaven, HilltopAds, PropellerAds, Kadam and Galaxion. Adsterra and Clickadu have no usable zone write API: their rules stay dry-run, and the card copies the selected zone ids so you can paste them into the network's blacklist by hand.
Every block and unblock β manual or automatic β lands in an append-only journal with the metrics that stood behind the decision; the current blocked set is a zone whose latest successful action is "block". The journal is rendered under the rule.
For campaign only networks (HilltopAds, Adsterra, Clickadu) Zone Killer judges zones approximately β by their share of the campaign's clicks, because the API gives no per-zone spend. Keep their rules in dry-run and check the list before blocking.
Cron
*/15 * * * * php /var/www/orbitra/aggregator_cron.php >> /var/www/orbitra/var/logs/aggregator.log 2>&1
*/30 * * * * php /var/www/orbitra/zone_rules_cron.php >> /var/www/orbitra/var/logs/zone_rules.log 2>&1
The first line is the cron the installer adds for cost sync. The second one β the Zone Killer executor β you add yourself, and only if you use auto rules; a pass is cheap (a rule with no candidates is a single GROUP BY over the campaign's clicks). Flags: --campaign=12 (one campaign), --quiet.
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 β