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 data protection”, to a lower one, such as “Medium data protection”, 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

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;
       }
}
 

Once the NGINX configuration is set up, you'll need to update the tracking snippet on your web page. The screenshot above shows what the generated tracking code on the app looks like. 

The marked URL should point to the proxy you have set up. Please choose the scenario that applies to you:

• If you are using your website's domain: The entire URL within the snippet (“//app-worker.visitor-analytics.io/main.js”) should be updated to “/analytics/main.js". The tracking snippet would then look like this:

<!-- TWIPLA Tracking Code for yourwebsitename.com -→<script>(function(v,i,s,a,t){v[t]=v[t]||function(){(v[t].v=v[t].v||[]).push(arguments)};if(!v._visaSettings){v._visaSettings={}}v._visaSettings[a]={v:'1.0',s:a,a:'1',t:t};var b=i.getElementsByTagName('body')[0];var p=i.createElement('script');p.defer=1;p.async=1;p.src=s+'?s='+a;b.appendChild(p)})(window,document,'/analytics.io/main.js','websiteKey','va')</script><!-- TWIPLA Tracking Code for yourwebsitename.com -->

• If you are using a different domain: The entire URL within the snippet (“//app-worker.visitor-analytics.io/main.js”) should be replaced with the domain you used. For example, if you’re using the domain “https://another-domain.com/”, the tracking snippet would look like this:

<!-- TWIPLA Tracking Code for yourwebsitename.com -→<script>(function(v,i,s,a,t){v[t]=v[t]||function(){(v[t].v=v[t].v||[]).push(arguments)};if(!v._visaSettings){v._visaSettings={}}v._visaSettings[a]={v:'1.0',s:a,a:'1',t:t};var b=i.getElementsByTagName('body')[0];var p=i.createElement('script');p.defer=1;p.async=1;p.src=s+'?s='+a;b.appendChild(p)})(window,document,'https://another-domain.com/analytics/main.js','websiteKey','va')</script><!-- TWIPLA Tracking Code for yourwebsitename.com -->

Note: Your websiteKey should remain unchanged.

You can view a live example of the integration here.

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.