Migrating from Voluum or RedTrack

This guide maps what you already have in Voluum or RedTrack to Tallyray, and suggests an order for moving. It describes Tallyray; for the details of your current tracker, use its own documentation: Voluum’s and RedTrack’s.

Caution

Tallyray has no import for another tracker’s campaigns, clicks or reports. You rebuild your setup in Tallyray, and keep your old tracker’s reports (export them from it) for history. Tallyray’s own click ids and tokens are not compatible with another tracker’s: a postback carrying an old tracker’s click id is refused as invalid_click_id and is not recorded, so it won’t appear in your postback log.

How the parts map

You have	In Tallyray
A traffic source (Voluum’s template or full integration; RedTrack’s traffic channel)	A connection on the source’s template, under Setup, Traffic sources. See Traffic sources.
An affiliate network (Voluum’s affiliate network; RedTrack’s offer source)	A network under Tracking, Networks, with its own postback URL and token. See Affiliate networks.
An offer	An offer on that network, whose URL carries {click_id}.
A lander	A lander, with calls to action pointing at /click.
Flows and paths, rules on the visitor	Flows with rules and weighted paths.
A campaign URL with the source’s tokens	A campaign; its URL carries the source’s tokens.
Conversion types (RedTrack) and custom events	Event types.
Automizer (Voluum), rules and optimisation (RedTrack)	Rules, tuners and schedules. See Rules, auto-bidding and schedules.
Custom tracking domain (CNAME)	Domains: a CNAME and a TXT record. See Domains.
Shared and scheduled reports	Views, links and schedules. See Reports.
API access keys	API keys and the API reference.
An MCP server (Voluum, RedTrack AI)	The MCP server.

Postbacks

Tallyray’s postback fields are named the way most trackers name theirs: cid for the click id, payout, txid for the transaction id, et for the event, plus status and currency. Make a network’s postback token, copy its URL, and replace your old tracker’s URL in the network’s postback settings, with the network’s macros in place. For a network with a template, the portal fills them in. See Postbacks and conversions.

Postbacks for clicks that went through the old tracker will not match Tallyray clicks.

A safe order

1. Set up beside the old tracker. Choose a plan, add a tracking domain, connect your source, add the network and its offers.
2. Move one small campaign. Build it in Tallyray, copy its URL, and test it yourself: your visit, then your click, then a conversion. See Getting started.
3. Check the numbers beside the old tracker’s for the same campaign, remembering that cost, time zone and the time a conversion is counted at can differ: Tallyray counts a conversion at its visit’s time by default, or at its own time if you choose.
4. Replace the URLs in your ads campaign by campaign, and the postback in each network, as you go. Pause the old campaign at the old tracker’s URL only when the new one has traffic.
5. Turn on automation last: rules and tuners start dry. Read their runs, then make them active. See Rules, auto-bidding and schedules.

What differs

• Tokens are the source’s own. Each source’s page lists the macros its template puts in the campaign URL. Don’t copy macros from another tracker’s template.
• Conversions go back to the source by the source’s template: by postback URL, or by API for Meta, Google Ads and TikTok.
• Tallyray never cloaks. A flow that sends ad platforms’ reviewers anywhere other than where visitors go is refused.
• Attribution can credit a journey among several clicks in reports: see Attribution models. What goes to the source, and what rules read, is always the network’s click.
• Currencies in reports are converted to your workspace’s currency at the European Central Bank’s daily rates, with the original amounts beside.