What is ATracker?

ATracker is a self-hosted tracker sold as an instance license. You install it on your VPS or dedicated server; clicks, postbacks, and reports live on the license owner’s infrastructure, not in a shared SaaS cloud. This page defines the product. It is not a homepage and not a reuse of the site hero.

As a class ATracker does the same job as Keitaro or Binom: campaign URL, click row, click ID, routing to a landing and offer, inbound network postback, reports by campaign and sub_id. Cloud neighbours (Voluum and peers) host that loop at the vendor. Model differences sit on self-hosted vs cloud and the /compare hub.

Objects in the admin

The operator creates Sources, Landings, offers, affiliate networks, and campaigns with a flow. Tracking domains and SSL belong to the instance. For some GEO and antifraud setups there are Exit Nodes: the click can ingress at a regional edge, not only DIRECT on the main server. Menu names match the product — not “Traffic Sources” / “Landing Pages.”

Sources rarely push spend by themselves. Cost Import pulls spend from ads accounts (or CSV) and writes daily cost onto the campaign so Reports show ROI, not only EPC. Without mapping the cabinet’s external campaign id to a tracker campaign, the import is empty or mixes accounts.

Migration from other trackers

Tracker Import (Settings, Ops group) reads the Keitaro or Binom API and copies structure: campaigns, offers, landings, sources, and for Keitaro — networks and streams. Import is read-only against the source; the old tracker is not modified. Campaigns arrive paused until URLs and postbacks are checked. That is a product fact, not an argument that you should migrate.

What ATracker is not

Not the “tracker” class. The class is the tracker article. ATracker is one self-hosted instance of that class.
Not cloud Voluum/RedTrack/BeMob. Vendor-hosted cabinet is not the default delivery model.
Not a landing with a CTA. Registration, pricing tables, and “Professional Tracker for Media Buyers” do not belong here.
Not an affiliate network, not an MMP, not GA4.

Screen-level help lives in the docs, not in the glossary. The glossary answers “what is this product,” not “how to click the first campaign.”

Operations match any self-hosted tool: DNS and a certificate for the tracking domain, disk for logs, instance updates. There is no vendor “event pack”; the ceiling is the server and the license. Outbound S2S into ads accounts and landing pixels are the same layers as class neighbours: account optimization on one side, network payout on the other.

ATracker does not replace an affiliate network and does not count site sessions the way GA4 does. If you only need a tag on your landing without a click ID and an offer postback, that is not a tracker job.