Migrate from RedTrack
RedTrack is a cloud tracker built around multi-touch attribution, and it keeps two habits you will rebuild in Qubix: routing lives in funnels and streams, and landing pages are always external — RedTrack never hosts them, it only tracks pages whose code you can edit. There is no import and no history transfer; the postback is the easy part.
What you bring across
| In RedTrack | In Qubix | How it moves |
|---|---|---|
| Offer Source | Network | Rebuilt — the affiliate network behind your offers. Qubix ships 328 templates. |
| Offer | Offer | Rebuilt — URL and payout. |
| Landing page | PWA or Website | Rebuilt. RedTrack pages are external — you keep hosting them or rebuild them in Qubix. |
| Traffic Channel / Source | Source | Rebuilt. |
| Campaign | Campaign | Rebuilt. |
| Funnels, Streams, weights, filters | Flows and distribution | Rebuilt — the funnel steps and stream weights become Qubix flows. |
| Domain (custom, CNAME) | Domain | Re-pointed to Qubix and given a role. |
| Postback | Postback | Seamless — change only the domain (see below). |
| Reports, attribution history | — | Not transferred. |
Qubix does not read from RedTrack's API. Rebuild in parallel and keep RedTrack running until conversions are confirmed to land in Qubix.
Term differences to keep in mind
- A RedTrack Stream (a redirect branch inside a campaign) and a Funnel (a prelanding → landing → offer chain with its filters and weights) both become part of a Qubix flow.
- RedTrack treats a page as a Landing page only if you can edit its code; a page you cannot edit it calls an Offer. In Qubix you decide this yourself — a page you rebuild as a PWA or Website is a landing; the affiliate URL is the offer.
- RedTrack is an attribution platform (last-click, first-click, linear and so on). Qubix records the conversion the network reports on the postback; there is no separate attribution model to re-pick.
The order to rebuild
- Domains. Point your tracking domains at Qubix and assign roles — Domains.
- Networks. Recreate each offer source as a network — Connecting a network.
- Offers. Recreate offers with URL and payout — Creating an offer.
- Sources. Recreate your traffic channels — Creating a source.
- Landings. Rebuild landing pages as PWAs or register them as Websites.
- Campaigns, funnels and streams. Recreate the campaign, then move funnel steps and stream weights into flows.
- Postbacks. Repoint the postback — below.
Postbacks: change only the domain
RedTrack's postback goes to /postback with clickid, sum, and a status (and often a type).
Open each offer source's postback setting and change only the domain:
Before: https://your.rdtk.io/postback?clickid={clickid}&sum={sum}&type={type}&status={status}
After: https://your-postback-domain/postback?clickid={clickid}&sum={sum}&type={type}&status={status}
Leave the /postback path and every parameter as they are. Qubix reads clickid, sum, status
and type without reformatting; an optional ptoken security parameter is ignored.
RedTrack keeps the event in type and the approval in status. Qubix reads both:
| RedTrack | Recorded in Qubix as |
|---|---|
type=Lead | registration |
type=Sale with status=approved | deposit |
status=pending | registration (pending) |
status=declined | rejection |
Keep sending the type and status your sources already send — nothing to rewrite.
Check before you switch off RedTrack
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.