TDS Tracker and Profiles: Linking Clicks, Proxies, Accounts

GetAntik editorial team · October 12, 2026 · 9 min read

How to connect a TDS tracker to antidetect profiles so you can trace conversions back to specific proxies and accounts, with setup steps and common mistakes.

Why bother linking the tracker to a profile at all

A team running dozens of ad accounts eventually hits the same wall: clicks exist, conversions exist, but there's no way to tell which exact account, proxy, and creative produced a given lead. A tracker shows aggregated campaign numbers, but it won't tell you that account #14 on a Warsaw proxy has been bleeding money for three days while account #22 with the same creative is profitable. The difference might be warm-up speed, IP quality, or someone forgetting to set the right timezone on one profile.

A tracker like TDS.ceo solves part of the problem — it counts clicks, conversions, and builds a funnel by source. But it knows nothing about the browser environment those clicks came from. Once you start cross-referencing tracker data with profile data — proxy ID, fingerprint preset, warm-up date — you get a way to find the actual causes of a failing campaign instead of just noting that "it's not converting."

This matters most for teams that have already gone through the exercise of calculating multi-accounting unit economics and know that a losing profile isn't an abstract number — it's a specific proxy that should be swapped out before it burns through the whole budget.

How the link works in practice

GetAntik supports TDS.ceo integration and lets you configure per-profile proxies individually. The logic is straightforward: each profile has its own proxy, its own fingerprint, and its own account/dashboard pairing. If you attach a separate tracker link or sub-ID to that same profile, you get an end-to-end chain: click → proxy → profile → account → conversion.

In practice it looks like this:

1. In TDS.ceo, you create a flow with unique sub-IDs for each profile-account pairing.
2. In GetAntik, the profile gets a dedicated proxy via the proxy manager — with availability checks and geo binding.
3. The tracker link with the matching sub-ID gets saved into the profile via bookmarks or profile notes.
4. Campaigns run strictly through that profile — no jumping between proxies, no manually editing links on the fly.

When a sub-ID is hard-linked to a profile, and the profile is hard-linked to a specific IP, the tracker report stops saying "source X delivered 40 conversions" and starts saying "profile 14, proxy PL-Warsaw-07, creative B — 40 conversions at 3.2% CTR." That's actionable data: you can compare proxies against each other, compare warmed-up profiles to fresh ones, and see exactly where performance starts to drop.

What this looks like in numbers

The difference is noticeable in practice. A team running 50 accounts without tying the tracker to profiles typically spends 2 to 4 hours per campaign figuring out "why it's not converting" — a media buyer manually cross-checks dashboard logs, CRM screenshots, and guesswork. With sub-IDs tied to profiles, that same diagnosis takes 10–15 minutes: open the report by sub-ID, see the dip concentrated in profiles sharing one proxy pool, draw the conclusion.

The second effect is faster bad-proxy replacement. If 5 out of 50 profiles show conversion rates half the average, and all five sit on proxies from the same provider or the same subnet, that's visible immediately in the sub-ID breakdown — not after a week of watching the dashboard. Swapping a proxy through the HollyProxy integration takes a few minutes; finding the cause would have taken longer.

Where teams usually go wrong

One sub-ID for multiple profiles. To save setup time, teams attach a single sub-ID to a group of 5–10 "similar geo" profiles. When a dip hits, it's unclear which profile is actually at fault — you're back to manually digging through account logs. The rule is simple: one profile, one sub-ID, no exceptions, even with a large profile count.

Swapping a proxy without updating the tracker. A proxy dies, gets replaced — but the tracker still carries the old geo or provider tag. Reports start lying: conversions get credited to the wrong country or provider. Any proxy change in the profile manager needs a matching update to the note or sub-ID, or the analytics fall apart within a couple of weeks.

Tracker configured, profile not. A team invests in setting up TDS but routes all profiles through the same proxy pool without separating by fingerprint. Then tracker data shows a conversion gap that's actually caused by a fingerprint-based block, not traffic quality. Before trusting the tracker's numbers, make sure fingerprint consistency on the profile is solid — otherwise you'll be optimizing the wrong thing.

Manually updating links across dozens of tabs. When the tracking link changes (new flow, new offer), it has to be re-entered in every profile by hand. Tolerable at 5 profiles, unmanageable at 100. The fix is bookmark templates: set up a bookmark structure with a placeholder once, then apply the template across all profiles at once instead of opening each one individually.

