How to Choose an Ad Tracker: A Checklist for 2026

Hosted or self-hosted

A self-hosted tracker runs on your server. You control the data and pay for the licence and the server, but you also own updates, backups, scaling and uptime. A hosted (cloud) tracker runs on the vendor's infrastructure: you sign up and start, and the vendor handles operations.

Ask yourself who will be woken up when the tracker is down at 3 a.m. If the answer is nobody, choose hosted.

Pricing models

• Per event (clicks or impressions): cheap to start, expensive to scale, and you pay for bot clicks too.
• Flat plans with feature or seat tiers: predictable at any volume.
• Overage fees: read what happens when you exceed a limit. Some trackers stop redirecting.

Core tracking

• Custom tracking domains with automatic HTTPS.
• Enough sub ID slots (10 or more) and traffic source templates for the platforms you buy.
• S2S postbacks with status mapping, and a click log you can search.
• Several redirect modes, for the cases where a plain redirect is not allowed.
• Redirect speed. Ask for real numbers from your GEOs; every 100 ms costs mobile visitors.

Routing and testing

• Rules by GEO, device, OS, browser, language, connection type, schedule and your own parameters.
• Weighted rotation of landing pages and offers, and split tests across whole paths.
• Daily caps with a fallback offer, so traffic is not wasted when a cap is hit.

Traffic quality

• Bot and datacenter filtering included, not sold per click by a third party.
• A way to route suspect traffic separately and still see it in reports.
• Clear reasons in the click log, so you can argue a refund with the source.

Integrations and data

• Conversion APIs for the ad platforms you buy on.
• Affiliate network templates with the right macros.
• An API and exports, so your data is never locked in.
• Cost import or cost per click settings, otherwise ROI is a guess.

Team and security

• Roles for team members, and the option to hide revenue or cost columns from some of them.
• Two-factor sign-in, session management and an audit log.
• Data processing terms and a clear retention policy.

Planning the move

1. List your sources, networks and postback URLs.
2. Recreate one campaign end to end and fire a test conversion.
3. Run old and new trackers side by side on a share of traffic for a few days and compare clicks and conversions.
4. Move campaigns in batches, and update the networks' postback URLs as you go.
5. Keep the old tracker read-only until late conversions have arrived.