Traffic filtering
The tracker has built-in traffic filtering tools. They allow you to block bots and spammers on various AlterCPA One blacklists.
The tracker has built-in traffic filtering tools. They allow you to block bots and spammers on various AlterCPA One blacklists.
The flow can be connected to an existing traffic filtering campaign. The flow will use all the settings of geography, languages, special filters, operating systems, browsers, protocols, black and white lists. At the same time, the settings of the target and dummy site, their methods of operation and the filter activity itself are ignored. Data on the verification of each visit is saved in the campaign click log.
You can also set up simple filtering manually. Manual filters are configured inside the flow in the "Filtering" section. The following global settings are available to you:
If a visit is blocked by manual filters or filtering campaign, a trafficback is shown to the user. This is analogous to a dummy site in a filtering campaign. The following settings are available:
When each filter is triggered, its type will be recorded in the filtering log: bots, geo, language, or blacklist. You can view the data on the triggering of filters in the "Statistics" section with the "Filter" criterion selected.
There is a belief that the headers and cookies that the tracker sends can affect the quality of filtering. To ensure that your advertising campaign is not banned, you can activate the “Do not send additional headers and cookies to visitors” mode. Of the minuses: this function also disables checking the uniqueness of clicks and breaks the way rotation mechanism. In most cases this is not critical. You can also prohibit sending headers only for trafficback.
Additional traffic filters are embedded inside each way:
If none of the ways fit the visitor, he will be directed to trafficback. This event will be recorded as "Trafficback" in the filtering log.