How to Install the Tracking Code

Loading this tracking code is recommended if you operate your website in “Maximum Privacy” mode without a cookie banner or generally for all visitors who accept your cookie banner in one of our data protection modes.

We recommend loading this tracking code for visitors who reject your website's cookie banner, or if your website is not in “Maximum Privacy” mode and you are aiming for fully compliant data collection.

Important Notes:

• You should never load both tracking codes for the same visitor at the same time.
• You do not need to change or reinstall the tracking code snippet if you adjust the data protection level of your website. This applies regardless of whether you switch from a higher data protection level, such as “Maximum Privacy”, to a lower one, such as “Medium Privacy”, or vice versa.
• Changing from “Maximum Privacy” mode to a lower level requires the addition of a website cookie banner, as visitor consent is now required for data collection

When setting up a custom domain for your website's tracking snippet, there are 3 options available.

1. Use the same domain as your website (best practice)
2. Use a sub-domain of your website
3. Use a completely different domain than your website (default setting provided by platform)

A more detailed overview of the options mentioned can be found in the following table:

In order to have access to all your visitors/traffic and be able to provide the best security for your website’s visitors, we recommend using the same domain in your tracking snippet as your website and configuring a proxy (via NGINX) to forward all requests as shown here.

The second best option is to use a sub-domain of your website within the tracking snippet and configure a CNAME DNS entry by following the instructions shown in the dashboard after setting up the custom domain.

 

To bypass ad blockers, a proxy can be set up on the domain serving the website. This allows all data to be sent from the browser via the same domain, for example to prevent or significantly reduce the blocking of the domain by ad blockers.

To get this working, you'll need to make the following changes:

1. Update your NGINX configuration to correctly forward all requests.
2. Update the TWIPLA snippet to work in Proxy Mode.

Important Note: This approach only works technically when using our standalone solution (it is not possible with TWIPLA plugins).

The following needs to be added to the nginx config:

server {
   [...]
   #TWIPLA
   location ~ ^/analytics {
         proxy_pass       proxy.twipla.com;
         proxy_http_version 1.1;
         proxy_set_header Upgrade $http_upgrade;
         proxy_set_header Connection "upgrade";

         proxy_read_timeout 1h;
         proxy_ssl_name "proxy.twipla.com";
         proxy_ssl_server_name on;
         proxy_ssl_protocols  TLSv1 TLSv1.1 TLSv1.2;
         proxy_ssl_session_reuse on;
         proxy_buffering on;

         proxy_cache_revalidate on;
         proxy_pass_header Set-Cookie;

         proxy_set_header X-Real-IP $remote_addr;
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
         add_header X-Cache-Status $upstream_cache_status;

         add_header       X-Served-By $host;
         proxy_set_header Host "proxy.twipla.com";
         proxy_set_header X-Forwarded-Scheme $scheme;
         proxy_set_header X-Forwarded-Proto  $scheme;
         proxy_set_header X-Forwarded-For    $remote_addr;
         proxy_set_header X-Real-IP          $remote_addr;

         gzip on;
         gzip_vary on;
         gzip_proxied any;
         gzip_comp_level 6;
         gzip_types text/plain text/css text/xml application/json application/javascript application/xml+rss application/atom+xml image/svg+xml;
       }
}
 

After setting up your NGINX configuration, the next step is to update the tracking snippet on your website. 

For example, your website domain is your-website-domain.com/analytics. If you're using the same domain, the entire URL within the snippet ('//app-worker.visitor-analytics.io/main.js') should be changed to ‘/analytics/main.js’.

Note: Your websiteKey should remain unchanged.

You can view a live example of the integration here.

If you are using a subdomain of your website or a different domain than default, the tracking URL within the snippet ('//app-worker.visitor-analytics.io/main.js') should be replaced with the domain you used. 

For example, you're using the subdomain, analytics.your-website-domain.com, the URL should be changed to ‘analytics.your-website-domain.com/analytics/main.js’.

Our analytics tools are compatible with all website builder platforms. Before manually integrating the tracking code, check whether an installation guide is listed further down this page. But if you are either unable to find your platform or are running a standalone website, follow the installation steps below to manually add the tracking code to your webpages:

If you're using one of the following platforms, we recommend referring to the linked installation guide for step-by-step instructions:

For users implementing Google Tag Manager (GTM), comprehensive installation instructions can be found in our dedicated guide.