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:
Choose an installation method
Based on how your website is built
Step 1: Add your website URLs
From the left menu, navigate to Settings → Integrations.
Click Configure on the Website card.
Enter your base URL. Click Add New to track more than one, for example a separate subdomain.
Give each URL a clear Page Name. You'll use it later to filter and segment your data.
Choose how much of your website to track: When you add a Base URL, choose one of two tracking scopes:
Enrich entire website: Track every page under this Base URL
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.
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:
Click + Add New to add a row.
Enter the URL, exactly as it appears in your browser's address bar.
Assign it a unique Page Name.
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 * as a wildcard for the dynamic part.
For example, to track the journeys page across every project, set the URL to /project/*/journeys. Reo captures every URL that matches this pattern, no matter what replaces the *.
Wildcards can appear mid-URL too, like abc.com/id/*/orgpage. Skip trailing wildcards, like abc.com/page/*, since Reo already captures everything after the last /.
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.
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
xxxxxxxxxxwith your Client ID.
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:
If you can edit your site's HTML directly
Refer to Method 1 to paste the tracking snippet inside the header
If you are using Google Tag Manager for your site Refer to Method 2 and install using Google Tag Manager (GTM)
If your site is built on npm-based JavaScript project Refer to Method 3 and install using NPM package
Still not sure? Ask whoever manages your website's code.
Method 1: Paste the snippet
Paste the snippet you copied above inside the <header> 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 header.html, _document.tsx, or your theme's base layout).
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 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 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.
To check manually instead:
Open your website
Right-click anywhere on the page and select Inspect to open developer tools
In the Network tab, search for
reoand 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.
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.
script-src <https://static.reo.dev>connect-src <https://api.reo.dev>
For cookies and data handling, see the cookie management 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.
Does it use external dependencies? Yes, a small number of third-party libraries. These are checked for vulnerabilities.
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.
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.
Which browsers and devices does it support? Chrome, Firefox, Safari, Edge, and Brave, on both desktop and mobile.
Will visitors notice any change to the site? No, it runs in the background and doesn't add any visible or intrusive elements.
What happens if the script hits an error? It fails safely. Built-in safeguards stop it from interrupting your site's core functionality.
Does it hold up under high traffic? Yes, it's built to keep performing as your site's traffic grows.
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 for the full setup.
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.
Last updated
Was this helpful?