Migrate from BeMob
BeMob follows the familiar cloud-tracker shape — a campaign routes traffic through a flow made of paths, landings are hosted on your own server, and each campaign picks a redirect mode. You rebuild all of it in Qubix. There is no import and no history transfer; the postback is the easy part.
What you bring across
| In BeMob | In Qubix | How it moves |
|---|---|---|
| Affiliate network | Network | Rebuilt. Qubix ships 328 templates. |
| Offer | Offer | Rebuilt — offer URL, click-ID param and payout. |
| Landing | PWA or Website | Rebuilt. BeMob landings are external — keep hosting them or rebuild in Qubix. |
| Traffic source | Source | Rebuilt. |
| Campaign | Campaign | Rebuilt. |
| Flow / Built-In Flow, Paths, weights | Flows and distribution | Rebuilt — default and rule-based paths and their weights become Qubix flows. |
| Domain (tracking + cloaking) | 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 BeMob's API. Rebuild in parallel and keep BeMob running until conversions are confirmed to land in Qubix.
Term differences to keep in mind
- BeMob's Built-In Flow (the routing inside one campaign) and a saved reusable Flow both become a Qubix flow; the Default path plus Rule-based paths and their weights carry the split logic.
- BeMob splits its domains into tracking and cloaking roles and exposes redirect modes (302 / Meta / Double Meta). In Qubix, cloaking is a campaign feature — see Cloaking.
- Paid add-ons such as Smart Rotations and Fix-On map onto Qubix's own flow settings.
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 flows. Recreate the campaign, then move the built-in flow's paths and weights into flows.
- Postbacks. Repoint the postback — below.
Postbacks: change only the domain
BeMob's postback goes to /postback with cid, payout and status. Open each affiliate
network's postback setting and change only the domain:
Before: https://your.bemobtrk.com/postback?cid={cid}&payout={payout}&txid={txid}&status={status}
After: https://your-postback-domain/postback?cid={cid}&payout={payout}&txid={txid}&status={status}
Leave the /postback path and every parameter as they are. Qubix reads cid, payout and
status, and uses txid to ignore a repeated postback for the same conversion.
The event is taken from status:
| BeMob status | Recorded in Qubix as |
|---|---|
lead | registration or deposit (with a payout it is a deposit) |
hold | registration (pending) |
reject | rejection |
Keep the statuses your networks already send — nothing to rewrite.
Check before you switch off BeMob
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.