LogoLogo
API DocsChangelogPlaybooksLoginBook a Demo
  • Getting Started
    • Introduction to Reo.Dev
    • For Users
      • Step 1: Find active accounts to target
      • Step 2: Track developer activity on your target accounts
      • Step 3: Identify developers engaging with your product
      • Step 4: Build custom segments that are most likely to convert
      • Step 5: Use filters to spot high-intent leads
    • For Admins
      • Step 1: Identify active accounts to target
      • Step 2: Track developer activity on your target accounts
      • Step 3: Find developers engaging with your product
      • Step 4: Create custom segments that are most likely to convert
      • Step 5: Integrating data sources with Reo.Dev
      • Step 6: Integrate Slack and set up notifications
      • Step 7: Add Customer Fit Criteria
  • Accounts
    • Account Lifecycle Stage
    • Custom CRM Stages
    • Developer Funnel Stages
    • Account Activity Score
    • Tags
    • Customizing Tags
    • Custom Lists
    • Using the Lists API in Reo.Dev
    • Managing CRM Owners in Reo.Dev
    • Follow an Account
    • How to Set Up Notification Alerts for Accounts, Developers & Segments in Reo.Dev
    • Flag incorrect data
  • Developers
    • Interpreting Intel on the Developer view page
    • Developer Activity Score
    • How to Find Inbound Developers in Reo.Dev
  • Segments
    • Creating Segments
    • Basic & Advance Segments
    • Filters 101
    • Segment Actions
    • My Segments
    • Shared Segments
    • Magic Segments
    • Favourite Segment
    • Add notes for better collaboration and context
    • CSV Exports for Segments
    • 10 Advanced Segments to create to spot high-intent opportunities
  • Buyers
    • Find Buyer Contact
    • How to Find, Segment & Engage Decision-Makers in Reo.Dev’s Buyer Section
    • Buyer Persona Configuration in Reo.Dev
  • Enrichment
    • Enrichment
  • Audiences
    • Buyer Audience
  • Integrations
    • Connect GitHub repositories
    • Reo.Dev Zapier Integration Guide
    • Webhooks
    • Developer Docs
      • Docusaurus
      • GitBook
    • CRM
      • HubSpot
      • Salesforce
      • Pipedrive
      • Zoho
      • Freshworks
      • Leadsquared
    • Tracking Beacon
      • Install JavaScript for Documentation
      • Install JavaScript for Product
      • Install JavaScript in Website
      • Install JavaScript in Local Product
      • Track Code Interactions
      • Install JavaScript for Documentation through Google Tag Manager
      • Reo.Dev JavaScript Cookies and Consent Guide
    • Product Usage API
      • Overview
      • How to Configure Product Usage Metrics in Settings
      • Telemetry Data
      • Product API
      • Examples of Product Usage Metrics
      • Data Collected for Product Usage
    • Communities
      • Open Communities
      • Owned Communities
        • Slack
        • LinkedIn Company Page
    • Email
      • Apollo.io
      • How to Integrate and Use Outreach.io with Reo.Dev
      • How to Integrate and Use Salesloft with Reo.Dev
    • Website Tracking
      • RB2B
  • Analytics
    • Impact Dashboard
  • Campaigns
    • Run bulk email campaigns
    • Testing Your Email Integration with Reo.Dev
  • Settings
    • Add Customer Fit Score Criteria
    • Add Firmographic and Technographic Filters
    • Configure Slack & Email Notifications
  • Account and Contact Usage Limit
    • Manage Account and Contact Limit Usage
  • User Management
    • Invite a teammate to Reo.Dev
    • Manage CRM Permissions
    • Roles and Permissions: Admin vs User
    • What Happens to Data When a User Is Deleted in Reo.Dev?
  • FAQs/Troubleshooting
    • How to Exclude Competitors from My Segments in Reo.Dev?
    • How to Sync a Segment to Salesforce/HubSpot?
    • Why Is the 'Sync to CRM' Button Greyed Out?
    • I Synced My Accounts, But They Are Not Showing in My CRM – What to Do?
    • Why Am I Seeing More Accounts in CRM Than I Synced?
    • Why Can't I Find My Account in the Dashboard Search Bar?
    • Resolving Caching Issues in Reo.Dev
    • Understanding Score Discrepancies Between Account and Developer Activity Score
    • Reo.Dev Credit-Based Pricing: FAQs
Powered by GitBook
On this page
  • Configure the Base URL in Reo.Dev UI (Required for Tracking to Work)
  • For Documentation Tracking via GTM
  • FAQs

Was this helpful?

  1. Integrations
  2. Tracking Beacon

Install JavaScript for Documentation through Google Tag Manager

PreviousTrack Code InteractionsNextReo.Dev JavaScript Cookies and Consent Guide

Last updated 12 days ago

Was this helpful?

LogoLogo

Resources

  • Changelog
  • Playbooks
  • DevGTM Conversations
  • Support
  • API Docs

Company

  • Blog
  • Contact Us
  • Book a Demo

Policies

  • Privacy Policy
  • Terms of Service

© 2025 All rights reserved Reo.Dev

