How to switch from ClickFlare to Tracked

Move one campaign at a time. First record the live route, offer links, identifiers, and conversion callbacks. Rebuild that path in Tracked, test it with fresh clicks, and switch only new traffic after the click and postback chain checks out.

This is the practical migration checklist. For current plan and feature comparisons, see Tracked vs. ClickFlare. For the campaign setup itself, see the affiliate campaign tracking guide.

Where Tracked is today

Tracked supports campaign URLs, page destinations, offer routing, click IDs, and postback conversion tracking. This guide shows how to rebuild and verify one campaign. It does not promise a native ClickFlare importer or automatic transfer of historical events. Keep ClickFlare reports available as the record of older traffic, and confirm any account-specific import or history-transfer path before depending on it.

Make a migration inventory

Before building the new route, save the current settings and the reports you need for reconciliation. Record one row per campaign so that a ClickFlare identifier or offer does not get mixed with its Tracked replacement.

Record from the current campaign	Why it matters
Campaign URL, tracking domain, traffic source, and ad parameter names	Recreate the entry path and preserve the values your ads send.
Routing conditions, default path, landing pages, and destination URLs	Rebuild the same audience and fallback behavior.
Each page CTA, its destination, and its current click URL	Keep button intent connected to the right offer pool.
Offer network, click ID field, network token, payout, event, and transaction fields	Map the new tracker ID and conversion fields correctly.
Postback endpoint, test procedure, conversion delay, and recent report totals	Verify new callbacks while accounting for conversions from old clicks.

ClickFlare documents its {cf_click_id} token and its own click URLs in its setup guides. Record those as ClickFlare values; do not copy them into Tracked and assume they will resolve there. ClickFlare's offer setup explains its offer token, and its campaign test guide shows its click URL pattern.

Rebuild the route and map page buttons

Create the equivalent campaign route in Tracked and use its generated campaign URL for test traffic. Keep the current ClickFlare URL available while testing. Preserve the incoming ad parameters that your campaign actually uses, including source, campaign, placement, and creative IDs.

For each landing-page CTA, record what the button means before assigning a Tracked path. In Tracked, a click slot identifies the page action and its configured offer pool. Weights control the relative selection among offers attached to that pool.

Map by button intent, not by assuming the old slot number maps to the same offer. /click/1 and /click/2 identify different page paths; the offers attached to each path and their weights determine which destinations can receive a click. Buttons with the same intent and pool can share a slot. Use separate slots for different pools. The weighted offer rotation guide has a worked button-to-pool example.

Use the Tracked click ID in the network field that stores it, then use the network's actual macro to return that same value in Tracked's generated postback. A tracker token is not portable between products just because both fields are called click_id. See the postback setup guide for the identifier handoff.

Test the full path before cutover

Test the Tracked route with a fresh visit and the same entry path the ad will use. Confirm that the landing page loads, its incoming parameters remain available, and each CTA reaches the intended Tracked slot and offer pool.

Then verify the full conversion loop:

1. Follow a new Tracked campaign URL and capture its click ID.
2. Confirm the selected offer receives that exact ID in the expected network field.
3. Send an approved test conversion through the network's test process or the documented test callback.
4. Confirm the event appears once under the expected Tracked campaign, page, and offer.
5. Check the payout, event name, and transaction ID if your setup sends them.

If both trackers still have outstanding clicks, test each callback route with an ID from its own tracker. Confirm the other tracker does not receive that conversion.

If a slot has no matching offers configured, its request can fall back to the campaign's available offer pool. Check each slot's assignments before sending traffic. An HTTP success response alone does not prove that the click ID matched or the right offer received conversion credit; the postback guide explains what to verify.

Cut over new traffic in stages

Choose one campaign or clearly identifiable traffic segment for the first cutover. Set a rollback trigger before you change its ad destination, such as a missing click ID, an unexpected destination, a page error, or a conversion that fails to reach the intended report.

Point that new traffic to the Tracked campaign URL after the test passes. Keep ClickFlare's route and callback available for its outstanding clicks. Route each returned ID only to the tracker that issued it. If the network supports separate callback templates by offer, campaign, or traffic source, configure distinct ClickFlare and Tracked mappings. If it does not, isolate the two click cohorts through separate offer or campaign configurations, or use a bridge only after verifying that it routes callbacks by tracker-specific ID. Do not send every conversion to both trackers: the other tracker may reject the ID or attach it to the wrong record.

Compare the same source, audience, geography, device, page, offer, and event window where possible. Check visits, page clicks, selected offers, callbacks, and approved conversions. Wait for the approval or reversal data that matters to your offer before expanding the cutover. Configured weights are routing instructions; they are not an automatic winner decision.

Keep rollback and older conversions traceable

If a cutover check fails, restore the original ClickFlare campaign URL for new ad traffic and investigate the Tracked path separately. Keep both sets of click IDs and reports distinct: a Tracked click ID does not become a ClickFlare click ID when traffic is switched back.

Do not remove either callback route while its tracker still has outstanding clicks that can convert. Keep ClickFlare reports for historical comparison, and keep the Tracked callback available for its own in-flight clicks until the relevant conversion window closes. This keeps delayed events tied to the tracker that created their IDs.

Frequently asked questions

Will ClickFlare's {cf_click_id} work in a Tracked offer URL?

No. Use the click ID generated by Tracked for new Tracked visits, store it in the affiliate network's supported field, and return it with that network's macro to Tracked's postback.

Will old ClickFlare visits and conversions appear in Tracked automatically?

This guide does not assume that historical events transfer. Keep the old reports accessible and verify any supported import or backfill path before treating older data as Tracked history.

Can one landing page send visitors to multiple offers after the switch?

Yes. Map each CTA to a Tracked click slot, then configure the eligible offer pool and weights for that slot. Use the same slot for buttons with the same intent and pool.

Do I need to change DNS to test the new campaign?

Test with the Tracked campaign URL and a configured Tracked domain while the ClickFlare route remains available. Do not repoint the existing live campaign domain as a test step.

Sources

• ClickFlare: How to add an offer, checked September 23, 2026.
• ClickFlare: How to test a campaign before sending traffic, checked September 23, 2026.
• ClickFlare: Parameters in postback URLs, checked September 23, 2026.

Start free and rebuild one campaign in Tracked.