Cloaker vs Tracker: What Is the Difference and How They Work Together

Newcomers often ask: “Do I need a cloaker or a tracker?” It is a bit like asking whether you need a lock for the door or a cash register. They are different tools for different jobs, and mixing them up costs money: some people pay for bots because they thought the tracker was protection, others cannot see their profit because the cloaker has no postbacks.

In short: the difference between a cloaker and a tracker

• A cloaker (a traffic filtering service, also called a cloaking service) decides who gets through to the offer. On every visit it checks the network, device, browser and behavior and sends the visitor either to the offer or to a safe page, the White Page. More in what is cloaking.
• A tracker counts what the traffic brought in. It records clicks, ties them to conversions through postbacks, accounts for cost and shows profit and ROI across breakdowns. More in tracker for affiliate marketing.

The cloaker answers “who is this?”, the tracker answers “what did it cost and what did it earn?”.

Side by side: what each one does

The overlap is small. That is why media buyers keep both systems for years. How to pick the second one is covered in how to choose an affiliate tracker.

Where each one sits on the click path

A visitor's path from the ad to the offer looks like this:

1. A person clicks the ad. The platform appends its own click ID (fbclid, gclid, ttclid) and your parameters to the link.
2. The filter checks the visit and decides: offer or White Page.
3. The tracker records the click, assigns its own ID and sends the visitor to the offer, adding that ID to the parameter for the affiliate network.
4. The person submits a lead. Later the network sends a postback with the click ID.
5. The tracker finds the click and records the conversion with its status and payout.

Steps 2 and 3 can live in different systems or in one. That determines the setup and the places where it can break.

Three ways to connect a cloaker and a tracker

Setup 1. Filter in front of the tracker

The ad points to your landing page, where the filter runs. Visitors who pass go through the tracker link to the offer. The tracker only sees clean traffic.

Pro: the tracker is not cluttered with bots. Con: two systems, two click IDs, and you need to pass the filter's ID into the tracker so you can match the data later.

Setup 2. The tracker queries the filter

The ad points to the tracker, and its flow has an external filter: the tracker sends the visit data and gets back “let in” or “do not”. Routing decisions stay with the tracker.

Pro: all routing lives in the tracker you already know. Con: the filter only sees what the tracker passes along, so checks that need the visitor's browser do not work in this setup.

Setup 3. Everything in one service

Filtering and money in one dashboard: one click ID, one database, one set of reports. Blocked clicks do not count toward cost, and passed clicks show their conversions immediately.

Pro: nothing to drift apart, easier troubleshooting. Con: if you have had a tracker set up for years, moving takes time.

How not to lose the click ID between systems

A two-system setup almost always breaks in one place: passing the click ID. The rule is simple: the ID that comes back in the postback must belong to the system that receives that postback.

Typical mistakes:

• the filter passes its own click ID to the offer, but the postback is set up to the tracker, which does not know that click;
• the tracker writes its ID into sub1, and the filter overwrites or strips that parameter along the way;
• the platform's ID (fbclid) is put into the parameter where the network expects the tracker's ID, so the postback arrives but attaches to nothing.

Tip. Before launch, walk the path yourself: click the ad link, see which parameters the offer opened with, and send a test postback with that ID. If the conversion attaches, the setup works.

How click IDs and sub IDs work is covered in Click ID and Sub ID, and the postback itself in the article on S2S postback.

Why the cloaker and tracker numbers do not match

A discrepancy is the normal state of a setup, as long as you understand why:

• The cloaker sees everyone. Its statistics include both passed and blocked visits. Compare only passed visits with the tracker.
• Some people drop off on the way. A visitor passed the filter but closed the page before reaching the tracker. The slower the landing page, the bigger the gap.
• Different uniqueness rules. One system merges repeat visits, the other counts each one.
• Different time zones. A report for “yesterday” can cover different hours in the two systems.
• Parameter errors. Some clicks landed in a different tracker campaign because of a wrong link.

If the gap between passed clicks and tracker clicks suddenly grows, look for a slow landing page, a broken link or overwritten parameters.

