Install Javascript for Forms Tracking

Reo.Dev’s JavaScript beacon works consistently across all your assets — website, documentation, and product. If the JS is already installed on any of these properties, you don’t need to re-install it to track form activity.

However, if you're using separate platforms for landing pages or lead capture (e.g., HubSpot, Unbounce), you’ll need to manually add the JS snippet to those assets to track form opt-ins effectively.

Installation Methods

You can install JavaScript to track the user activity on the documentation webpages in two ways.

Using CDN

To install JavaScript code using our CDN, follow the instructions below:

1. Get the JavaScript Snippet:

Copy the JavaScript code snippet from Reo.Dev Dashboard. Go to Integrations >> Tracking Beacon >> Documentations >>Method 1: Using CDN

https://web.reo.dev/dashboard/integration/documentation

2. Integrate the JavaScript into Your Web Project:

Go to the root index.html page of documentation web pages

3. Locate the <head> Tag:

For optimal performance, it’s recommended to place the script within the <head> tags of your HTML document. This ensures it's loaded early in the page's lifecycle.

4. Insert the JavaScript Snippet:

Insert the JavaScript snippet provided within the <head> section of your HTML file.

5. Save and Deploy:

Save the changes to your HTML file and deploy it to your server.

6. Verification:

Go to any screen after login and right-click anywhere
In the dropdown menu, select Inspect.

In the elements tab, Use the Ctrl + F or Cmd + F and search for “reo”

If the tracking code appears, verify that the code matches

As an NPM Package

To install JavaScript code as an NPM package, follow the instructions below:

Install the Package: Open your terminal or command prompt.

npm i reodotdev
# or
yarn add reodotdev

Integrate the Package into Your Project: Within your project, identify the file or module where you want to incorporate the user activity tracking.
Use with NPM: Import the required function from the installed package and set up the script to load the Reo tracking.

Copy the JavaScript code snippet from Reo.Dev Dashboard. Go to Integrations >> Tracking Beacon >> Documentation >>Method 2: As NPM Package

Adjust Environment Variables (if needed)
If using environment variables, make sure to set them up in your environment configuration or .env files.
Save Changes:
Save the file containing the updated code.
Build and Deploy:
Compile or bundle your project based on your build process, and deploy the changes to your server or hosting service.
Verification:
Go to any screen after login and right-click anywhere
In the dropdown menu, select Inspect.

In the elements tab, Use the Ctrl + F or Cmd + F and search for “reo”

If the tracking code appears, verify that the code matches.

Error Scenarios

Script initiation
Script initiation has been modified to rely on code initiation only on successful callback post download from CDN. So it will only initiate if successfully downloaded. In case the download fails, the javascript won’t get enabled but this eliminates the likelihood of an error scenario of page breaking
API failure on token delete
On deletion of all Reo tokens, the most recent event tracking data will likely fail, but subsequent API calls will work fine
Any inadvertent code failure on JavaScript
This should not be an issue since the code is wrapped in a try-catch block, the console may throw errors, which won’t be visible even on the console since logger would be disabled on the script

Cookie Management and Compliance

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

Adding Form URLs in Reo.Dev

Once your JS is installed and deployed, go to:

Settings → Integrations → Tracking Beacon → Forms

Here you can:

Add the URL of the page where your form lives (e.g., /contact).
Give the form a custom name for easier identification later.

Once saved, this name becomes available in the Segment builder under:

Activity Group → Forms → Key Pages: Forms

You can then use this to create segments of users who visited those pages.

Note: This filter currently identifies all visitors to the page, not just form submitters. We’re working on enhancing this feature so you’ll soon be able to filter users who specifically filled out the form on a configured page.

Content Security Policy (CSP) Considerations

If your website uses a strict Content Security Policy (CSP), you may need to update it to allow our script to load and execute correctly. Please ensure the following directives are updated to include our domains:

Required CSP Directives

script-src https://static.reo.dev;
connect-src https://api.reo.dev;

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.

PreviousTrack Code Interactions NextInstall JavaScript for Website/Documentation through Google Tag Manager

Last updated 7 days ago

Was this helpful?