---
title: The Rebilder Tag
description: Count AI-referred visits and supported browser activity on your website with the Rebilder Tag. Connect the script and review reporting coverage.
canonical_url: https://rebilder.com/docs/tag
last_updated: "2026-08-20"
---

# [The Rebilder Tag](https://rebilder.com/docs/tag)

> Count AI-referred visits and supported browser activity on your website with the Rebilder Tag. Connect the script and review reporting coverage.

- **Updated:** 2026-08-20
- **Author:** Rebilder
- **Section:** Concepts
- **Description:** Count AI-referred visits and supported browser activity on your website with the Rebilder Tag. Connect the script and review reporting coverage.
- **Publisher:** Rebilder

## The whole install

The Rebilder Tag is a first-party script you paste into your own site. It is dependency-free, it is served from rebilder.com, and the install is complete when this one line is in your HTML:

Anywhere in your page HTML

```
<script defer src="https://rebilder.com/tag.js" data-rebilder-store="STORE_ID"></script>
```

Replace `STORE_ID` with the store id shown on [Console install](/console/install). The tag works on any platform that lets you add a script tag; there is no build step and no package to keep current.

The tag records browser activity. Add the [gateway](/docs/quickstart) for source-backed serving and server-side request reporting. Both feed the Console.

## What it reports

One beacon per initial pageview, sent with `navigator.sendBeacon` to the endpoint below, and nothing else. The payload is three fields:

| Field | What it carries |
| --- | --- |
| `path` | `location.pathname` only. A query string never leaves the page, and the stored column refuses a value containing `?`. |
| `ref` | The referrer, only when it comes from another origin. A same-origin referrer is dropped at the endpoint and never stored. |
| `wd` | `navigator.webdriver`, verbatim. `true` means an automated browser declared itself; `false` or absent means nothing. |

The server supplies the timestamp from its own clock, because the tag sends none, and classifies the cross-origin referrer into a platform (`chatgpt`, `perplexity` and the rest) with the same classifier the gateway events path uses. A route change in a single-page app does not fire another beacon; the count is initial pageviews.

## What it deliberately does not collect

> **Data excluded from reporting** The tag reports the fields documented below. It excludes form contents and personal identifiers from event payloads.

- **No query strings, ever.** The beacon sends `location.pathname` only, the endpoint strips any query that reaches it anyway, and the database refuses a path that carries one. Search terms, tokens and tracking parameters never reach the table.
- Pageview records exclude IP addresses. The endpoint uses separate, temporary rate-limit records; see the Privacy Policy for processing details.
- **No raw User-Agent.** The endpoint classifies server-side, and only the classification lands.
- **No cookies, no storage, no identifiers, no fingerprinting.** The tag sets nothing and reads nothing beyond the three fields above. Rows are pageviews, not people, so any visitor count derived from them is an estimate and is labelled as one wherever it renders.
- **Honors Do Not Track and Global Privacy Control.** When `navigator.doNotTrack` is `1` or `globalPrivacyControl` is set, the tag sends nothing at all.
- The Rebilder Tag measures activity on the website where you install it. See the Privacy Policy for analytics used on rebilder.com.
- Tag events are sent to `https://api.rebilder.com/v1/client-events`.

## Reporting coverage

The tag sees traffic that executes JavaScript in a browser: human visitors, including the ones AI assistants refer, and browser-driving agents that declare themselves through `navigator.webdriver`. It also gives WordPress-sourced and self-hosted stores the human-pageview denominator their agent numbers were missing.

> **Direct HTTP request coverage** Direct HTTP requests do not execute the tag. Use server-side reporting for those requests and tag data for supported browser activity. The Console keeps these measurements distinct.

Read the two instruments together: the tag carries the human-pageview denominator and the AI-referred half, and the gateway carries agent fetches, the answer rate and the miss log.