Skip to main content
Every website you want to track with bchic Analytics must first be connected to your organization. Once linked, you’ll receive an individual tracking script for each domain.

Connect a website

Navigate to Settings → Organization and expand the Linked Website URLs section. You’ll see all currently connected domains along with an input field to add new ones. Enter the full URL of your website (e.g. https://my-website.com) and click the + icon to save it.
You can link as many websites as you like to a single organization. Each domain gets its own tracking script with a unique website ID.

Install the tracking script

Once a website is linked, you can retrieve its script. Click the code icon next to the desired domain in the list. A pop-up will open with a personalized installation guide. First, select your website platform — supported options include WordPress, Webflow, Shopify, Squarespace, Wix, Framer, and a generic HTML option. You’ll then be walked through how to embed the script on your platform. The script itself looks something like this:
<script defer src="https://analytics.bchic.de/script.js" data-website-id="YOUR-WEBSITE-ID"></script>
Copy the script and paste it into the <head> section of your website as instructed.

Proxy the script through your own domain

If your Content Security Policy (CSP) only allows scripts and requests from your own domain, you can proxy both the tracking script and the event API through your web server. Your website then loads bchic from your own origin:
<script defer src="/js/analytics.js" data-website-id="YOUR-WEBSITE-ID"></script>
For nginx, add locations like these to the server block of the domain where your website runs:
location = /js/analytics.js {
    proxy_pass https://analytics.bchic.de/script.js;
    proxy_set_header Host analytics.bchic.de;
    proxy_ssl_server_name on;
    proxy_ssl_protocols TLSv1.2 TLSv1.3;
    proxy_buffering on;
}

location = /js/api/send {
    proxy_pass https://analytics.bchic.de/api/send;
    proxy_set_header Host analytics.bchic.de;
    proxy_ssl_server_name on;
    proxy_ssl_protocols TLSv1.2 TLSv1.3;
    proxy_buffering on;
    proxy_http_version 1.1;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
}
After changing nginx, reload the server and make sure your CSP allows script-src 'self' and connect-src 'self'.
For detailed step-by-step guides for each platform, check out our Integrations section. We recommend following the instructions there, as they account for platform-specific nuances.

Verify tracking

After installation, you can check whether tracking is active on your website’s Overview page. As soon as the first pageview is registered, data will appear in your dashboard. If no data shows up after a few minutes, make sure that:
  • the script is placed in the <head> section of your page — not in the <body>.
  • the website ID in the script is correct and matches the linked domain.
  • no ad blocker is preventing tracking in your browser (try disabling it temporarily to test).