How to switch from RedTrack to Tracked: campaign migration checklist

Move one RedTrack campaign at a time. First identify whether its ads use a tracking-link redirect or land directly on a page with a RedTrack script. Then inventory its source IDs, page route, network click-ID field, cost setup, and conversion signals before rebuilding the path in Tracked.

Tracked brings page hosting and editing into the campaign workflow: host supported HTML or ZIP files, proxy or redirect to a page that stays elsewhere, and route page and offer traffic with weights. Rebuild with a fresh Tracked click ID, test the callback, then move one identifiable ad segment. Keep RedTrack live for conversions that return against RedTrack-issued IDs.

Start free and rebuild one RedTrack campaign.

Where Tracked is today

Tracked supports hosted HTML/ZIP pages, proxy and redirect destinations, custom domains, weighted page and offer routes, and page click slots such as /click/1 and /click/2. Put Tracked's {{click.id}} in the affiliate network field that stores the tracker ID. The network callback can return that value to Tracked's GET /postback?click_id=... endpoint.

Payout, currency, and timestamp are optional callback values. For a primary conversion, send payout without a type; a typed callback is a secondary event and records zero payout. The postback setup guide shows the Tracked callback pattern.

This guide does not assume a native RedTrack importer or automatic transfer of RedTrack click and conversion history. Keep RedTrack reports for the older cohort and verify any separate history-transfer service before relying on it.

Identify the RedTrack path before rebuilding

RedTrack's redirect path sends the visitor through a campaign tracking link. Its no-redirect path sends the visitor straight to the landing page or site, where a RedTrack script records the click and parameters. In that script flow, the landing-page CTA uses a RedTrack click URL rather than linking directly to the offer. RedTrack documents the two methods in its no-redirect tracking guide.

Open the actual ad destination and inspect the page before changing anything. Record whether the ad URL is a RedTrack tracking link or the page URL with a script, which parameters arrive, and what each CTA opens. Do not treat the old script or generated link as a portable Tracked setup.

Export a focused migration inventory

Save the settings and reports you need to compare. RedTrack's Logs can export filtered data by date, click ID, campaign, traffic source, offer source, and offer. Capture the relevant click, conversion, S2S/API postback, and cost-update slices before the cutover.

Export the relevant log slices before cutover so you have a baseline when reconciling delayed conversions. RedTrack's Logs guide explains its filtered exports.

RedTrack item	Record before the move	Rebuild or verify in Tracked
Entry path and source IDs	Redirect or script flow; ad URL; source, campaign, ad set, placement, and creative IDs and macros.	Use a separate Tracked campaign URL and preserve the source values you need to report on. Test with representative ad parameters.
Page and routes	Page files or URL, scripts and assets, CTA destinations, route rules, fallbacks, and offer weights.	Host the HTML/ZIP or test proxy/redirect mode. Map each CTA to the intended /click/N slot, eligible offers, and weights.
Affiliate network click ID	RedTrack offer token, network field name, callback template, and the network macro used to return the saved value.	Replace RedTrack's token with {{click.id}}; return that exact stored value as Tracked's click_id.
Source cost	Whether RedTrack uses API cost updates, a cost macro, or manual costs; the campaign/ad set/ad level, ID mapping, timezone, and currency.	Recreate the cost path only after verifying the supported Tracked workflow for that source. Treat the old API connection and mappings as RedTrack-specific.
Outbound conversion signals	Ad-platform endpoint, event names, click/source ID fields, value fields, and any S2S, pixel, or CAPI settings.	Verify the exact Tracked workflow for each destination and event. An inbound Tracked postback does not establish an equivalent outbound integration.
Historical baseline	Filtered logs and report totals for clicks, conversions, payouts, spend, and conversion delay.	Retain RedTrack history for reconciliation; this guide does not assume it will import into Tracked.

RedTrack's {clickid} is its own generated ID passed to an affiliate network. Its {ref_id} parameter is used for the traffic source's click ID; do not mix the two up. RedTrack's dynamic parameter guide shows the outbound {clickid} and the callback's clickid=NETWORK_MACRO mapping. Those values belong to RedTrack. For new Tracked visits, store {{click.id}} at the network and return it as click_id.

Rebuild the page and offer path

Create the Tracked campaign alongside RedTrack and test it on a separate Tracked campaign URL or custom domain. Do not repoint the existing tracking domain or make a wholesale DNS change as a test step.

