To configure filtering on a virtual server or shared hosting, you need:
- VDS/VPS virtual server or shared hosting.
- Domains (for JS integration, you can use domains of site builder platforms like Tilda, Blogspot, Wix and others).
- Safe pages (websites) for bots and moderators (white page).
¶ Virtual Server
Optimal Configuration
Since enabling JS Fingerprinting is mandatory when setting up cloaking for Google Ads/Bing Ads, it is recommended to configure a virtual server with a minimum of 2 processor cores / 2 GB of RAM and an NVME / SSD drive for quick redirection of visitors to the black page. Ideally, a configuration with 4 cores / 4 GB or higher is recommended.
The optimal server location is as close as possible to your target audience. Installation on less powerful servers or shared hosting is possible, but it may lead to higher traffic loss.
Acceptable Configuration
For cloaking on Facebook,TikTok and native networks, enabling the JS Fingerprinting option in flows is not recommended due to the potential loss of a significant portion of traffic. In such cases, installation on shared hosting is possible. However, saving resources may negatively affect the speed of redirecting users to the black page during sudden traffic spikes.
To set up filtering on a virtual server or shared hosting, the following requirements must be met:
We do not recommend hosting white pages on the servers of the following hosting providers: Namecheap, Aeza, AlexHost, Beget, SiteGround
¶ Domains
Any domain registrars are acceptable. Here are some of them:
¶ White Page
A white page is a website that contains no content prohibited by advertising networks. It is scanned by bots and reviewed by advertising network moderators. The script of our service is placed in the root directory of this site.
The white page must have basic HTML5 markup, including the opening <body> and closing </body> tags.
It is recommended to use lightweight and optimized white pages for fast loading, avoiding heavy images, videos, animations, and excessive scripts or tracking tags. This will result in a faster redirection speed to the black page and reduce traffic loss, especially when JS Fingerprinting is enabled.
You can assess the loading speed and file sizes of your white page in the browser:
- For Firefox: Right-click on the page - Inspect - Network - Refresh (F5);
- For Chrome: Right-click on the page - Inspect - Network - Refresh (F5);
Our test white page is located at this domain: https://white.hoax.tech (1 processor core, 1 GB of RAM, NVMe disk).
Access to the black page is possible via a standard browser, residential proxies, or a home IP address.
You can review the recommendations for creating white pages here.