Migrate from Kintura
Kintura routes traffic with per-user machine learning rather than fixed weights, through routes and route targets, and its landings are hosted by you. In Qubix you rebuild the routing as a campaign flow. There is no import and no history transfer; the postback is the easy part.
What you bring across
| In Kintura | In Qubix | How it moves |
|---|---|---|
| Affiliate network | Network | Rebuilt. Qubix ships 328 templates. |
| Offer | Offer | Rebuilt — offer URL and payout. |
| Landing page | PWA or Website | Rebuilt. Kintura landings are external (KinturaJS) — keep hosting them or rebuild in Qubix. |
| Traffic source | Source | Rebuilt. |
| Campaign (one source + one region) | Campaign | Rebuilt. |
| Routes, Route Targets, Filters | Flows and distribution | Rebuilt — routes and their targets become the split and rules in a Qubix flow. |
| Whitelists / Blacklists | Cloaking and campaign rules | Rebuilt where an equivalent applies. |
| Domain | Domain | Re-pointed to Qubix and given a role. |
| Postback | Postback | Seamless — change only the domain (see below). |
| Reports and history | — | Not transferred. |
Qubix does not read from Kintura's API. Rebuild in parallel and keep Kintura running until conversions are confirmed to land in Qubix.
Term differences to keep in mind
- A Kintura Route is the link from a campaign to its Route Targets (landings and offers); a Filter gates a route by rule. Both become a Qubix flow.
- Kintura distributes traffic with predictive machine learning per user, not weights. In Qubix you set the split per flow; there is no per-user predictive routing to re-create one-for-one.
- A Kintura Campaign is bound to one traffic source and one region — rebuild it the same way, one campaign per source and geo where you relied on that.
The order to rebuild
- Domains. Point your domains at Qubix and assign roles — Domains.
- Networks. Recreate each affiliate network — Connecting a network.
- Offers. Recreate offers with URL and payout — Creating an offer.
- Sources. Recreate traffic sources — Creating a source.
- Landings. Rebuild landings as PWAs or register them as Websites.
- Campaigns and routes. Recreate the campaign, then move routes, targets and filters into flows.
- Postbacks. Repoint the postback — below.
Postbacks: change only the domain
Kintura's postback goes to /conversion with cid, payout and a status. Open each affiliate
network's postback setting and change only the domain:
Before: https://track.kintura.io/conversion?cid={cid}&payout={payout}&txid={txid}&status={status}
After: https://your-postback-domain/conversion?cid={cid}&payout={payout}&txid={txid}&status={status}
Leave the /conversion path and every parameter as they are. Qubix reads cid, payout and
status, and uses txid to ignore a repeated postback. Kintura's status is a free label (often
lead); Qubix reads the common values, and a postback with a payout and no recognised status is
recorded as a deposit, one without a payout as a registration.
Check before you switch off Kintura
Fire a test conversion and watch it land on the Postbacks feed, then in the deposit and registration reports. Cut traffic over only once conversions arrive reliably.