How to reconcile numbers without stress

Agree on a few simple rules and reconciliation will take minutes:

1. One time zone across all systems, or at least a clear idea of how many hours apart they are.
2. One baseline: the filter's passed clicks against the tracker's clicks, not all visits against all clicks.
3. One unit of time: compare closed days, not the current one, which is still being filled in.
4. An acceptable gap: write down what percentage of discrepancy is normal for your setup. While the gap stays within it, there is nothing to hunt for; when it grows, that is a signal, not noise.

Reconcile conversions separately: the tracker against the affiliate network dashboard, by click date.

Example: one campaign through the eyes of two systems

The numbers below are an illustration, not a benchmark. Say an ad link received 1,000 visits in a day.

The cloaker covers the top of the table: how many visits there were and why 150 of them did not see the offer. The tracker covers the bottom: what the visitors who got through brought in. Neither system can fill in the other's rows.

Here is the practical takeaway. If you only look at the tracker, you do not know how many bots you paid the platform for. If you only look at the cloaker, you do not know whether the campaign pays off. If both systems are linked by one click ID, you can answer the question that really matters to a media buyer: what does one real visitor cost and what does he bring in.

What to do with blocked clicks

Blocked visits are not junk to throw away; they are data:

• they show which placements, networks and devices send bots;
• in native and push advertising, placements where the filter blocks nearly everything are worth turning off right in the ad network, so you stop paying for them;
• a spike of blocks for a single reason signals that the traffic source has changed.

More on the signs of invalid traffic in how to filter out bots.

Pass rate is not a quality score

One trap in a cloaker and tracker setup is treating the share of passed visits as a grade. A high pass rate does not mean the filter is “bad”, and a low one does not mean it is “good”. If you buy traffic on a platform that passes a verified click ID, most visitors may reach the offer, and that is normal. The real warning sign is different: when almost nobody reaches the offer, the rules are probably cutting real people along with the bots. Decision reasons help you sort it out; see why a click went to the White Page.

How ArtisanClo handles it

ArtisanClo is a filter and a tracker in one dashboard, and every flow has an operating mode:

Tracker mode without filtering works when you connect via the PHP file, the Keitaro filter or the Binom gate.

If you keep your own tracker, there are two paths:

• An external tracker in Cloaking mode. In the Tracker step you pick a tracker from the list (Keitaro, Binom, RedTrack, Voluum and others) or a custom one. The dashboard shows a parameter like external_id={click_id} for the offer link and highlights whether it is already there. Through this parameter the click ID goes to the tracker and comes back in the postback, and CR and revenue appear in the cloaker's statistics.
• A filter inside the tracker. In Keitaro, ArtisanClo runs as a flow filter; in Binom, as a gate in the landing page. That is setup 2 from the list above. Step by step in Keitaro + cloaker and Binom + cloaker.

For a cautious start there is shadow mode: with the PHP file, the Keitaro filter or the Binom gate, every visitor goes to the offer, and the log shows who the filter would have blocked. That way you can evaluate the filter on your own traffic without losing anything.

Ready-made integrations are listed on the tracker integrations page.

What to choose: a cloaker, a tracker or both

• A white-hat offer where you only need to count money: a tracker. It is still useful to see how many clicks went to bots, so a mode that flags bots in reports gives you more than bare tracking.
• You need to block bots, reviewers and spy tools, and you already count money: a filter linked to your tracker through the click ID.
• You need both and do not have a tracker yet: it is easier to start with one service where both modes live together. Before you buy a cloaker, check whether it includes a tracker and a reason log.
• A team of several media buyers: unified reporting and access control matter: who sees cost, who edits flows, who only views reports.

The bottom line

A cloaker decides who sees the offer; a tracker counts how much money that brought in. They do not replace each other, they complement each other. You can connect them in three ways: filter in front of the tracker, filter inside the tracker, or everything in one service. In any setup, the key is one click ID that travels the whole path and comes back in the postback. What both halves of ArtisanClo can do is on the features page.