If you have the landing-page files and want to edit the page in Tracked, upload the supported HTML/ZIP package and check its assets, forms, and scripts. If the page should remain at its current origin, test proxy or redirect mode and confirm the final URL and CTA behavior. The hosted, proxy, and redirect guide covers those page choices.

Map each button by what the visitor is trying to do, not by RedTrack's old link numbering. In Tracked, /click/1 and /click/2 are separate page click slots. Assign each slot its intended offer pool and weights, then test every CTA. Inspect the destination URL and confirm that {{click.id}} resolves to a new Tracked ID rather than appearing as literal text.

Build the callback with the network's actual macro for the field where it saved that Tracked ID. For example, a network may call its field aff_sub, so its callback returns the saved value as click_id=NETWORK_AFF_SUB_MACRO. Test the callback with a new Tracked click and confirm the event appears against that click. Include payout, currency, or timestamp only when the network supplies them; keep type off for a primary conversion.

Recreate costs and outbound signals independently

RedTrack's cost setup can use a source API, a click-cost macro, or manually entered cost. API updates can depend on the traffic channel, cost level, ID roles, and campaign cost model. RedTrack's cost tracking guide and automatic cost update guide describe those RedTrack-specific paths.

Record how the source currently supplies spend, which source IDs receive it, and the timezone and currency used. Rebuild that separately from the page and click-ID path. Verify that the source's cost workflow is supported in Tracked before expecting the same API sync or granularity.

Do the same for conversions RedTrack sends back to an ad platform or another destination. Save the endpoint, event mapping, identifier, and value fields, then verify whether Tracked supports that exact outbound workflow. The generic Tracked postback in this guide receives conversion data; it is not proof that a RedTrack pixel, S2S callback, or CAPI configuration has a matching Tracked integration.

Test, cut over, and keep rollback available

1. Open the separate Tracked campaign URL with representative source, campaign, ad, and creative values. Confirm the intended page mode, assets, and final destination.
2. Click every page CTA. Confirm each uses the intended /click/N slot, reaches an eligible offer, and passes a resolved Tracked ID into the network's expected field.
3. Run the network's permitted test flow with that fresh ID. Confirm the callback reaches the right Tracked click and campaign. Check the primary payout, optional currency and timestamp, and any typed secondary event separately.
4. Check source cost and outbound conversion signals as separate paths. Match IDs, event names, value fields, timezone, and currency; don't infer success from a page load or an HTTP response alone.
5. Move one identifiable ad or traffic segment after the checks pass. Compare the same source IDs and time window across page visits, offer clicks, spend, callback delivery, conversions, and payout. Allow for the offer's approval and reporting delay before expanding.

Set a rollback trigger before the first ad change: missing source IDs, a page or offer error, an unresolved network click ID, or a callback attached to the wrong click are useful examples. If one occurs, send new traffic back to the RedTrack URL while investigating the Tracked path. Keep the Tracked callback active for Tracked clicks already in flight, and keep RedTrack's callback active for its own outstanding IDs until their conversion window closes. Route a conversion only to the tracker that issued its click ID; a rollback changes the path for new traffic, not the owner of earlier IDs.

Frequently asked questions

Can I import my RedTrack history into Tracked?

No native importer or automatic history transfer is verified in this guide. Export the filtered RedTrack logs you need and keep the old reports available for reconciliation.

Does RedTrack's {clickid} token work in a Tracked offer URL?

No. Use Tracked's {{click.id}} for new visits, store that value in the network field, and return the saved value to Tracked as click_id in the callback.

Should I switch my existing tracking domain or DNS first?

No. Test with a separate Tracked campaign URL or configured Tracked domain. Keep RedTrack available for existing clicks and conversions while the new route is measured.

Will RedTrack's cost sync and ad-platform signals move with the campaign?

Do not assume they transfer. Rebuild and verify cost ingestion and outbound event delivery for each source and destination. The Tracked callback described here is for receiving conversion data.

What happens to conversions that arrive late?

Return each conversion to the tracker that issued its click ID. Keep both callback routes available until their own outstanding clicks have passed the relevant conversion window.

Sources

• RedTrack: Logs, checked September 30, 2026.
• RedTrack: Dynamic Parameters/Tokens/UTMs, checked September 30, 2026.
• RedTrack: No redirect / redirectless tracking, checked September 30, 2026.
• RedTrack: Cost/Ad spend: general, checked September 30, 2026.
• RedTrack: Cost/Ad spend: automatic update, checked September 30, 2026.

Start free and rebuild one RedTrack campaign in Tracked.