How does an arbitrage guy pick a tracker? A buddy recommended it, or everyone’s using it. Then you actually start working with it, and it turns out the functionality you need just isn’t there: sure, it works, it counts, it tracks — but it could be… a bit more convenient, somehow. Not just working, but actually helping you push ROI up and make more money. So what should a good gambling tracker have on board? That’s exactly what I’m about to walk you through.
0. Standard Redirects
The tracker has to remember the visitor’s ID and pass it both ways — along with the rest of the postback data. A visitor clicks, the click gets an ID, and the tracker never loses track of it from there. First it pushes the ID forward: as a macro dropped into the link to the offer or landing page, so the affiliate network picks it up as its own sub or clickid. Then it takes it back: the advertiser sends a postback about a registration, deposit, hold, or cancellation, and the tracker matches it to the original click and grabs everything that came with it — geo, amount, tags.
The display method itself needs to adapt to the traffic source. Some sources want a plain redirect with no caching (push, pop, teaser networks); others need the link hard-stuck to a specific user; others call for a meta-refresh or a JS redirect; and others want an iframe, or a file served with no redirect at all.
Without this baseline, there’s no point reading any further: if the tracker can’t reliably tie a conversion back to a specific click, source, and creative, you’ll never know what actually worked and what just burned your budget. This is the bare minimum every sane tracker has, for any vertical.
1. Goal-Based Conversions with Accurate Conversion Dates
The standard goals in gambling are registration, first deposit, and repeat deposits. In most trackers — including some of the best-known ones — conversions get stamped with either the click date or the date of the first conversion (registration). In a tracker built right for gambling, every conversion gets its own date, and that’s the date it shows up under in the stats. That rules out situations where an FTD lands today, but your tracker’s stats show it two weeks back, because that’s when the click happened.
In practice, that means separate leads for separate events, not one lead just flipping through statuses. Registration gets its own lead with its own registration date. Once the player makes a deposit, a new lead shows up with a new external ID and its own date — the actual payment date, not the click or registration date. Same story with revshare: every subsequent payment is its own lead, with its own date, amount, and status — not just tacked onto the old record.
Why does this matter so much specifically in gambling? Weeks, sometimes a whole month, can easily pass between a player’s registration and their FTD. If the tracker keeps one lead for the entire funnel, your reporting follows the registration date instead of the date the money actually moved: registration in January, FTD in February — and the stats book that deposit as a January event. Deposit caps and monthly balances drift out of place, and comparing periods against each other or reconciling with the affiliate network becomes nearly pointless.
2. Optimization Features
First, parameters in the postback. Second, a server-side Facebook pixel and the ability to feed Google a conversions list on a schedule. Both matter most in gambling specifically, where you can’t just slap a standard pixel onto the casino’s own site.
Parameters are simple enough: the outgoing postback shouldn’t just carry the bare fact that a conversion happened — it needs the details too: event type, amount, currency, tags. Otherwise, the ad network only sees “a lead came in” and optimizes blind — on quantity, not quality.
Facebook is trickier. In 99% of cases, affiliates drop the pixel code on the “Thank You” page after the lander, but in gambling, the player registers and deposits on the casino’s own site, not your lander — there’s simply nowhere for you to insert a pixel. That’s where the server-side pixel — also known as the Conversions API — saves the day: the tracker fires the event to Facebook straight from its own server, no access to the casino’s site required. As a bonus, these events don’t get clipped by ad blockers or iOS restrictions either.
Ideally, you can assign a standard event to every stage of the lead — new, hold, approved: say, Lead when it comes in and Purchase on approval, with the tracker attaching the amount and currency to Purchase automatically. Fans of optimizing off a pile of different events get to find out firsthand that it’s all bullshit and one single Lead event is plenty. The only thing that matters is firing it on deposit: you can scope the pixel down to specific goals, so the ad account learns from deposits, not registrations.
With Google, a postback is a non-starter — you can’t fire a conversion over with a simple request. So the scheme runs in reverse: the tracker keeps a live CSV export, and Google Ads pulls it on its own schedule. Every row has the click’s gclid, the goal code, conversion time, payout, and currency. Each pull only returns leads that are new since the last one — no duplicates.
The goal code is the conversion’s name, which means registration and deposit go into Google as separate conversion actions: you can optimize on deposits and leave registration as a secondary goal that doesn’t factor into bidding. Set up a separate export for every ad account, and always filter it — by flow, domain, or campaign — otherwise every single lead you have ends up in there. Google won’t pull a file more than once a day on a single schedule, but nothing stops you from setting up several schedules at different times: four of them, six hours apart, is already more than enough for solid optimization.
3. Split-Testing Functionality
Running a plain 50/50 split across two ways is something almost any tracker can do. But ideally, you want a whole arsenal of options:
- An ML-powered split that shifts weight toward whichever way has the better conversion rate or EPC.
- Cap-driven split adjustment — for both registration and deposit caps — so the system automatically shifts traffic to ways with room left in their caps and avoids overflow.
- Split levels. Say traffic runs across 3 ways, each with its own cap. Once way 1 hits its cap, you can set a backup cap on it (or 10 backup caps), and traffic will move through them one after another. You can also prioritize backup caps — choosing the order they get filled in.
- Geo-splitting as a first stage. You can point all your traffic at one single link, create a flow or split for each geo, and the system will sort clicks by country at the very first level before picking a link for them.
Put it all together and you can build massive structures — a flow with 10 ways, each carrying 10 caps of its own. They all spin inside the split, the ML shifts more weight toward whatever’s turning the most profit, and cap overflow is off the table. And any returning player lands right back on their own product every time — the system remembers them.
4. Capturing Deposit Amounts for Every Player
The mechanics are simple: the advertiser or affiliate network sends the exact deposit amount in the postback, not just the bare fact that a deposit happened. The tracker takes it in, ties it to a specific player, and totals it up by flow and way. It’s best to tie it to the network’s customer ID rather than the click — that way, repeat deposits for revshare get counted correctly too.
Once the advertiser hands over that data in the postback, you get to see your own traffic quality by flow in something close to real time, and you’ll know in advance which flows are about to get cut off and which ones are about to get an uncap and a bumped payout. Small, sparse deposits on a flow are an alarm bell — one that rings long before the network pulls the plug on you. Steadily large deposits are your cue to go negotiate a better rate or ask for the cap to come off. Without the amounts, all you see is a lead’s binary status — approved or not — and you find out about the problem, or the bonus, after the fact, once the decision’s already been made without you.
5. A Built-In Cloak That Handles Practically Any Traffic Source
Facebook is stupidly easy to screw over. All it takes is: plain redirect → four checkboxes → a blank page instead of a real white page → a CAPI pixel with a developer token, which is that same server-side pixel from point 2. Zero hassle building white pages: FB’s moderators scan the site for banned words, and there simply aren’t any on an error page or a blank page. And no, I have no idea what everyone keeps whining about.
Google is a lot harder to screw over, but it is still doable: you won’t find a nastier traffic source, and it won’t fall for a half-assed attempt. Here’s what you’ll need:
- A list of the geos you’re actually running — and if you genuinely can’t restrict geos, then at least languages and excluded countries. Running worldwide traffic in English is a dangerous move.
- A real white page — an actual site built for humans, with contacts, a policy, and proper markup. Name the file
home.htmlorhome.php, and neverindex.html— that’ll break everything. - A black page — best served as a local file with a randomized name.
- The “Verify Ad Click” checkbox — and this one is absolutely mandatory. Anyone who shows up without an ad click ID in the link — that same
gclid— never gets to see the black page. Skip this checkbox, and you’re better off not running Google traffic at all.
And this needs to be an actual cloak paired with a specific white page — not some duct-taped flow setup pretending to be one. It parses every single click on its own and decides which version of the site to show: the white page to moderators and bots, the black page to real people. Ideally, both live locally, right next to the cloak’s processing file, and redirects as a concept don’t even enter the picture. That’s exactly how AlterCPA One is built, by the way — a tracker that ships with a cloud-based, self-learning cloak built for Google.
6. Importing Spend from Any Source
Spend doesn’t just materialize out of thin air inside the tracker — it has to be imported: automatically, by link, by hand, or via API. And it has to work with any source — ad networks, teaser networks, auto-buying tools. There’s almost always just one condition: the network needs to pass the creative, ad, or ad-set ID into one of the UTM tags, otherwise the tracker has nothing to match its clicks against, and your spend ends up floating separately from your revenue.
Get the integration working, and you’ll see your full ROI in one place: revenue finally lines up against cost. For every flow and way, you get CPC, spend, profit (revenue from hold and approved leads minus spend), and ROI on that combo. Auto-import only needs to run a couple of times a day — covering yesterday and today — and you’ll never have to manually cross-check statements from two different dashboards again.
Just make sure you find out exactly how your tracker calculates ROI first. In some systems, break-even is 100%, and anything below that is a loss. In others, break-even is 0%: negative means a loss, positive means you’re already in profit. Mix the two up, and you’ll be celebrating a 90% ROI that’s actually a 10% loss.
7. Maximally Flexible Stats and Analytics, Ideally Drill-Down
So that any question along the lines of “what converted, when, from where, and with which subs” gets answered in a couple of clicks, no dancing with tambourines required. Drill-down, in practice, means report breakdowns nested inside each other in any order you like: by flow first, then by geo inside the flow, then by sub inside the geo, then by date inside the sub. Every level expands with a plus icon, and you don’t have to rebuild your filters for every new question.
Ideally you’ve got somewhere around twenty parameters available for breakdowns — date, hour, flow, way, site, geo, device, browser, IP, tags, subid, and so on — and you set the nesting order just by dragging things around with your mouse. Feel like crunching the numbers by hand? Export the report straight to Excel.
And all of this needs to stay fast even at high volume. Fresh clicks get pulled from a “hot” table, and the heavy archive only kicks in once the report period actually reaches back into it — a question about today’s traffic shouldn’t have to sit around while the tracker digs through six months of history.
8. Flexible Pricing, Free Features, and Both a Self-Hosted and Cloud Version
Everyone’s needs are different. Newcomers poking at a single flow, trying to push it into profit, need a free solution and a cloud version — AlterCPA Red, say — so they don’t have to give themselves a headache over servers and other such filth. Bigger players need their own feature set, and at serious volume, a self-hosted version like AlterCPA Lite: no server neighbors, no artificial limits, and horsepower you control yourself (shoutout to the pop-under crowd). And a perfect tracker needs to cover all of these needs for a reasonable amount of money, without forcing anyone to pay for bells and whistles they’ll never touch.
9. Site Storage
You’ll need this if you’re running custom prelanders or white pages (handy for certain traffic sources). It’s basically the same scheme as the local cloak files from point 5, except the sites don’t sit on separate hosting — they live in storage wired directly into the tracker itself. Upload the site’s archive, pick it in a flow or way, and when a click comes in, the tracker serves it straight up, with no redirect at all.
This setup comes with a handful of perks. Every site in storage gets its own stats — CR, EPC, approval rate, earnings — across every flow and way it’s running on, and macros like {click} or {geo} get substituted straight into the page’s code. Every site’s address is obfuscated, too: there’s no way to guess the ID from it, or even how many sites you’ve got in there. And if it’s your own private storage, it lives on a separate server, the same one your domains get parked on: less chance of catching a ban because of bad neighbors, and it’s harder for anyone to trace a domain back to the tracker itself.
Not everyone needs this: if you’re running straight to offers with no prelanders or white pages of your own, you’ll live just fine without storage. But wherever you need your own white and black pages on a regular basis, everyone finally gets to do their own job: you pour the traffic, the cloak filters it, the tracker counts it, and the bots can go fuck themselves.
Bottom Line
These 9 points are the bare minimum. Skip site storage if you genuinely don’t need it — you’ll survive. But picking a tracker without everything else means settling, and making a seriously questionable call.
And if you haven’t been in gambling all that long — pay special attention to whether a free plan even exists. Pricing in general, really. And if you think the market only really has room for 1–2 solutions everyone has to bend around — forget it: there are better Alternatives out there, just running on a smaller marketing budget.