Track Visits Using Redirect Method
With a redirect method you track visits via campaign URL of a redirect campaign in PeerClick.
This is a classic method that redirects a visitor through PeerClick servers. Because of that, you can use a lot of path-altering options, such as rule-based paths, weights, A/B testing or AI. However, it may not be compliant with every traffic source.
Traffic will go the following way:
Traffic channel → Tracker campaign link → (optional) Internal tracker redirects (Meta Refresh / Double Meta Refresh) → Destination link
Pros:
Use path altering options, such as rule-based paths, weights, AI or A/B testing;
Use redirect modes to hide referrer data;
Easy to implement - for many cases, it doesn't require adding any scripts to a landing page;
Can grab visit information (CEP parameter) from either a click URL, cookie, or HTTP referrer data.
Cons:
Not complainant with some traffic sources (such as Facebook Ads (now Meta Ads));
Tiny bit slower, because there is redirect through PeerClick servers;
A redirect visible in a browser's address bar may discourage visitors from continuing to your page.
Track Visits Using Direct Method
With a direct method you track visits via direct tracking URL of a direct campaign in PeerClick.
A direct method of tracking uses cookies and local storage (in that order) to pass visit information between sites.
Traffic will go the following way:
Traffic source → Destination link
There is no unnecessary redirect, and the visit is registered by the tracker when the user goes to the lander or offer where the pixel is installed.
Pros:
Faster, because there is no redirect through PeerClick servers;
Compliant with all traffic sources, including those that don't allow rotating destinations (such as Facebook Ads (now Meta Ads);
Can track organic traffic.
Cons:
Doesn't allow for landing page rotations, such as rule-based paths, weights, A/B testing or AI. Offer rotations are still possible (if landers are used);
Doesn't support using various redirect modes to hide referrer data;
Requires access to a promoted page's HTML code to insert a JS script.
Track Visits Using Website Protection Direct Method
With a Website Protection direct method you track visits via website URL of a website protection campaign in PeerClick.
Your offer gets the most qualified traffic according to your target audience.
Traffic will go the following way:
Traffic source → Destination link
There is no unnecessary redirect, and the visit is registered by the tracker when the user goes to the lander or offer where the Website Protection code is installed.
There is no unnecessary redirect, and the visit is registered by the tracker when the user goes to the lander or offer where the Website Protection code is installed.
Pros:
Provides max-level traffic filtration;
Compliant with all traffic sources, including those that don't allow rotating destinations (such as Facebook Ads (now Meta Ads);
Can track organic traffic.
Cons:
Tiny bit slower, because waits for appeal answer to PeerClick servers;
Doesn't allow for landing page rotations, such as rule-based paths, weights, A/B testing or AI. Offer rotations are still possible (if landers are used);
Doesn't support using various redirect modes to hide referrer data;
Requires access to a promoted page's code to insert a PHP / JS script.
Check Required Conditions of Visits Tracking
Visits in the tracker record correctly if the following conditions are met:
1. Traffic at the traffic channel side must be launched to the URL that tracks visits:
to a campaign URL for redirect campaigns;
to a direct tracking URL for direct campaigns;
to a website URL for website protection campaigns.
2. The domain used in pixels must be parked, must not be banned / not paid.
3. The link of the landing page / offer specified in the campaign must work on a direct transition (for example, the affiliate program can close the offer).
4. The campaign must be active (not paused).