Video Tutorial
Setting up flows for Google Ads/Bing Ads, it is essential to enable:
- JS Fingerprinting;
- Automatic bot detection;
It is also recommended to enable:
- Google Click ID option (only for Google Ads);
- Filtering by time zone;
- Matching the browser's timezone to the visitor's location;
- Filtering by touchscreen (in the case of targeting ad campaigns only to mobile devices);
When configuring flows for Facebook/TikTok and native networks, it is not recommended to enable JS Fingerprinting due to the potential loss of a significant portion of traffic.
It is necessary to create a separate flow for each white page because integration files are unique in each flow to prevent the sameness of the code.
No need to redownload the integration script to apply flow settings!
After making changes, simply save the flow.
¶ Basic Setup
To create a flow, go to the Add Flow section.
Specify the flow's name:
Choose the countries from which visitors should be redirected to the black page.
If your target visitors can be from any country, leave the field empty.
Select the device types for which you want to redirect visitors to the black page.
This completes the basic setup for automatic bot filtering for Facebook, TikTok, native, and teaser advertising networks.
For optional configuration and integration script downloads, go to the Optional Configuration and Integration Setup sections.
If you are setting up a flow for Google Ads - proceed to the next section.
¶ Google Click ID Option
This setting enhances the bot protection level, so it is recommended to use it for Google Ads.
The Google Ads advertising network automatically adds special parameter Click ID (GCLID) to each link. If the Google Click ID option is enabled in the flow, our system checks for the presence of this parameters and only visitors from the Google Ads advertising network will be redirected to the black page. If you go to the white page domain without Click ID (https://whitepage.com), visitors will stay on the white page.
- In your Google Ads account, the "Auto-tagging" feature must be enabled.
After creating the first campaign, select «Account settings» in the left navigation panel. Open the «Auto-tagging» section. To enable Auto-tagging, check the box for «Mark the URL that people click through from my ad». Click Save.
- Enable the Google Click ID option.
With the Google Click ID option enabled to check the redirect to the black page, you need to access the white page using residential proxies or from your home IP address (temporarily adding your country to the flow) with a special parameter:
/?gclid=Cj0KCQiAmpyRBhC-ARIsABs2EArUH0fVxaDZJyqvuAUjkHhEgQAWmTfENIrJyQ7tJtteDAdfryCV4REaAoXnEALw_wcB
which is added to the white page domain:
https://whitepage.com/?gclid=Cj0KCQiAmpyRBhC-ARIsABs2EArUH0fVxaDZJyqvuAUjkHhEgQAWmTfENIrJyQ7tJtteDAdfryCV4REaAoXnEALw_wcB
This Click ID parameter is only intended to verify the correct flow setup and redirection to the black page when the Google Click ID option is enabled. You don't need to add it to the Google account advertisement. Simply specify the regular white page link without Click ID.
¶ Adding the Black Page Link
Specify the link to the black page in absolute format (with the https:// or http:// protocol. We recommend that you always enable SSL on all your sites, as you may lose traffic due to browser security policies). It can be either a link to your flow in the affiliate program or:
a separate directory on the same domain where the white page is located, for example:
https://whitepage.com/black_page
or on a subdomain of the white page:
https://black.whitepage.com
or a site on a third-party domain:
https://blackpage.com
¶ JS Fingerprinting Option
A mandatory setting for filtering Google Ads and Bing Ads bots.
If you do not activate this option, traffic distribution will be based only on PHP parameters. Please note that PHP cannot provide a sufficient set of data for effective filtering of Google and Bing bots.
¶ Timezone Filtering (recommended)
Timezone filtering is not mandatory, but you can use it if needed.
When selecting, consider that countries often span multiple time zones.
You need to specify all time zones of the countries whose visitors should be allowed to access the black page.
Note: Adding timezone filtering may result in more traffic loss
¶ Browser Timezone Matching to Visitor's Location (recommended)
Enabling this option checks the match between the timezone set in the visitor's operating system settings and their actual location.
¶ Touchscreen Filtering
If the customized flow is intended only for mobile traffic, you can additionally enable touchscreen filtering. On the black page, visitors will be allowed only if their devices have a touchscreen.
¶ Automatic Bot Detection (Matchex® Technology)
Matchex® Technology is a mandatory filter for cloaking Google Ads and Bing Ads, allowing you to identify common features even among the most advanced bots. Parameters deviating from the norm are determined for each visitor, and the filter subsequently seeks them among other visitors. This way, the system self-learns and filters out bots automatically.
¶ Optional Configuration
This configuration block is not mandatory (click to expand)
This functionality allows additional traffic filtering based on:• Internet Service Providers (ISPs);
• Subnets (CIDR);
• Individual IP addresses;
• User-Agent;
It also allows admitting visitors to the black page based on:
• Specific HTTP referrers;
• Specific subnets (CIDR);
When adding parameters, ensure the correct format, as templates are provided within the fields.
Note that adding a whitelist of allowed HTTP referrers may result in significant loss of target traffic.
After configuring all filtering parameters, save the flow, and then proceed with the configuration in the Integration Setup section.
¶ Integration Setup
¶ Integration Types
There are two types of integration supported:
-
PHP Integration
In this type of integration, the connection between the flow in hoax.tech and the white page is made using the PHP fileindex.php, which is downloaded in the flow and uploaded to your server in the white page directory. This is the most commonly used integration method. -
JavaScript Integration
This is used if the white page is hosted on external web services that do not support PHP code processing. For example, on platforms such as Tilda, Shopify, Wix, Blogspot, Github. In this case, the PHP file from the flow is uploaded to any secondary server, and a special script is generated, which is added to the original HTML code of the white page.
In the classic PHP integration with your server for the white page, the default action for the black page is a Redirect 302, which is automatically replaced with JavaScript Redirect when JS Fingerprinting is enabled in the flow.
Therefore, it is recommended to use the default settings:
In JavaScript integration using third-party builder services to host the white page, the default action for the black page is JavaScript Redirect.
It is also recommended to use the default parameters:
¶ Types of Black Page Actions
Depending on the type of filtration enabled in the flow settings and the type of integration, there are seven types of actions with the black page:
All Types of Actions and Their Combinations with Integration Types (click to expand)
-
JavaScript Redirect
The redirection occurs on the browser side, resulting in a slower redirection speed compared to other types.
This is the only possible redirect type when JS Fingerprinting is enabled, which is necessary for filtering advanced Google Ads/Bing Ads bots. -
iframe
This display method, using the<iframe>tag, allows embedding web pages (black page) and other content directly on the white page in a separate window. -
Redirect 301
Permanent redirect. If you activate a 301 redirect, after the first visit to the black page, its URL and content will be cached in the visitor's browser. Upon subsequent visits, the visitor will always be directed to this page, bypassing our system. Even if there are changes in the flow settings and the black page URL, the browser cache needs to be cleared for those changes to take effect. -
Redirect 302
Temporary redirect. When using this method, the browser receives a signal that the new address is temporary, so it does not cache the content. This type of action is set by default for PHP filtration. -
Redirect 303
View other. This type of redirect is similar to the temporary 302 redirect. -
HTML Meta Refresh
Redirection using themeta http-equiv="refresh"construction, which sends a command to the browser to reload the current page after a certain period of time when the user enters it, or to redirect the user to another URL. -
Set Cookie
No redirect action. In case the visitor is identified as a bot, a cookie with the flow hash name in the following format is set using the HTTP Set-Cookie header:58cfe539d816ec78a117474c2a76617f. This method can be applied, for example, to display different content on the site, to issue different files when a button is pressed, etc.
¶ Combining integration types and actions
If incompatible actions such as Redirect 301, 302, 303, or HTML Meta Refresh are selected, they will be automatically replaced with JavaScript Redirect.
Displaying black page in an iframe can be disabled using X-Frame-Options headers. In this case the iframe action will not work.
¶ Installation
¶ Installation for PHP-integration
After selecting the integration type (in this case, PHP) and the action type (you can leave Redirect 302).
- Download the index.php file;
- Go to the hosting panel;
- Rename the launch file of the white page to index2.php (if the launch file is index.html, also rename it to index2.php, changing the extension to .php);
- Upload the previously downloaded index.php file from the flow to the root directory of the site;
It should look something like this (index2.php is the renamed launch file of the white page, and index.php is the file downloaded from the flow);
¶ Installation for JavaScript–integration
After selecting the integration type (in this case, JavaScript) and the action type (you can leave JavaScript Redirect).
- Download the integration file query.php and upload it to any server or shared hosting;
- Specify the link to the integration file in absolute format (⚠️only domains with SSL certificate are supported (protocol https://);
(for example, https://myscriptpage.com/query.php) - Generate code for integration in the website builder;
- Copy the code and paste it on the white page after the
<body>tag;
<!DOCTYPE html>
<html lang="en">
<head>
...
</head>
<body>
▶ paste the copied code here ◀
...
</body>
</html>
¶ Verification of the settings correctness
Verify the correctness of the setup by navigating to the white page from your home IP address, allowed in the flow's country, or using residential proxies.
If you want to test the redirect with an IP VPN/IPv4 proxy, add the IP address to the flow in the "Test IP" field. In this method, all flow settings and browser fingerprints are ignored.
If the Google Click ID option is enabled, to check the redirect to the black page, go to the white page with a special Click ID parameter:
/?gclid=Cj0KCQiAmpyRBhC-ARIsABs2EArUH0fVxaDZJyqvuAUjkHhEgQAWmTfENIrJyQ7tJtteDAdfryCV4REaAoXnEALw_wcB
which is added to the white page domain:
https://whitepage.com/?gclid=Cj0KCQiAmpyRBhC-ARIsABs2EArUH0fVxaDZJyqvuAUjkHhEgQAWmTfENIrJyQ7tJtteDAdfryCV4REaAoXnEALw_wcB
This Click ID parameter is only intended for checking the correctness of the flow setup and the transition to the black page when the Google Click ID option is enabled. Do not add it to the Google Ads campaign; simply specify the link to the white page.
Open the dashboard where the visits should be displayed:
If the test visits are not visible in the Dashboard, the white page is not working, or you encounter errors in the browser, use the Troubleshooting section or contact us via Telegram or Live chat.