Filters tab contains one of the most important campaign setting. Here you define the behavior of your safe/money pages.
If the visitor satisfies the filters settings there money page (your lander) will appear. If the visitor doesn't pass the filters, than we say that visit is filtered and the safe page is shown.
Active - applies the filter settings you define.
Allow all - redirects every type of traffic to a money page.
Filter all - redirects every type of traffic to a safe page.
On High Alert - this checkbox enables a special filter mode. When an unwanted visit is tracked, the next five visits will also be sent to the safe page, no matter where they came from.
Allow any traffic - allows all kinds of traffic to visit your landers.
Allow Desktop traffic - allows to visit your landers only from a desktop.
Allow Mobile traffic - allows to visit your landers only from a mobile devices.
Allow only whitelisted ISPs - you should create an ISP (Internet Service Provider) whitelist for your target country in Settings > ISP White Lists before you can start using this filter. When this checkbox is checked, traffic from other ISPs will be blocked.
Frequency cap - is the additional filter which you can use to limit the number of visits of your campaign. The frequency of visits is calculated by the cookies. By setting the frequency cap you are protecting your landers from bots and from unwanted visits; including your competitors. It is recommended to set the frequency cap equals to 1 when launching a campaign and increasing this value during the optimization process.
Zeustrak alert:
IMPORTANT NOTE: The frequency capping feature requires a cookie file to be set on your landers which are placed on your domains. This feature is turned on by default and the cookie file is set without any notification to the user. That cookie contains the info about the user which may be interpreted as personal data, however, this info does not contain any specific data that can identify a specific person.
In this case, if you are targeting EU citizens you might need to inform your visitors about that cookie file before they visit your landers. To keep it more simple you could use, for example, a template provided by the COOKIE CONSENT by Insites or create your own.
Facebook Filter - black list / data base of IP-addresses and other specific markers related to Facebook.
Facebook Prefetch Filter - the Facebook Android app generates a lot of preview traffic, loading the page before the user has actually clicked on the ad. If you switch on this option, the Facebook app will be forced to load your lander from a real ad click and the preview traffic will not be displayed in your statistics.
IPv6 Filter - use this option to send any IPv6 traffic to the safe page.
Filter Empty Referrers - use this option to send any traffic wihout a referer to the safe page.
AdWords - black list / data base of IP-addresses and other specific markers related to Google AdWords.
VPN/Proxy/Tor/Hosting Filter - data bases of IP-addresses of IP-replacement services.
Luminati (js filter) - data base of IP-addresses and other specific markers related to Luminati's services. This is a JavaScript solution, so there will be redirect and some delay to perform the tests.
Require Gyroscope on Mobile (js filter) - use this option to send any traffic without physical gyroscope on the device (e.g. smartphone simulator) to the safe page. This is a JavaScript solution, so there will be redirect and some delay to perform the tests.
Basic Headless - determines headless browsers. These types of browsers are often used by bots. If a visit from a headless browser is detected such visit will be sent to the safe page. Can detect only simple headless technology.
Advanced Headless (js filter) - also determines headless browser but this time more efficiant and detects almost all hidden headless browsers. If a visit from a headless browser is detected such visit will be sent to the safe page. This is a JavaScript solution, so there will be redirect and some delay to perform the tests.
WebRTC Leak (js filter) - detects WebRTC leak. If a leak is detected this visit will be redirected to a safe page.
Time Zone Consistency (js filter) [Beta] - this filter compares two time zones: the time zone expected by location and the actual (system) time zone of a visitor. If these numbers don’t match, such visits will be sent to the safe page. This is a JavaScript solution, so there will be redirect and some delay to perform the tests.
Language Consistency - this filter compares the language of a browser expected by location and the actual (system) language. If these languages differ, such visits will be sent to the safe page.
In addition to the basic filters you can also set Custom rules.
Status - activates or disables a rule.
Type: Filter - this blocks traffic according to a defined rule. Allow - this allows traffic according to a defined rule.
To be able to use Custom rules, you'll need to press the Add condition to rule. There is a wide variety of conditions that can satisfy all your needs.
