Sources and networks

Two directories that configure the "edges" of the funnel: a traffic source describes which parameters arrive in the campaign URL and where to send conversions back; an affiliate network — which parameters to append to the offer and where the network sends its postback.

Traffic sources

The Sources section in the top menu.

Templates

About 200 templates: 196 from the Keitaro template export (data/keitaro_traffic_sources.json) plus built-in ones (Facebook, Google Ads, TikTok, Snapchat, VK, Yandex, and others). A template fills in the source's parameters and postback. You can also create a "custom source" without a template.

Templates are generated data. They must not be edited by hand: a mistake in a single macro looks fine in the interface, but the click arrives without external_id, and no postback can then find the click. They are regenerated by the cli/generate_keitaro_templates.py script from Keitaro exports; the check is php tests/keitaro_templates_test.php.

Parameters

Each parameter is a triple:

Field	Example	Meaning
Alias	ad_id	The name under which the value is stored in the click (clicks.parameters_json) and available as {ad_id}
Parameter	ad_id	The parameter name in the campaign URL
Source macro	{{ad.id}}	What to substitute into the link in the ad dashboard

When a source is selected for a campaign, these parameters are automatically added to its URL. They are what gives the cost import IDs to match on (Costs) and the "URL parameter" filter its values.

Postback to the source

The postback_url and the statuses to send. When a campaign is assigned such a source, its postback lands on the campaign's S2S Postbacks tab — see Postbacks and conversions.

URL check

A source can have a URL for availability checking. Check all of them at once with the button in the list, the bot command /checksources, or a cron:

0,30 * * * * php /var/www/orbitra/check_sources_cron.php

Affiliate networks

The Affiliate networks section.

Templates

About 440 templates: 395 from the Keitaro export (data/keitaro_affiliate_networks.json) plus built-in ones. A template provides:

• The Postback URL for the network's dashboard (the global postback) — https://your-domain/<postback_key>/postback?subid=…&status=…&payout=…;
• Offer parameters — what to append to the URL of each offer of this network.

Offer parameters

For example &subid={subid}&campaign={sub_id_1}. They are appended to the offer URL at click time, not saved into the offer: editing the network immediately affects all of its offers. A parameter already written in the offer URL takes priority — a manual subid={subid} will not be doubled. Path suffixes like /{subid} are also supported. Full rules — Affiliate network offer parameters (in English).

Available macros: {subid} / {clickid} (the click ID), {ip}, {country}, {device}, {referer}, {keyword}, {cost}, {external_id}, {creative_id}, {ad_campaign_id}, {offer_id}, and any click parameters ({sub_id_N}, {ad_id}…). A macro with no value on the click becomes an empty string.

LeadForge

LeadForge (the ⚙ menu) is a separate tool: it assembles a local offer landing from a downloaded page and submits leads to a CPA network through a generated order.php. Its list of networks is outbound lead-submission adapters, not the "Affiliate networks" directory. Details — in the LeadForge section of Landing pages.