Migrate from Skro
Skro is a cloud tracker: a campaign routes through a flow with a default path and rule-based paths, and it hosts your static landers itself with free SSL. You rebuild the routing in Qubix and re-host the landers. There is no import and no history transfer; the postback is the easy part.
What you bring across
| In Skro | 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. Static landers hosted on Skro must be re-hosted (see warning). |
| Traffic source | Source | Rebuilt. |
| Campaign | Campaign | Rebuilt. |
| Flow, Default path, Rule-based paths, weights | Flows and distribution | Rebuilt — paths, conditions 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. |
Term differences to keep in mind
- A Skro Flow is the whole routing container; a Path is a branch of landers and offers inside it — a Default path plus Rule-based paths. All of it becomes a Qubix flow.
- Skro supports cloaking (a cloaking domain with a 302 redirect); in Qubix the same is handled through 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 hosted landers as PWAs or register external ones as Websites.
- Campaigns and flows. Recreate the campaign, then move the default and rule-based paths and their weights into flows.
- Postbacks. Repoint the postback — below.
Postbacks: change only the domain
Skro's postback goes to /postback with clickId, payout and status. Open each affiliate
network's postback setting and change only the domain:
Before: https://your.skrotrack.com/postback?clickId={clickId}&payout={payout}&status={status}
After: https://your-postback-domain/postback?clickId={clickId}&payout={payout}&status={status}
Leave the /postback path and every parameter as they are. Qubix reads clickId, payout and
status without reformatting.
The event is taken from status:
| Skro status | Recorded in Qubix as |
|---|---|
approved | deposit |
pending | registration (pending) |
declined | rejection |
refund | rejection (charged back) |
Keep the statuses your networks already send — nothing to rewrite.
Check before you switch off Skro
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.