When moving makes sense
The move pays off if Binom mostly distributes your traffic: rules by country, device and tokens, a bot filter, many domains. In TDS.SO routing, bot filtering, the click log and statistics run in the cloud. Your VPS only runs a web server that passes traffic on, so there is no tracker to update or tune on it.
Wait if you rely on things TDS.SO does not have: Smart Rotation, continent or connection type rules, lander click URLs with lp=1, or reports you have built up in Binom. The TDS.SO tracker (offers, conversions, revenue, ROI) is in beta, so check it against Binom on one campaign before you move the rest.
What maps to what
| Binom | TDS.SO |
|---|---|
| Campaign | Link: domain/slug or the whole domain |
| (no direct equivalent) | Template: shared settings for many links |
| Rule | Stream: checked top to bottom, the first match wins; a stream without conditions never fires |
| Default paths | Main URL, the Everything else row |
| Path and offer weights | URL shares inside a stream or the main URL |
| Normal Rotation / Fix On | How to choose → At random / Keep the same |
| Binom Protect, bot rule | The template's Filter Level and Bot Action, checked before streams |
| Offers, traffic sources | Tracker → Offers and Traffic Sources (beta) |
The template is new if you come from Binom. You set streams, the redirect type and the bot filter once and create links from it. Changing the template's redirect type, bot filter or Parameter Forwarding updates existing links straight away. The URL, the Bot URL and streams are copied into a link when you create it.
Bot filtering is part of every plan. Levels are Off, Standard, High, JavaScript (a browser check) and Custom, where you tick signals such as data centers, VPN or an empty referrer. Filtered clicks go to a page you set and stay in the click log with the reason.
Rule criteria and conditions
Almost every Binom criterion has a condition with the same name: country, region, city, ISP, IP, proxy, device, model, browser, OS, language, referrer and day of week. Token criteria become the URL Parameter condition. Inside a stream you join conditions with AND (All) or OR (Any), and list several values of one condition with commas.
- The only operators are is and is not. There are no regular expressions.
- Time conditions use UTC. Statistics use the time zone in your profile settings.
- There is no equivalent for Continent, Connection Type, Datacenter or Smart Rotation. For data center traffic use the bot filter signal instead of a rule.
The full list is in the conditions reference.
Tokens
| Binom | TDS.SO |
|---|---|
{clickid} | {click_id}, 32 characters |
{country} | {country} or {country_code}, the country code |
{user_agent}, {language} | {ua}, {lang} |
{os_name}, {browser_name} | {os}, {browser} |
{device_type} | {device}: pc, mobile, tablet |
{t1}…{t30} | {name} of any GET parameter, for example {sub1} for ?sub1=abc |
{ip}, {city}, {region}, {isp} and {referer} are the same. There are no campaign tokens. If your network stores the click ID in a field with a length limit, check that it accepts 32 characters. The full list is in the macros reference.
Redirects and landers
| Hide referrer in Binom | TDS.SO |
|---|---|
| None | 302 Temporary |
| Meta refresh / Double meta refresh | Meta Refresh / Double Meta Refresh |
There is no equivalent of Smart meta refresh. TDS.SO also has JavaScript, iframe and button redirects, a preloader and a landing page on your domain: see the redirects page.
Integrated landers move as static pages. Upload the HTML or a ZIP, or build a page with the AI generator, and put the offer link in the page itself. There is no lander click URL like /click?lp=1.
Conversions and postbacks
If Binom only routes your traffic, the network side does not change: the click ID still reaches the offer, and the network counts conversions on its own.
To count conversions in TDS.SO, switch the tracker on in Settings → General → Tracker, create the offer with {click_id} in its URL, attach the offer and a traffic source to the link, and copy the postback address from Tracker → Conversions into the network. Binom's cnv_status and payout parameters are understood as they are. cnv_id is not, so name the click ID parameter click_id, clickid or subid in the network's postback template. Details are in the postbacks docs.
Run the pilot campaign through both trackers for a week and compare conversions one by one. The article on why tracker and network numbers differ lists the usual causes.
Plan: one domain at a time
- Inventory. For each campaign write down the domain, path, rules, default paths, bot settings, redirect mode and tokens. Mark rules that use criteria TDS.SO does not have.
- Server. Install the TDS.SO server on a separate VPS with one command. The installer stops nginx and Apache, so Binom campaigns on the same server would stop opening.
- Templates. Build templates from the tables above. Save repeated streams with Save all streams as a set.
- Pilot domain. Add the domain in the dashboard and create links with the same path (Slug after / → Custom), or Just / for the whole domain. Then point the domain's A record to the new server. Until a link exists, the domain answers
404. - Test. Send clicks from different countries and devices, check streams and the bot filter, and compare a week of numbers with Binom.
- The rest. Move the remaining domains the same way, export the Binom reports you need, and cancel the licence when clicks on it stop.
Until you switch Binom off, going back is one DNS change: point the A record back to the Binom server. Domains you have not moved keep working on Binom the whole time.
Help with the move
There is no import tool. Send screenshots of a campaign's rules and paths in Telegram or leave a request on the switching page, and we will tell you what moves before you start. Help is free. Plans start at $9.99 a week with unlimited clicks and domains: see pricing. The full reference is in the docs.
Questions
Can I import campaigns from Binom?
No. You recreate templates and links by hand using the mapping tables. For many similar campaigns, build one template and create links from it in bulk or through the API.
Will my campaign URLs stay the same?
Yes, if the path is one segment: create the link with a custom slug equal to the old path, or use the whole domain. A path with a slash inside it cannot be reproduced, because a link is looked up by the first path segment.
Do I need Binom Protect or a separate anti-fraud service?
Bot filtering is built into every TDS.SO plan, with levels from Standard to a JavaScript browser check and custom signals. Whether it is enough for your traffic is something to check on the pilot domain.
Can TDS.SO run on the same server as Binom?
No. The installer stops nginx and Apache, so Binom campaigns on that server would stop opening. Use a separate VPS.
What happens to my Binom statistics?
They stay in Binom. Export what you need before you cancel. TDS.SO counts from the first click on the new links.