Migrate from Zeustrak
Zeustrak pairs a tracker with heavy built-in traffic filtering: a campaign routes through flows and paths, and its filters tab decides who sees the money page and who is sent to the safe domain website. Qubix covers the same ground with flows and cloaking, so you rebuild both. There is no import and no history transfer; the postback is the easy part.
What you bring across
| In Zeustrak | In Qubix | How it moves |
|---|---|---|
| Affiliate Network | Network | Rebuilt. Qubix ships 328 templates. |
| Offer | Offer | Rebuilt — offer URL and payout. |
| Lander | PWA or Website | Rebuilt. Cloud landers hosted on Zeustrak must be re-hosted (see warning). |
| Traffic Source | Source | Rebuilt. |
| Campaign | Campaign | Rebuilt. |
| Flows, Paths, weights, rules | Flows and distribution | Rebuilt — path pairs, weights and rule conditions become Qubix flows. |
| Filters / cloaking (money page vs domain website) | Cloaking | Rebuilt — the safe page and the filter conditions become Qubix cloaking. |
| Tracking Domain | Domain | Re-pointed to Qubix and given a role. |
| Postback | Postback | Seamless — change only the domain (see below). |
| Reports and history | — | Not transferred. |
Term differences to keep in mind
- The money page is your real offer path (not a payments page); the domain website is the safe/white page shown to filtered-out traffic. In Qubix that split is cloaking.
- A Zeustrak Path is one lander-and-offer pair with a weight; a Flow is a reusable template of paths. Both become a Qubix flow.
- Zeustrak runs on a cloud server you provision through its panel; Qubix is installed once and hosts everything.
The order to rebuild
- Domains. Point your tracking 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 cloud landers as PWAs or register external ones as Websites.
- Campaigns, flows and filters. Recreate the campaign, then move paths and weights into flows and the filter/safe-page setup into cloaking.
- Postbacks. Repoint the postback — below.
Postbacks: change only the domain
Zeustrak'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-zeustrak-domain/postback?cid={cid}&payout={payout}&type={type}&state={state}
After: https://your-postback-domain/postback?cid={cid}&payout={payout}&type={type}&state={state}
Leave the /postback path and every parameter as they are. Qubix reads cid and payout without
reformatting.
Zeustrak marks the event with type (lead, deposit, ftd, funnel); for a funnel
conversion it adds an approval state. Qubix reads both:
| Zeustrak | Recorded in Qubix as |
|---|---|
type=lead | registration |
type=deposit, type=ftd | deposit |
state = approved / paid / confirmed | deposit confirmed |
state = reject / decline / cancel | rejection |
Keep the type and state your networks already send — nothing to rewrite.
Check before you switch off Zeustrak
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.