Exort Tracker Documentation

Exort is a self-hosted affiliate tracker. You install it on your own server, and it tracks your clicks, conversions and campaign profit — with no traffic data leaving your infrastructure.

This documentation covers installing Exort, setting up campaigns, and running the tracker in production.

Who it is for

Exort is built for affiliate marketers and media buyers who need:

• Full control over their data — clicks and conversions are stored in your own database, not a vendor’s.
• Speed on the redirect path — click processing runs close to your traffic, without a round trip to someone else’s cloud.
• No per-click pricing — the cost of your server does not change because a campaign scaled.

If you have used Keitaro, Binom, Voluum or RedTrack, the concepts here will be familiar: campaigns, flows, landers, offers, traffic sources and postbacks.

Quick start

Three steps get you from an empty server to a tracked click.

1. Get a server. Ubuntu 22.04 or later, 2 GB RAM, 10 GB disk. See Choosing a server for details on specs and location.

2. Install. One command on a fresh server:

curl -sSL exort.io/install.sh | sudo bash && sudo exort install

The installer is interactive and takes about two minutes. See Installation for the full walkthrough.

3. Log in at http://<your-server-ip>/admin with the credentials the installer prints when it finishes.

What is documented

The documentation is organised the same way the tracker itself is, so what you see in the admin panel maps to a section here.

Getting Started — picking a server, installing, creating an administrator, connecting a domain, and building your first campaign.

Campaigns — creating campaigns, the tracking URL and its parameters, sub IDs and source tokens, click uniqueness, cost tracking, and reading the campaign report.

Flows and Traffic Distribution — routing traffic by conditions: filters on geo, device and OS, weighted rotation across landers and offers, redirect types, bot filtering, and split testing.

Landers and Offers — managing landing pages and offers, lander types, uploading files directly to the server, payout types, conversion caps, and macros.

Traffic Sources — registering sources, mapping their tokens, and reporting conversions back to them.

Conversions and Postbacks — how conversion tracking works end to end, receiving postbacks from affiliate networks, conversion statuses, and what to check when a postback does not register.

Reports and Analytics — the dashboard, custom reports, trends, the click log, and how data is stored for fast querying.

Domains and SSL — adding tracking domains, automatic HTTPS, and running behind Cloudflare.

Users and Access — team roles, per-entity permissions, and hiding profit figures from selected users.

Server and Maintenance — the CLI reference, updates, backups, logs, license activation, migrating to another server, and troubleshooting.

Integrations — the tracking script, conversion pixels, and third-party services.

Reference — the full macro list, glossary, FAQ, and release notes.

Getting help

If something in this documentation is wrong, unclear or missing, tell us — the gaps we hear about get filled first.