TWIPLA for HTML Websites

If you are new to TWIPLA, follow these steps to get started:

Sign in to your account here and open the dropdown menu in the top-left corner. Select Add new website to get started.

If your website builder only allows tracking code installation in the header and you encounter issues, it is likely because the script is executing before the Document Object Model (DOM) is fully loaded. This often triggers the error: "Uncaught TypeError: b is undefined." 

To resolve this, you can keep the script in the header but wrap it in an event listener to ensure it only runs after the DOM is ready.

Here's a code snippet that accomplishes this:

<script> document.addEventListener("DOMContentLoaded", function () { (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, '//app-worker.visitor-analytics.io/main.js', 'INSERT-HERE-YOUR-WEBSITE-ID', 'va'); }); </script>

Note: Be sure to replace 'INSERT-HERE-YOUR-WEBSITE-ID' with your specific website ID.

While this modification works for header installations, placing the code at the end of the </body> tag remains the best practice for most sites to ensure a smooth integration.

The tracking code is a lightweight JavaScript snippet that enables our platform to collect and analyze your website data. This code is unique to each website added to your account and serves as the bridge between your site and your analytics dashboard. 

You will receive your unique tracking code during the initial onboarding process or whenever you add a new site. While the installation process may vary depending on whether you use a standalone website or a building platform (like Wix), the core functionality remains the same.

To comply with data privacy regulations while improving data collection, we have updated our tracking code approach. You now have access to two different tracking codes that are generated for your chosen website. You can select between NO Visitor Consent Needed for Tracking and Visitor Consent Needed for Tracking (Platform NOT SET to Max Privacy Mode).

You can read more about how the tracking code works in our article: Tracking Code.

Standard analytics often miss significant traffic becaue they depend on cookies, user consent, and unblocked scripts. If any of these factors fail, the visit is never recorded.

TWIPLA restores this data by combining cookieless tracking with custom domain scripts. By loading the script from your own domain, you bypass third party ad blockers and capture first party data that matches your server totals. This ensures a complete and accurate picture of your real traffic.

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.

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.

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’.

To set up a Custom Tracking Domain (via a CNAME DNS entry), follow these steps:

1. Navigate to the Customize Domain in Snippet to Avoid Traffic Loss section.
2. Enter the custom domain for the tracking snippet and click Save Changes. For this example, we're using the subdomain, analytics.your-website-domain.com.

3. The Confirm Snippet Domain Change modal will appear with the required DNS details. To verify your newly added custom domain, you need to add the CNAME record (details below) displayed on the modal with your domain registrar or DNS provider:

   Type: CNAME

   Hostname: @

   Value: geo.hostedby.net.

4. Once the DNS record is correctly configured, the platform will automatically verify the setup and prepare everything needed. This process may take anywhere from a few minutes up to 24 hours — click Verify DNS to continue.

After completion, the platform will start tracking on the custom domain. 

Now that your tracking code is live, it’s time to dive into your data! We’ve put together some guides below to help you get the most out of every feature:

• What Are Heatmaps? The Only Guide You Need
• What Are Session Recordings and How to Get the Most Out of Them
• What Are Conversion Funnels? A Guide for Digital Marketers
• The Complete Guide to Getting the Fundamentals of Your Website Right
• How to Use Website Surveys and Polls to Boost Your Digital Marketing Activities

Please see our detailed Standalone App FAQs here.

If you encounter any issues during installation, you can reach us through:

• Email: Send us a message at support@twipla.com.
• Chat Bubble: Use the chat bubble available on our website.
• In-App Support: Access support directly within the platform.

For additional details, please visit our Contact Us page. We are committed to ensuring a smooth and seamless experience with our plugin!