Migrate from Voluum
Voluum routes traffic through flows and paths, hosts nothing itself (landers live on your own server), and reuses flows across campaigns. You rebuild all of that in Qubix. There is no import and no history transfer; the postback carries over almost unchanged.
What you bring across
| In Voluum | In Qubix | How it moves |
|---|---|---|
| Affiliate network | Network | Rebuilt. Qubix ships 328 templates. |
| Offer | Offer | Rebuilt — offer URL, clickid mapping and payout. |
| Lander | PWA or Website | Rebuilt. Voluum landers are external — keep hosting them or rebuild in Qubix. |
| Traffic source | Source | Rebuilt. |
| Campaign | Campaign | Rebuilt. |
| Flow, Paths (default + rule-based), weights | Flows and distribution | Rebuilt — the default and rule-based paths and their weights become Qubix flows. |
| Domain (dedicated / custom) | 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 Voluum's API. Rebuild in parallel and keep Voluum running until conversions are confirmed to land in Qubix.
Term differences to keep in mind
- A Voluum Flow is a reusable path bundle shared by many campaigns; a Path is a branch inside it — a Default path catches traffic that matches no Rule-based path. All of this becomes a Qubix flow. Qubix has no shared-flow object, so re-apply the same routing to each campaign that used it.
- Voluum weights apply at path, lander and offer level. In Qubix you set the split per flow.
- Voluum's Anti-Fraud Kit has no direct equivalent — Qubix's protection lives in its cloaking and campaign rules; see Cloaking.
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.
- Landers. Rebuild landers as PWAs or register them as Websites.
- Campaigns, flows and paths. Recreate the campaign, then move default and rule-based paths and their weights into flows.
- Postbacks. Repoint the postback — below.
Postbacks: change only the domain
Voluum's postback goes to /postback with cid (the click id) and payout. Open each affiliate
network's postback setting and change only the domain:
Before: https://your.voluumtrk.com/postback?cid={cid}&payout={payout}&txid={txid}
After: https://your-postback-domain/postback?cid={cid}&payout={payout}&txid={txid}
Leave the /postback path and every parameter as they are. Qubix reads cid and payout without
reformatting, and uses txid to ignore a repeated postback for the same conversion.
Voluum marks the event type with a custom et value (for example et=install or et=purchase).
Qubix reads it when present; a postback with a payout and no recognised event is recorded as a
deposit, one without a payout as a registration. If your networks separate registrations and
deposits by a specific et value, keep sending it.
Check before you switch off Voluum
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.