Move from Keitaro and Binom without rebuilding campaigns by hand
Give inotrack your old tracker's address and an API key, and it pulls in your affiliate networks, offers, sources, landing pages and campaigns with flows, weights and filters. It shows you the plan first, then brings everything over paused: no traffic moves until you check and enable it.
The whole catalog and routing
From Keitaro through Admin API v1, from Binom through API v2. The import only reads from the old tracker.
| What | Keitaro | Binom | In inotrack |
|---|---|---|---|
| Affiliate networks | Affiliate networks | Affiliate networks | Advertisers (CPA networks). From Keitaro: if a network with the same name already exists, the offer is attached to it, so no duplicate is created. From Binom: if the name matches, a new network is created and tagged "(Binom #id)". Offers without a network are grouped under a generic advertiser. |
| Offers | Offers (except local ones) | Offers | Offers with their URLs (macros replaced with ours, see the table below), geo, payout and currency. From Keitaro, the daily cap and the affiliate parameters appended to the URL come over too. |
| Traffic sources | Traffic sources | Traffic sources (tokens t1…t10) | Sources: source parameters → sub1…sub10, plus the link template. From Keitaro, the platform's click id parameter comes over too; with Binom you set it by hand. |
| Landing pages | Landing pages | Campaign path landing pages | Landing pages by external URL. Archives uploaded to the tracker are not downloaded, so you will need to upload them again. |
| Campaigns and flows | Campaigns → streams | Campaigns → paths and rules | "Campaign / Flow" flows: a split of offers and landing pages with weights, filters by geo, device, OS and language. In Binom, paths are collapsed into one split (weight = path share × share within the path), and each rule becomes a separate flow with its own filters. |
API key → preview → import
- 1
Tracker address and API key
Keitaro: Account → API keys (Admin API v1). Binom: Settings → the API block at the bottom of the page, the api_key parameter. The key is held in memory only for the duration of the import: it is never saved to the database, the logs or the report.
- 2
Preview
The tracker reads the old account and shows a plan: what will be created, what will be updated, where names matched and what will not be migrated, with a reason for each entity. Nothing is written to the database at this step.
- 3
Import in the background
The import runs as a job: you see the progress and, at the end, a report on every entity plus the full macro table. Offers and flows are created paused, so not a single click goes to an unchecked link.
- 4
Check and launch
Go through the warnings in the report, point your networks' postbacks at the new domain, upload the landing page archives and enable flows one by one. The old tracker keeps working until you switch the links in your ad accounts.
Re-running the import updates what has already been migrated (matched by external id) and creates no duplicates, so you can keep pulling in changes from the old tracker while you move.
What is left for you to do
Point network postbacks at the new domain
Postback URLs live in your network accounts, and the import cannot reach them. Create a postback endpoint in inotrack (there are presets for popular networks) and replace the URL in your network account with https://<your-domain>/pb/<token>?clickid={clickid}…
Landing page archives
Keitaro's local landing pages and Binom's archives are not downloaded: only the external URL is migrated. Upload the landing pages that lived inside the tracker to inotrack as an archive.
Links in ad accounts
Each flow here has its own link. Once a flow is checked and enabled, replace the tracking link in your ad account.
Anything the report flags with a warning
OR filters, flow triggers, flow weights within a campaign, a fallback offer on a cap, sub tags after the 10th, postbacks to Binom sources — all of this is listed in the report for the specific entity. Set up whatever you need by hand.
The postback URL format and network presets are in the postbacks guide (in Russian).
What stays in the old tracker
Nothing is lost silently: anything that was not migrated, or was migrated only in part, is listed in the import report with a reason.
- Statistics: clicks, conversions and costs stay in the old tracker
- Domains, users and access rights
- Landing page files uploaded to the tracker, and Keitaro's local offers
- Keitaro flow triggers and filters combined with OR
- Binom rules with any condition other than geo, device, OS or language — the whole rule is skipped, because a flow missing some of its conditions would catch the wrong traffic
Macro mapping table
In offer, landing page and flow URLs, Keitaro and Binom macros are replaced with ours. The full table is included in every import report; all of our macros are in the reference (in Russian).
| inotrack | Keitaro | Binom | Note |
|---|---|---|---|
| {clickid} | {subid} | {clickid} | click id |
| {sub1}…{sub10} | {sub_id_1}…{sub_id_10} | {t1}…{t10} | — |
| {geo} | {country}, {country_code} | {country_code}, {country} | ISO country code; the country name ({country:ru} in Keitaro) is not migrated |
| {city} | {city} | {city} | — |
| {device} | {device_type} | {device_type} | desktop, mobile, tablet, tv |
| {os} | {os} | {os_name}, {os} | — |
| {browser} | {browser} | {browser_name}, {browser} | — |
| {source} | {ts_id} | {traffic_source_id}, {trafficsource} | the source id in inotrack |
| {flow} | {campaign_id}, {stream_id} | {campaign_id}, {campaign} | inotrack flow token: a campaign expands into flows |
| {offer} | {offer_id} | {offer_id} | the offer id in inotrack |
| {campaign} | {ad_campaign_id} | — | the platform's campaign (the campaign / utm_campaign parameter) |
| {creative} | {creative_id} | — | — |
| {rnd} | {random} | — | a random token; the {random:1,100} range is not supported |
Macros with no equivalent — {sub_id_11}…{sub_id_30} and {t11}…{t30}, {ip}, {user_agent}, {referrer}, {isp}, {region}, {language}, campaign, offer and source names — are not stripped: they stay in the URL as is and show up in the report. The offer is paused, so a "raw" macro will not go out to the network unnoticed.
Moving from RedTrack, Voluum, BeMob, AdsBridge
There is no API key import for these trackers; it exists only for Keitaro and Binom. You set your campaigns up from scratch while the old tracker keeps taking traffic.
- 1
Networks and offers
Create the affiliate networks and offers. In each offer URL, replace the old tracker's macros with ours: {clickid}, {sub1}…{sub10}, {geo}, {device}. The full list is in the macros reference.
- 2
Sources and flows
Create a traffic source with its own parameters in sub1…sub10. Build the first flow with the "Launch campaign" wizard and clone it for similar ones; large batches of look-alike flows are easier to create through the API (from the Growth plan).
- 3
Network postbacks
Create a postback endpoint (there are presets for LeadGid, Pampadu, Unicom24, Guruleads, Leads.su and other networks) and replace the URL in your network account with https://<your-domain>/pb/<token>?clickid={clickid}…
- 4
Links in ad accounts
Check the flow with a test click and conversion, then replace the tracking link in your ad account. The old tracker keeps running in parallel until you have switched everything over. Statistics stay there, so export the reports you need first.
Macros are in the reference (in Russian); the first flow is in the quickstart.
Still choosing? Point-by-point comparisons: inotrack vs Keitaro, inotrack vs Binom, inotrack vs RedTrack, inotrack vs Voluum, inotrack vs BeMob, inotrack vs AdsBridge — or all comparisons.
Questions
Will my statistics be migrated from Keitaro or Binom?
No. The import migrates settings: networks, offers, sources, landing pages and flows. Clicks, conversions and costs stay in the old tracker.
Can I import from RedTrack, Voluum, BeMob or AdsBridge?
No. The API key import exists only for Keitaro and Binom. Coming from any other tracker, you set up networks, offers, sources and flows from scratch (with the "Launch campaign" wizard, by cloning or through the API) and switch postbacks and ad account links by hand.
What happens to my traffic during the migration?
Nothing. The import only reads from Keitaro and Binom, and in inotrack offers and flows are created paused. Traffic keeps running through the old tracker until you switch the links in your ad accounts yourself.
Can I run the import again?
Yes. The import remembers each entity's external id: a rerun updates what has already been migrated instead of creating duplicates. It leaves the status (paused or live) alone, so flows you have enabled will not go back to paused.
Where is the old tracker's API key stored?
Nowhere. The key lives in memory for the duration of the preview or job and does not end up in the database, logs, report or error messages. The tracker address must be a public https URL.
Where do I run the import?
In the panel, on the "Import from Keitaro and Binom" page: the steps "Connection" → "Preview" → "Import", and at the end a report with the tabs "Migrated", "Names matched", "Not migrated" and "Macros". Any user with write permission can run it: a buyer's import creates personal records, an admin's creates team-wide ones, and a viewer cannot import. The same is available through the tracker API: …/import/keitaro/preview, …/run and …/jobs/{id} (for Binom, …/import/binom/…).
Can I migrate only some of my Binom campaigns?
Yes: list the ids of the campaigns you need (up to 1,000) in the "Only these campaigns" field. With no list, the import takes all active campaigns.
Which plan includes the import?
All of them: the import is not a separate module. On Enterprise we also help with the migration: we go through the report with you and tell you what to set up by hand.
Moving from Keitaro or Binom?
Install inotrack on your own server and bring your campaigns over with the import. On the Enterprise plan we help with the migration: we go through the report and set up what is not migrated automatically.
Questions? Message us on Telegram: @SmokeJung.