Table: what to check when setting up the link

Team access: who sees what

If several buyers share the tracker and the profiles, access becomes a question worth answering up front. Not everyone needs to see all 300 profiles and all flows in the tracker — usually a buyer works with their own pool of accounts and their own geo flows. GetAntik handles this with roles and limits: team member permissions let you restrict which profiles a given person sees, while a finance role can view profile spend without access to the browser sessions themselves.

A media buying team lead can get the full picture through the team dashboard: who's online right now, how many browsers are open, what the daily spend per profile looks like. That removes the need to ask every buyer individually what they currently have running.

A separate advantage is live view and remote control of a teammate's profile. If a buyer notices a colleague's conversion rate dropping on a specific account, they can connect to that same profile and watch what's happening in real time — without passing around passwords, without switching devices, without touching the verified fingerprint, and without risking a flag from logging in a second time from a different environment.

Warm-up and tracking don't conflict

Teams sometimes worry that adding tracking links to a fresh, unwarmed account looks suspicious to the platform — too fast a jump to ad activity. That concern is valid: an account with no browsing history, no ordinary activity, that immediately starts firing off ads with tracking redirects does look like a burner account rather than an organic one. So the tracker link should go in only after warming up the profile — once the account already has visit history, cookies, and ordinary behavior behind it. Warm-up and tracker analytics are sequential steps, not parallel ones.

When you don't need this at all

Not every team benefits from setting up sub-IDs for every profile. If you're running only 3–5 accounts, one offer, one geo, it's simpler to just check stats directly in the ad platform dashboard and the tracker's general report without per-profile detail. The added complexity pays off once you're past 15–20 profiles and manually cross-referencing data starts taking longer than setting up automatic linking would.

It's also not worth trying to link the tracker to a profile when traffic comes from organic sources rather than ad account clicks — there's simply nothing to pass into a sub-ID there, and the effort goes nowhere.

Setup checklist

• Figure out how many profiles actually need sub-ID-level detail (usually active campaigns, not your entire profile archive).
• Create a separate flow in the tracker for each campaign group, with room for a sub-ID per profile.
• Verify that each profile's proxy matches the flow's geo — otherwise the country-level report will be wrong.
• Run the profile through a standard warm-up cycle before attaching the tracking link.
• Save the link and sub-ID in the profile's bookmarks or notes, not just in the buyer's memory.
• Set up a regular check-in: review the sub-ID report every 1–2 days and cross-reference it against proxy status in the profile manager.
• Separate profile access between buyers using roles, so no one confuses someone else's campaigns with their own.

If your team has already built a solid process around profiles and proxies but has been running them without any tracker linkage, it's worth cleaning up the pool itself first — that's covered in detail in the piece on organizing hundreds of profiles without chaos. Structure first, analytics on top of it — do it the other way around and the tracker link will just collect garbage data.

FAQ

Do I need to change the sub-ID every time I relaunch a campaign? No, not if the profile and proxy stay the same. The sub-ID is tied to the profile-proxy-account combination, not to a particular campaign run. Change it only when the proxy changes or when the profile is handed off to another buyer.

Can one tracker be used across multiple antidetect accounts at the same time? Yes — that's exactly how the setup is meant to work: one flow in the tracker, many sub-IDs, one per profile. The real limit is usually the tracker's own cap on flows and sub-IDs, not the antidetect browser.

What if the tracker shows good click numbers but the account gets rejected in moderation? Those are different stages of the funnel. The tracker counts clicks and visits; platform moderation is a separate process that depends on whether the creative and landing page match the platform's policy. Linking the tracker to a profile only helps with traffic attribution, not with passing moderation.

Should tracking links be stored in the profile's cookies instead of bookmarks? There's no benefit to that — cookies hold session state and login data, not static links. Bookmarks or a text note in the profile are easier to work with: you can copy and update them without risking a broken session.

What if the same proxy is shared across several profiles to save on costs? You can still split sub-IDs by profile, but geo and provider will match across all of those profiles in the tracker report, which lowers diagnostic accuracy. If budget allows, it's better to keep a separate proxy at least for profiles running different offers — see the breakdown on choosing the right proxy type for the job in proxies for multi-accounting.

media buyingtracker integrationproxy managementad accountsteam workflow