You can install the Reo.Dev JavaScript tracking script in your documentation using Google Tag Manager (GTM).

Before adding the script to GTM, you must configure your Base URL in the Reo.Dev UI.


Configure the Base URL in Reo.Dev UI (Required for Tracking to Work)

To ensure tracking applies to the correct documentation pages, you must first configure the Base URL in your Reo.Dev dashboard.

What is the Base URL?

The Base URL is the root domain where your tracked documentation pages exist. For example:

  • If your documentation is hosted at https://docs.example.com, set docs.example.com as your Base URL.

  • If you track multiple subdomains, configure each accordingly in Reo.Dev.

How to Set the Base URL?
  • Log in to your Reo.Dev dashboard.

  • Navigate to Tracking Setup → Website Tracking.

  • Enter your Base URL in the Website URL field (e.g., docs.example.com).

  • Choose between:

    • Enrich Entire Website → Tracks all pages under this domain.

    • Enrich Specific Pages → Tracks only selected pages.

For Documentation Tracking via GTM

  1. Go to the Documentation tab.

  2. In the Documentation URL field, enter the Base URL of your documentation site (e.g., docs.example.com).

  3. Click + Add Documentation URL if you have multiple subdomains for docs (e.g., help.example.com, developer.example.com).

Once the Base URL is set up, you can proceed with adding the tracking script in GTM.


Step 1: Login to you google tag manager https://tagmanager.google.com/

Select Appropriate accounts which is link to the docs.

Step 2: Click on Tags menu and move the the tags page.

You may have different tags already exist , You can click on “New” for creating a new tag for script.

Step 3: On clicking on New, you will have screen for defining a new tag . You can give a name to this tag.

Step 4: Click on “Choose a tag type…”

Step 5: Select the tag type as Custom HTML.

Step 6: In HTML section, paste the code for script : (make sure to update you clientID in place of “myreo786”)


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

Step 7: After that, choose a trigger for the script to load. After choosing trigger (Initialization -All pages) , click on button.

Step 8: After adding trigger, you can save the tag by clicking on Save button.

Step 9: On saving the tag , you will land on tags page. Then click on Submit button to proceed for publishing your changes.

Step 10: Then click on Publish button to proceed for publishing your changes.(you can fill other details as well which appears while publishing changes).

Step 11: You can continue.

Step 12: Once you see below screen , which means your changes are published.

After publishing GTM changes , go to you docs for which you have made changes in GTM.

You will find below scripts in inspect element of the docs: (with your clientID)

<script type="text/javascript" id="">!function(){var a;var 
b="myreo786";var c=function(){Reo.init({clientID:"myreo786"}
)};(a=document.createElement("script")).src="https://static.
reo.dev/"+b+"/reo.js";a.async=!0;a.onload=c;document.head.
appendChild(a)}();</script>
<script src="https://static.reo.dev/myreo786/reo.js
" async=""></script>

Cookie Management and Compliance

To learn more about Reo.Dev's cookie usage, categorization, and best practices for implementation, refer to this guide.


FAQs

Does the JavaScript code introduce any vulnerabilities or risks to the website?

The JavaScript code has been tested thoroughly to ensure that it does not introduce any vulnerabilities or risks to the website. Data sent by the JavaScript code is encrypted using the HTTPS protocol to ensure secure transmission and prevent unauthorized access.

Does the JavaScript code use external dependencies or third-party libraries?

The JavaScript code uses secure third-party libraries that have been thoroughly checked for vulnerabilities and risks.

How does JavaScript handle user privacy? Is there a potential risk of collecting personally identifiable information (PII) without proper consent?

It is designed to collect anonymous data such as browser information, page views, copy and click events without collecting any non-consented PII.

What impact will including this JavaScript have on the page load times of my app?

The code has been optimized to minimize any negative impact on page load time and performance. This code uses asynchronous loading technology so it can load independently without blocking the rendering of the screen content.

Has the JavaScript been tested on different browsers and devices to ensure cross-platform compatibility and consistent behavior?

The JavaScript code is thoroughly tested on multiple browsers (Chrome, Firefox, Safari, Edge, Brave) and devices (desktop, mobile) to ensure compatibility and consistent behavior.

Will the inclusion of this JavaScript affect the overall user experience of the product, for example, slow down UI interactions or cause unexpected behavior?

It doesn't affect the overall user experience. It will not slow down, or introduce any intrusive elements that have an impact on the experience.

Are there any fail-safe mechanisms in place to prevent scripts from disrupting critical functionality in the event of an error?

We have implemented fail-safe mechanisms in the javascript to prevent scripts from interrupting the website's critical functionality in the event of an error, thus ensuring a smooth user experience.

Will the JavaScript code continue to perform optimally as the app traffic and user base increase over time?

The code is optimized for scalability. The JavaScript code is designed to scale as your online traffic and user base grow. It will continue to work best even as traffic to your site increases. There are no significant limitations or performance bottlenecks associated with the tracking mechanism.

Is your JavaScript compliant with relevant industry standards and best practices such as GDPR and CCPA for data protection and user consent?

The JavaScript code adheres to relevant industry standards and best practices, such as GDPR and CCPA, regarding data privacy and user consent.