> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/integrations/input-sources/developer-insights/website.md).

# Website

### Overview

**Most visitors to your website never fill out a form.** They check your pricing, read a case study, browse your integrations page, **then leave without a trace**. That's the **majority of your funnel happening completely out of view.**

Connecting your website to Reo.dev closes that gap. 

Once installed, Reo.dev identifies the developers, buyers, and accounts behind your website traffic, including the ones who never convert on a form. That activity flows into their account and developer profiles, segments, and alerts. 

**GTM teams get a live view of who's visiting, what they're looking at, and how close they are to a buying decision.**

The setup has 4 steps: 

{% stepper %}
{% step %}

### [Add the URLs you want to track](#step-1-add-your-website-urls)

{% endstep %}

{% step %}

### [Mark high-intent pages for separate tracking (optional)](#step-2-configure-key-pages-optional)

{% endstep %}

{% step %}

### [Get your client ID and tracking snippet](#step-3-get-your-client-id-and-tracking-snippet)

{% endstep %}

{% step %}

### [Choose an installation method](#step-4-choose-the-installation-method)

*Based on how your website is built*
{% endstep %}
{% endstepper %}

***

### Step 1: Add your website URLs

1. From the left menu, navigate to **Settings → Integrations.** 

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2F4CjXxPkE5KlRNDLGKiFK%2FScreenshot%202026-09-09%20at%209.44.33%E2%80%AFAM.png?alt=media&amp;token=000a9cd2-d1c4-4b51-8ce5-ed418bcb9689" alt=""><figcaption></figcaption></figure>

2. Click **Configure** on the **Website** card.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FVfhL9JPQesvMZeluj7NL%2FScreenshot%202026-09-09%20at%2011.44.52%E2%80%AFAM.png?alt=media&amp;token=db2cf746-4704-470a-9c52-b652c8db0458" alt=""><figcaption></figcaption></figure>

3. Enter your base URL. Click **Add New** to track more than one, for example a separate subdomain.
4. Give each URL a clear **Page Name**. You'll use it later to filter and segment your data.

{% hint style="info" %}
**What's a Base URL?**\
\
The main domain under which all your tracked pages exist. For example:

* To track your whole site at <mark style="color:red;">`https://www.reo.dev`</mark><mark style="color:red;">,</mark> set the Base URL to <mark style="color:red;">`reo.dev`</mark>
* To track only a subdomain, like <mark style="color:red;">`agents.reo.dev`</mark>, set the Base URL to <mark style="color:red;">`agents.reo.dev`</mark>
  {% endhint %}

5. **Choose how much of your website to track:** When you add a Base URL, choose one of two tracking scopes:
   1. **Enrich entire website**: Track every page under this Base URL
   2. **Enrich specific pages**: Track only the URLs you add as Key Pages in Step 2. Every other page on the site stays untracked. If you only care about specific high-intent pages, like pricing or case studies, choose Enrich specific pages so you're not tracking the rest of the site too.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2F7cXygLLndrHPOUMzGXlC%2FScreenshot%202026-09-09%20at%2012.07.24%E2%80%AFPM.png?alt=media&amp;token=da614a33-7e5b-4abe-a0ce-62834a681b55" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Tip:** Use these pages to build a segment of developers, buyers, or accounts interacting with your website. The Page Name you set here becomes a filter, under Key Website Pages, when you create that segment.
{% endhint %}

***

### Step 2: Configure key pages (optional)

Adding your high-intent website pages lets you track activity on them separately. A few examples of what to add:

* **Case study pages**: a visitor reading these is likely evaluating your solution against real customer outcomes
* **Pricing page**: one of the strongest indicators of purchase intent
* **Integration or solution pages**: show a visitor is exploring how your tool fits into their workflow
* **Landing pages with UTM parameters**: reveal which marketing campaigns are actually driving engagement

To add a key page:

1. Click **+ Add New** to add a row.
2. Enter the URL, exactly as it appears in your browser's address bar.
3. Assign it a unique Page Name.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2Fvzf5AwPIehGoWZzb7ttG%2FScreenshot%202026-09-09%20at%2012.10.14%E2%80%AFPM.png?alt=media&amp;token=5a3e7cde-0d44-4d73-952c-92909557b08d" alt=""><figcaption></figcaption></figure>

