How to switch from Voluum to Tracked without losing conversion tracking

Switch one campaign, not your whole account. Inventory its Voluum lander, offer, traffic-source tokens, routing rules, and network postback. Rebuild that path in Tracked, test it with a new click ID, then move only new traffic. Keep Voluum live for conversions from clicks that Voluum already issued.

The reason to make the move is workflow: in Tracked, you can host or proxy the landing page, route its CTA to an offer, inspect the attributed journey, and edit the page in the same campaign workspace. The Tracked vs. Voluum comparison covers the product decision; this guide covers the cutover mechanics.

Where Tracked is today

Tracked supports campaign routes, hosted HTML/ZIP pages, proxied or redirected page destinations, click slots, weighted offer routing, dynamic page macros, and postback conversions. It does not promise a native Voluum importer or automatic transfer of Voluum's historical clicks and reports. Export or retain the old reports for reconciliation and rebuild the first campaign intentionally. Do not call a route equivalent until you have tested its page, offer, and callback.

Export an inventory before touching the ad URL

Voluum's report export can preserve the historical numbers you will compare against. Its lander setup describes a lander element with an external URL and a click-through path; that URL alone may not be the source HTML. Save the page source or hosting access separately before trying to host or edit it in Tracked.

From the current Voluum campaign	Record for the Tracked rebuild
Tracking domain, campaign URL, traffic-source parameters	Incoming ad link and the exact source, campaign, creative, and placement values you need to retain.
Lander URL, hosting location, CTA links, any script dependencies	Whether to host the page in Tracked, proxy it, or redirect to it; which CTA maps to each click slot.
Flow/path rules, default route, offer weights	Routing conditions, eligible offers, fallback path, and intended split.
Offer URLs, network click-ID field, network conversion macro	New Tracked {{click.id}} outbound handoff and returned click_id mapping.
Postback templates, event names, currency, payout, conversion lag	New callback test plus a plan for delayed Voluum conversions.

Voluum documents its click identifier as cid and the {clickid} token in its postback guidance. Those are Voluum values. A new Tracked click uses Tracked's own {{click.id}} macro on the outbound offer URL and Tracked's /postback?click_id=... on the way back. Do not copy a Voluum token into Tracked and expect it to resolve.

Rebuild the page-to-offer path

Create a new Tracked campaign without changing the live Voluum ad URL. If you control the landing-page files, upload the supported HTML/ZIP package and test its assets. If the page must stay on its existing origin, evaluate proxy or redirect mode and verify the final URL and click behavior. The hosting mode guide explains the tradeoff.

Map each page CTA by intent. In Tracked, /click/1 and /click/2 are distinct click slots; each can have its own eligible offer pool and weights. If two buttons mean the same offer choice, they can share a slot. If they lead to different funnels, use separate slots and test both. Do not assume Voluum's click URL number or lander link naming maps to the same offer in Tracked.

Carry through the ad parameters your traffic source actually sends. Test a URL with representative source and creative values, then inspect both the landing page and the Tracked report. A route that loads but drops the source click ID or creative label is not a completed migration.

Replace the click-ID and postback contract

For each network offer, place {{click.id}} in the network field that persists the external tracker click ID. The exact field name varies by network. Configure the network's callback to return that stored value as Tracked's click_id, then test the callback with a fresh Tracked click. See the postback setup guide for a generic example.

When both trackers have pending clicks, do not send every conversion to both. Voluum-issued IDs must continue to return to Voluum; Tracked-issued IDs must return to Tracked. If the network supports separate callbacks per campaign, offer, or affiliate configuration, use those scopes. Otherwise isolate the click cohorts or use a bridge only after confirming it can distinguish which tracker issued the ID. A single unexamined global callback can silently lose delayed conversions.

Run a small cutover with a rollback trigger

1. Open the new Tracked campaign URL. Confirm the page assets load and every CTA reaches its intended slot and offer.
2. Inspect the outbound offer URL. Confirm the network receives a real Tracked click ID, not literal macro text.
3. Send a permitted test conversion through the network's testing flow. Check the event under the expected Tracked click, campaign, page, and offer; reconcile payout and event type.
4. Move one identifiable ad or traffic segment to the Tracked URL. Leave the Voluum route and its callback active for older clicks.
5. Compare the same audience and time window: lander visits, offer clicks, callback delivery, approved conversions, and payout. Set a rollback condition such as missing IDs, wrong destinations, page failures, or callback mismatches.

If a condition fails, restore the old Voluum URL for new traffic and keep the Tracked callback active for Tracked clicks already in flight. Keep both report sets until the relevant conversion window closes. Historical Voluum events remain Voluum history unless a separately verified import path exists.

Frequently asked questions

Can I import my Voluum history into Tracked automatically?

This guide does not assume an importer or automatic historical transfer. Retain Voluum reports and verify any account-specific migration service before relying on it.

Will Voluum's {clickid} work inside a Tracked offer URL?

No. Use {{click.id}} in the Tracked offer URL, then return that value through the network's supported callback macro as Tracked's click_id parameter.

Can I move a Voluum lander into Tracked?

If you have the page files and rights, you can use Tracked's supported hosted-page workflow. A Voluum lander URL is not necessarily a downloadable source package; inventory hosting, assets, forms, scripts, and CTA behavior before moving it. Proxy or redirect mode may fit a page that remains elsewhere.

Should I switch my tracking domain on day one?

No. Test a separate Tracked campaign route and domain first. Change only the chosen ad segment after the page, offer click, and callback pass. Preserve the old domain and postback for in-flight Voluum clicks.

Sources

• Voluum: Add a Lander Element, checked September 30, 2026.
• Voluum: Parameters in Postback URLs, checked September 30, 2026.
• Voluum: Export to CSV, checked September 30, 2026.

Start free and rebuild one Voluum campaign in Tracked.