Migrate from PeerClick
PeerClick routes a campaign's traffic through rules, paths and weights, and its landers are only pointers to pages you host yourself. You rebuild the routing in Qubix and re-point or rebuild the landers. There is no import and no history transfer; the postback is the easy part.
What you bring across
| In PeerClick | 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. A PeerClick lander is a pointer to your externally-hosted page — keep hosting it or rebuild in Qubix. |
| Traffic source | Source | Rebuilt. |
| Campaign | Campaign | Rebuilt. |
| Flow, Paths, Rules, Weights | Flows and distribution | Rebuilt — rules, paths and weights become Qubix flows. |
| 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 PeerClick's API. Rebuild in parallel and keep PeerClick running until conversions are confirmed to land in Qubix.
Term differences to keep in mind
- A PeerClick Rule is the condition (geo, device …); a Path is the destination bundle chosen after the rule; a Flow is a reusable rules-and-paths template shared by many campaigns. All of it becomes a Qubix flow.
- Weight in PeerClick is a raw number normalised to a percentage (weight 2 vs 8 → 20/80). In Qubix you set the split per flow.
- PeerClick's campaign types (Redirect / Direct / Website Protection) decide whether landers can rotate. In Qubix the routing is the same regardless — you build it in the flow.
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 your external pages as Websites.
- Campaigns, rules and paths. Recreate the campaign, then move rules, paths and weights into flows.
- Postbacks. Repoint the postback — below.
Postbacks: change only the domain
PeerClick's postback goes to /postback with cid, payout and status. Open each affiliate
network's postback setting and change only the domain:
Before: https://pstb.peerclick.com/postback?cid={cid}&payout={payout}&status={status}&txid={txid}
After: https://your-postback-domain/postback?cid={cid}&payout={payout}&status={status}&txid={txid}
Leave the /postback path and every parameter as they are. Qubix reads cid, payout and
status, uses txid to ignore a repeated postback, and ignores the optional protection_hash
security parameter.
The event is taken from status:
| PeerClick status | Recorded in Qubix as |
|---|---|
Sale | deposit |
Hold | registration (pending) |
Reject | rejection |
Keep the statuses your networks already send — nothing to rewrite.
Check before you switch off PeerClick
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.