How to migrate from ThriveTracker to Tracked

To migrate from ThriveTracker, export first, then move one campaign at a time. Start by downloading the Click/Conversion Log, because ThriveTracker keeps raw data for a limited window by default. Snapshot each rotation's current weights and AI settings. Then rebuild one campaign in Tracked, replace {subid} with {{click.id}} at the network, and test the callback. Move one ad segment while ThriveTracker's /conv postback keeps serving older clicks.

Most ThriveTracker migrations hit three problems that other tracker moves don't. Raw data ages out on a schedule. AI-adjusted rotation weights keep changing until you freeze them. And landing pages link out through ThriveTracker's LP code. This guide handles each one. For the product decision itself, read Tracked vs. ThriveTracker.

Where Tracked is today

Tracked supports campaign routes, custom domains, hosted HTML/ZIP landing pages with visual editing, proxied or redirected page destinations, page click slots such as /click/1, user-configured weighted routing, conditional rules, macros, and generic postback conversions with reports and journeys.

Tracked does not adjust rotation weights automatically today. Automatic winner selection is in development. If ThriveTracker's AI Auto Optimization does real work for you, weigh that before moving. This guide does not assume a ThriveTracker importer or automatic transfer of clicks, conversions, or campaign settings. Spend sync and outbound conversion delivery depend on the provider and connection. Universal CAPI is in development.

Which ThriveTracker setup are you leaving?

ThriveTracker's pricing page lists Cloud plans. Its FAQ says Cloud runs on ThriveTracker's AWS infrastructure. It also describes a Self-Hosted Pro plan, where you control the redirect domain, server performance, and server location.

• Cloud: no server to shut down. Your overlap is limited by your subscription period and your raw-data window. Check your billing term before choosing a cutover date.
• Self-Hosted Pro: you also own a server. Keep it running, renewing its SSL, and reachable through the whole overlap. Retire it only after the last conversion window closes.

Either way, the tracking domain and postback endpoint used by live ads stay on ThriveTracker until you deliberately move them.

Export the Click/Conversion Log before raw data ages out

ThriveTracker's data storage guide says raw data is kept for the current month plus the previous three by default. Raw data includes click and conversion logs and drill-down reports. Aggregated data is kept for two years, and IP-aggregated data for one year. Support can extend raw retention on request.

The Click/Conversion Log is the most granular report. Its CSV export includes click and conversion details plus custom variables, per ThriveTracker's custom variable guide. Export it now, by campaign and month, before older months fall out of the window. Save aggregate reports too, for longer-range comparisons.

These files are your reconciliation baseline. They are not an import format for Tracked.

Inventory one campaign: postbacks, click macros, costs, and domains

ThriveTracker item	What to record	Tracked rebuild
Campaign URL and tracking domain	Full ad URL per traffic source, custom domain, and source tokens passed in	A separate Tracked custom domain and campaign URL carrying the same source values
Rotations and branches	Each rotation's landers, offers, current weights, rules, and branches	Weighted routes and conditional rules with weights you set
AI Auto Optimization	Whether AI is on, metric (ROI, CVR, EPC), lookback window, and today's computed weights	Fixed weights for now; automatic selection is in development
Landing pages	Page URL or files, LP Group, and every link using the LP code or ?g= offer targeting	Hosted HTML/ZIP page or proxy/redirect, with CTAs on /click/1, /click/2
Offer URLs	Network field carrying {subid}, such as sub1={subid}, plus the default payout	The same field carrying {{click.id}}, plus the offer payout
Network postback	/conv URL with subid, amount, tid, and the network macros used	/postback with click_id, payout, and conversion_id
Upsell and event tracking	Which events fire beyond the main sale and how they are labeled	Primary conversion plus typed secondary events
Third-party postbacks	Global or offer-level postbacks to traffic sources and their tokens, such as {externalid}	Verify the matching Tracked provider path before relying on it
Costs	Source cost token, or historical edits made with Manual Cost Update	Provider spend sync where Tracked supports that source

Map the /conv postback to Tracked

ThriveTracker's support articles show the network postback as /conv?subid=...&amount=...&tid=.... subid is ThriveTracker's click ID and is required. amount overrides the offer's default payout. tid is an optional transaction ID. Its network setup guide shows how the network's own token fills subid. Confirm the exact URL under Tracking → Pixels & Postbacks in your account. Older support pages can lag behind the interface.

Tracked's callback is GET /postback?click_id=.... Map ThriveTracker's subid to click_id, amount to payout, and tid to conversion_id. Tracked uses conversion_id to drop retried duplicates. Leave type off the main sale so it records payout. A typed callback records a secondary event with zero payout, which suits upsells or lead steps. The postback setup guide shows the full pattern.

Separate third-party postbacks and costs

ThriveTracker can fire additional third-party postbacks, at global or offer level, to send conversions back to traffic sources. Its traffic source postback guide uses tokens such as {externalid} for the source's click ID. Record each one. Outbound conversion delivery in Tracked is provider-specific, so check Tracked's path for that source before you move the campaign. An inbound Tracked postback does not, by itself, send anything to an ad platform.

For costs, ThriveTracker offers a Manual Cost Update tool for historical dates, plus whatever cost token the source passes. In Tracked, spend comes from provider sync where a connection exists for that source. Otherwise, keep comparing spend in the ad platform until you confirm a supported path.

