Migrate from Octo Tracker

Octo Tracker routes traffic through streams and a two-stage TDS — first from the source to prelandings, then from a prelanding to offers — and it does not host your pages: prelandings and landings sit on your own server, wired with Octo's ot.php snippet. In Qubix you rebuild the routing as a campaign flow and re-host the pages. There is no import and no history transfer; the postback is the easy part.

What you bring across

In Octo Tracker	In Qubix	How it moves
Affiliate network (ПП)	Network	Rebuilt. Qubix ships 328 templates.
Offer	Offer	Rebuilt — offer URL and payout.
Prelanding / landing (Преленд / Ленд)	PWA or Website	Rebuilt and re-hosted (see warning).
Traffic source	Source	Rebuilt.
Campaign (Кампания)	Campaign	Rebuilt.
Streams (Потоки) + the two-stage TDS	Flows and distribution	Rebuilt — the source → prelanding → offer routing and stream weights become a Qubix flow.
Filters (bot / targeting)	Cloaking and flow rules	Rebuilt.
Domain	Domain	Re-pointed to Qubix and given a role.
Postback	Postback	Seamless — change only the domain (see below).
Reports and history	—	Not transferred.

Pages must be re-hosted and re-wired

Octo's page tracking relies on its ot.php / out.php snippet on your own hosting. That mechanism is Octo-specific — rebuild prelandings and landings as PWAs or upload them as Websites, and let Qubix handle the tracking instead of ot.php.

Term differences to keep in mind

• A Stream (Поток) is one weighted route with its filters — not a reusable template. In Qubix the routes and weights become a flow.
• The two-stage TDS (source → prelanding, then prelanding → offer) becomes a single Qubix flow that chains a prelanding, a landing and an offer.
• vcode is Octo's click id — in the postback it is what Qubix matches the visit by.
• Octo's lead statuses (for product/товарка offers) update a conversion later; Qubix records the status each postback carries.

The order to rebuild

1. Domains. Point your domains at Qubix and assign roles — Domains.
2. Networks. Recreate each affiliate network — Connecting a network.
3. Offers. Recreate offers with URL and payout — Creating an offer.
4. Sources. Recreate traffic sources — Creating a source.
5. Pages. Rebuild prelandings and landings as PWAs or Websites.
6. Campaigns and streams. Recreate the campaign, then move the streams, their weights and the two-stage routing into a flow.
7. Postbacks. Repoint the postback — below.

Postbacks: change only the domain

Octo's postback goes to /postback/common.php with vcode (the click id), amount and status. Open each affiliate network's postback setting and change only the domain:

Before:  https://your-octo-domain/postback/common.php?vcode={vcode}&amount={amount}&status={status}&sec=12345678
After:   https://your-postback-domain/postback/common.php?vcode={vcode}&amount={amount}&status={status}&sec=12345678

Leave the /postback/common.php path and every parameter as they are. Qubix reads vcode, amount and status without reformatting, and ignores the sec security parameter.

The event is taken from status:

Octo status	Recorded in Qubix as
submit	deposit (confirmed)
hold	registration (pending)
decline	rejection

Keep the statuses your networks already send — nothing to rewrite.

Check before you switch off Octo Tracker

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.

What's next

Migrate to Qubix

The overall move and what transfers.

Flows and distribution

Where Octo streams and the two-stage TDS go.

Parameter passing and postback

The postback in depth.