#### **Tracking dynamic URLs using wildcards**

If your URLs include dynamic segments, like a project ID or org name, track every variation as one Key Page. Use <mark style="color:red;">`*`</mark> as a wildcard for the dynamic part.

For example, to track the journeys page across every project, set the URL to <mark style="color:red;">`/project/*/journeys`</mark>. Reo captures every URL that matches this pattern, no matter what replaces the <mark style="color:red;">`*`</mark>.

Wildcards can appear mid-URL too, like <mark style="color:red;">`abc.com/id/*/orgpage`</mark>. Skip trailing wildcards, like <mark style="color:red;">`abc.com/page/*`</mark>, since Reo already captures everything after the last <mark style="color:red;">`/`</mark>.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2Fi5oUpQYQPJJEdCvY79V2%2FScreenshot%202026-09-09%20at%2012.10.32%E2%80%AFPM.png?alt=media&amp;token=643e0ce1-17ef-4f2c-a62a-b04ba59740f8" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Note:** The Page Name for a Key Page also appears under the **Key Website Pages** filter when you build a segment.
{% endhint %}

***

### Step 3: Get your client ID and tracking snippet

Every method below needs these two things. Get them once, then pick your method.

#### **What's a Client ID, and where do I find it?**

* Your Client ID is a unique key that connects this snippet to your Reo.dev account. Without it, Reo.dev has no way to tell which account the tracking data belongs to.
* The same ID works across every tracking type (Documentation, Website, Product, Forms), so reuse it if you've already copied it elsewhere.
* You can find your client ID on top of the Website page within the Reo product. Copy the client ID.&#x20;

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FZDz9Ob4A7KXagYfS7mTV%2FScreenshot%202026-09-09%20at%2010.34.39%E2%80%AFAM.png?alt=media&amp;token=a69228fe-2fe8-4fb1-9784-a64b4cd9c6f4" alt=""><figcaption></figcaption></figure>

#### Copy the tracking code

* On the same page, under Step 3 (Install Tracking Pixel), you will find the tracking code.
* Copy the tracking snippet below, and replace <mark style="color:green;">`xxxxxxxxxx`</mark> with your Client ID.

```javascript
<!-- Start of Reo Javascript -->
<script type="text/javascript">  
	!function(){var e,t,n;e="xxxxxxxxxx",t=function()
{Reo.init({clientID:"xxxxxxxxxx"})},
(n=document.createElement("script")).src="https://static.reo.dev/"+e+"/reo.js",n.defer=!0,n.onload=t,document.head.appendChild(n)}();
</script>
<!-- End of Reo Javascript -->
```

***

### Step 4: Choose the installation method

Once you have your client ID and the tracking code, all you have to do is install the tracking snippet using the method that matches how your website is built.

**Choose from the following methods:**&#x20;

{% columns %}
{% column %}
**If you can edit your site's HTML directly**