Freeze AI rotations before you compare

AI Auto Optimization adjusts rotation weights from conversion data, according to ThriveTracker's AI guide. Recalculation runs on a delay. That means the weights you see today will not be the weights next week.

Pick one of two approaches:

1. Snapshot and copy. Record the AI-computed weights on the day you rebuild. Enter them as fixed weights in Tracked. This carries forward what the AI has learned, but it will not keep adapting.
2. Reset to a clean test. Turn AI off in ThriveTracker for the campaign being moved and run even weights in both systems. This makes the comparison cleaner but discards the learned split.

Either way, you set the weights in Tracked. The automatic winner selection article explains what Tracked is building and why fixed weights differ from it.

Rebuild the campaign and landing pages in Tracked

1. Connect a separate domain. Use a new subdomain as a Tracked custom domain. Leave the ThriveTracker domain alone, because live ads and pages depend on it.
2. Move the landing page. ThriveTracker's documented setup registers landing pages by URL, so the files usually sit on a host you already use. If you have them, upload the HTML or ZIP to Tracked as a hosted page and edit it next to its reports. If the page must stay where it is, test proxy or redirect mode. The hosted, proxy, and redirect guide compares the options.
3. Replace the LP code. ThriveTracker's click-through guide has you copy the LP code (an /outgoing link) onto every out-link. Its multiple-offers guide appends ?g= with an offer ID to target one offer. In Tracked, point each CTA at a click slot instead. Buttons with the same intent share a slot. A button that targeted one specific offer gets its own slot with that offer. See the weighted offer rotation guide.
4. Rebuild rotations as routes. Add landers and offers with the weights you chose above. Translate rules and branches into conditional rules.
5. Swap the offer token. Replace sub1={subid} with sub1={{click.id}} in the network's actual field.
6. Add a second callback. Create the Tracked postback at the network. Keep the existing /conv postback unchanged.

Test with a fresh visit carrying real source parameters. Confirm the page, each CTA, the selected offer, and a resolved Tracked ID at the network. Fire a permitted test conversion and confirm it attaches once to the right click and payout.

Cut over by campaign and avoid double counting

Choose one campaign or a clearly separable ad segment. Write down a rollback trigger, such as a missing click ID, a broken page, a wrong offer, or a callback on the wrong click. Then point only that segment at the Tracked URL.

During the overlap, return each conversion only to the tracker that issued the ID. ThriveTracker subid values go to /conv. Tracked IDs go to Tracked's /postback. If the network allows one postback per offer, use separate offers or campaigns for each tracker. Never fire every conversion to both. When reporting, take each ad's numbers from the one tracker that served it during that period.

Also turn off ThriveTracker's AI for any rotation you have moved, so leftover traffic doesn't push its weights in a misleading direction.

Reconcile, then retire ThriveTracker

Compare the moved segment against the network's report for the same dates. Check visits, offer clicks, conversions, and payout, after the offer's approval lag. Then move the next campaign.

Before cancelling	Why
No live ad points at a ThriveTracker campaign URL	Old links stop working when the account or server goes
Longest conversion window for ThriveTracker clicks has passed	Late /conv callbacks need somewhere to land
Final Click/Conversion Log and aggregate exports saved	Raw data has a retention window, and access ends with the account
Third-party postbacks rebuilt or knowingly dropped	Traffic sources keep receiving conversion signals
Network /conv postbacks removed	Stops failed callbacks after shutdown
Self-Hosted Pro server backed up and decommissioned	Applies only if you run your own server

Frequently asked questions

Can I import ThriveTracker history into Tracked?

No verified import path exists. Export the Click/Conversion Log and aggregate reports, and keep them for reconciliation. Rebuild live campaigns in Tracked.

Does ThriveTracker's {subid} work in a Tracked offer URL?

No. It resolves only inside ThriveTracker. Use {{click.id}} in the network's sub field for Tracked traffic and return it to Tracked as click_id.

Will Tracked keep optimizing my rotations like ThriveTracker's AI?

Not today. Tracked uses weights you set. Automatic winner selection is in development. Snapshot the AI weights before moving if you want to keep what it learned.

How soon should I export my ThriveTracker data?

Before starting the migration. Raw data is kept for the current month plus three previous months by default, so older click-level detail can age out while you work. Ask ThriveTracker support if you need a longer window.

What replaces the LP code on my landing pages?

Tracked click slots. Point each out-link at /click/1, /click/2, and so on, then attach the right offer pool and weights to each slot.

Sources

• ThriveTracker: Pricing, checked October 22, 2026.
• ThriveTracker: FAQ, checked October 22, 2026.
• ThriveTracker: How Long Is My Data Stored For?, checked October 22, 2026.
• ThriveTracker: Viewing Custom Variables in Reporting, checked October 22, 2026.
• ThriveTracker: Conversion tracking for Cake, HasOffers, and HitPath networks, checked October 22, 2026.
• ThriveTracker: Traffic source conversion tracking, checked October 22, 2026.
• ThriveTracker: Updating Your Historical Cost Data, checked October 22, 2026.
• ThriveTracker: AI Auto Optimization, checked October 22, 2026.
• ThriveTracker: Adding Your Click Through URL, checked October 22, 2026.
• ThriveTracker: Landing page that links out to multiple offers, checked October 22, 2026.

Start free and rebuild one ThriveTracker campaign in Tracked.