> ## Documentation Index > Fetch the complete documentation index at: https://docs.betterumami.com/llms.txt > Use this file to discover all available pages before exploring further. # Configure the Betterumami Tracker Script Attributes > Customise tracking behavior using data attributes on the script tag — restrict domains, disable auto-tracking, collect Core Web Vitals, and more. The Betterumami tracker is configured entirely through `data-*` attributes on the ` ``` The sections below document every available attribute. *** ## Required Your unique Betterumami website ID. Every request the tracker sends is tagged with this value so Betterumami knows which website the data belongs to. You can find this ID in the **Tracking code** section of your website's edit panel. ```html theme={null} ``` *** ## Tracking Behaviour *Available since v2.0.0* Controls whether the tracker initialises at all when the script loads. Set to `false` only when you want to disable every form of automatic data collection — pageviews, click tracking, path change detection, and performance tracking — and send all data yourself using [Tracker functions](/docs/tracker-functions). ```html theme={null} ``` Setting `data-auto-track="false"` disables **all** tracker initialisation, including performance tracking. If you only want to control pageview collection while keeping other features active, use `data-auto-pageview="false"` instead. *Available since v3.2.0* Disables automatic pageview tracking while leaving the rest of the tracker — including performance monitoring and click tracking — fully initialised. Use this when you want to fire pageviews manually via `umami.track()` (for example, in a single-page application with a custom router) while still benefiting from automatic features. ```html theme={null} ``` *Available since v2.0.0* A comma-separated list of hostnames on which the tracker is allowed to run. Each value is matched against `window.location.hostname`. When `data-domains` is set, the tracker silently does nothing on any hostname not in the list — making it safe to deploy the same snippet across production, staging, and local development environments without polluting your production analytics. ```html theme={null} ``` Be precise about whether your production site uses the `www` subdomain. `mywebsite.com` and `www.mywebsite.com` are treated as different hostnames. Add both if your site is accessible at both addresses. *** ## Data Destination *Available since v2.0.0* Overrides the URL that the tracker sends data to. By default, data is sent to the same origin as the script file. Use this attribute to route tracking requests to a different server — for example, a proxy you control, a self-hosted Betterumami instance, or a vanity domain that bypasses common ad-blocker block lists. ```html theme={null} ``` *** ## URL Collection *Available since v2.11.0* Set to `true` to strip query string parameters from every URL before it is recorded. Betterumami will store the path (e.g. `/products`) but not the query string (e.g. `?ref=newsletter&utm_source=email`). Useful when query strings contain sensitive or high-cardinality values you don't want appearing in your dashboard. ```html theme={null} ``` *Available since v2.16.0* Set to `true` to strip the hash fragment from every URL before it is recorded. Pages at `/docs/intro#getting-started` and `/docs/intro#installation` will both be recorded as `/docs/intro`. Helpful when your hash fragments reflect in-page anchor links that you don't want counted as separate pages. ```html theme={null} ``` *** ## Privacy *Available since v2.17.0* Set to `true` to honour the browser's [Do Not Track](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/doNotTrack) setting. When a visitor has DNT enabled and this attribute is set, the tracker will not send any data for that visitor. ```html theme={null} ``` *Available since v2.18.0* The name of a JavaScript function (defined in the global scope) that is called before every tracking request is sent. The function receives two arguments — `type` and `payload` — and must return either a (possibly modified) payload object to allow the send, or a falsy value to cancel it entirely. Use this for last-mile filtering, payload enrichment, or conditional suppression of specific events. ```js title="Define the handler before the script tag" theme={null} function beforeSendHandler(type, payload) { // Cancel sends for admin users if (document.cookie.includes('is_admin=true')) { return false; } return payload; } ``` ```html theme={null} ``` The handler function must be defined in the global scope (`window.beforeSendHandler`) **before** the Betterumami script executes. Define it in a ` ``` If you're sending pageviews manually and have set `data-auto-pageview="false"`, performance tracking still initialises correctly. Avoid using `data-auto-track="false"` in this scenario, as that disables performance tracking too. *Available since v2.11.0* Tags every event sent by this script instance with a named label. Use tags to separate traffic from different experiments, page variants, or deployment cohorts and then filter your dashboard by tag. ```html theme={null} ``` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.