[Refer to Method 1](#method-1-paste-the-snippet) to paste the tracking snippet inside the header
{% endcolumn %}

{% column %}
**If you are using Google Tag Manager for your site**\
\
[Refer to Method 2](#method-2-google-tag-manager) and install using Google Tag Manager (GTM)
{% endcolumn %}

{% column %}
**If your site is built on npm-based JavaScript project**\
\
[Refer to Method 3](#method-3-npm-package) and install using NPM package
{% endcolumn %}
{% endcolumns %}

Still not sure? Ask whoever manages your website's code.

***

### **Method 1: Paste the snippet**

Paste the snippet you copied above inside the <mark style="color:red;">`<header>`</mark> tag of your website. This is usually in the site's main template or layout file, the one that loads on every page (for example <mark style="color:red;">`header.html`</mark>, <mark style="color:red;">`_document.tsx`</mark>, or your theme's base layout).&#x20;

If you're not sure where that is, ask whoever manages your site's code, or use one of the other methods below.

***

### **Method 2: Google Tag Manager**

Add the snippet above as a custom HTML tag in Google Tag Manager. See the [Google Tag Manager guide](https://docs.reo.dev/install-javascript-for-website-documentation-through-google-tag-manager) for setup steps.

***

### **Method 3: NPM package**

Install the Reo.dev NPM package if your website is built with npm. See the [NPM package guide](https://docs.reo.dev/install-javascript-using-npm-package) for setup steps.

***

### Troubleshooting

#### **Verify the snippet is installed**

The fastest way: on the Website configuration page (**Settings → Integrations → Website → Configure**), click **Check status** in the top-right corner. It tells you whether Reo.dev is receiving data from your site.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2F1SFKqnjpAAblMWojh318%2FScreenshot%202026-09-09%20at%2012.16.39%E2%80%AFPM.png?alt=media&amp;token=b96f6e67-491b-43e1-b486-79c67331d6c4" alt=""><figcaption></figcaption></figure>

To check manually instead:

1. Open your website
2. Right-click anywhere on the page and select **Inspect** to open developer tools
3. In the **Network tab**, search for <mark style="color:red;">`reo`</mark> and check if the network calls are being registered (status code: 200)

***

### Error scenarios

#### **1. The script doesn't load**

The tracking snippet only runs after it downloads successfully from the Reo.dev CDN. A failed download doesn't break your page, it just means that visit isn't tracked. It also won't throw visible errors in the browser console, since the script runs inside a try-catch block with logging disabled. No action is needed. Use the verification steps above if you want to confirm the snippet is live.

#### **2. Reo tokens are deleted**

If all Reo tokens are deleted, the most recent event may fail to send. Tracking recovers on its own, and subsequent calls work normally. No action is needed.

#### **3. Avoid duplicate installs**

Don't install the tracking snippet more than once on the same page. Multiple copies can conflict with each other.

Still stuck? Contact your Customer Success Manager on Slack, or email [**support@reo.dev**](mailto:support@reo.dev).

***

### CSP requirements

If your site enforces a Content Security Policy (CSP), allow these domains. This is usually set in your site's HTTP response headers or a CSP meta tag, ask whoever manages your hosting if you're not sure where.

* <mark style="color:red;">`script-src <https://static.reo.dev>`</mark>
* <mark style="color:red;">`connect-src <https://api.reo.dev>`</mark>

For cookies and data handling, see the [cookie management guide](https://docs.reo.dev/integrations/tracking-beacon/reo.dev-javascript-cookies-and-consent-guide).

***

### FAQs

* **Is the tracking script safe to install?**\
  Yes, it's been tested to rule out vulnerabilities or risks, and all data is transmitted over HTTPS.<br>
* **Does it use external dependencies?**\
  Yes, a small number of third-party libraries. These are checked for vulnerabilities.<br>
* **Does it collect personal information (PII)?**\
  No, it collects anonymous data only, such as browser information, page views, and click events, and never collects non-consented PII.<br>
* **Will it slow down my page?**\
  No, it loads asynchronously, so it doesn't block your page from rendering, and it's built to have minimal impact on load time.<br>
* **Which browsers and devices does it support?**\
  Chrome, Firefox, Safari, Edge, and Brave, on both desktop and mobile.<br>
* **Will visitors notice any change to the site?**\
  No, it runs in the background and doesn't add any visible or intrusive elements.<br>
* **What happens if the script hits an error?**\
  It fails safely. Built-in safeguards stop it from interrupting your site's core functionality.<br>
* **Does it hold up under high traffic?**\
  Yes, it's built to keep performing as your site's traffic grows.<br>
* **Do I need a cookie consent banner?**\
  It's not strictly required, but strongly recommended for GDPR and CCPA compliance. Categorize Reo's tracking as a Performance or Marketing cookie in your consent tool, and load the snippet only after a visitor accepts, not before. See the [cookie management guide](https://docs.reo.dev/reo.dev-javascript-cookies-and-consent-guide) for the full setup.<br>
* **How do I remove the tracking snippet?**\
  Reverse whichever method you used to install it: delete the script tag from your site, or delete or pause the tag in Google Tag Manager, or remove the npm package. You can also remove individual tracked URLs from the Reo.dev UI at any time.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.reo.dev/integrations/input-sources/developer-insights/website.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.