Yes, you can. By default, landing page files are stored on the server in the folder /var/lib/docker/volumes/binom_landers_data/_data/. We do not recommend connecting to the server as root to work with landing pages. Our support team can create a separate user for you to work with landing pages via SFTP upon request.

Yes, you can. To do this, create a folder named "custom-index" in the "Files" section and upload the necessary files to it.

The folder on the server - /var/lib/docker/volumes/binom_landers_data/_data/custom-index.

We cannot guarantee stable tracker work in case you temper with the server. All the changes that are made on your server by someone other than Binom team are made at your own risk.

The load is calculated based on the amount of cores that your server has and the Load Average parameter. Example: Your server has 4 cores. 100% load is Load Average: 4. If the current load is Load Average: 2, the tracker will show a Load of 50% on the Monitor tab.

Some traffic sources (e.g. Adsterra) use symbol "#" as a part of their tokens. Due to how this symbol is processed by the borwsers using the Chromium engine and due to how our web-server processes this symbol in particular, in case the traffic source fails to swap their token for the real value and the symbol "#" is a part of the campaign url, the other tokens, following the "#" symbol in the Campaign Link, will not be recorded by the tracker because the symbol "#" will be treated as the "Named Anchor" or "Anchor Identifier" (details on anchors), and not as a "param=value" pair.

Same can be true for the lander and offer links. Everything following the "#" symbol in the lander of offer link can be lost.

Also in Chromium-based browsers it can so happen, that if you have tokens with "#" symbols in your campaign link and a Direct landing, those tokens will be forwarded to the offer URL.

We recommend that you don't use Zabbix as a monitoring service for your server because it disrupts some processes of the tracker and interact with the MYSQL database.

As an alternative that we can recommend is a duo of Node Exporter + Prometheus.

By default, the tracker will show the real IP of the traffic in case the proxying via CloudFlare is on for the domain without any additional settings.

However, the traffic that goes throug WARP is hidden by Cloudflare and the IP address is not forwarded. Thus the IP address\ISP would always be of Cloudflare.