Website
Reo.Dev can track developers who visit your website to analyze their interactions and transform this data into actionable insights for your sales funnel.
Step 1: Configure Website URL
Add the website base URLs you want to track. You can choose to add multiple base and sub-domain URLs by clicking on ‘Add New’.
The Base URL is the main domain under which all your tracked pages exist. For example:
If your website is
https://www.example.com, set the Base URL asexample.com.If you want to track only a subdomain like docs.example.com, then set
docs.example.comas the Base URL.

Add a Page Name for each base URL

Once added, you can create a Segment to view accounts/developers/buyers interacting with website. The page name will appear under the ‘Key Website Pages’ filter while creating segments.
Step 2: Add Key Pages
This is an optional step, but adding your high-intent website pages helps you track activities on specific pages of your website separately.
For example:
Case Study Pages – Visitors researching customer success stories are likely evaluating your solution.
Pricing Page – A strong indicator of purchase intent.
Integration or Solution Pages – Suggests users are exploring how your tool fits into their workflow.
Landing Pages with UTM parameters – Helps track the effectiveness of specific marketing campaigns.
To add key pages:
Add URLs of specific website pages you want to track activities on

Add a Page Name for each URL

You can create a Segment to see accounts/developers/buyers interacting with specific Key Pages. The page name will appear under Key Website Pages filter while creating segments.
Step 3: Install Tracking Pixel
Copy the below tracking code snippet and paste it in the <header> of your site
Here are few more ways you can install JavaScript on your website pages:
Using Google Tag Manager. Here’s the setup guide.
Using NPM Package. Here’s the setup guide.
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
Copy
Reo.Dev can track developers who visit your website to analyze their interactions and transform this data into actionable insights for your sales funnel.
Step 1: Configure Website URL
Add the website base URLs you want to track. You can choose to add multiple base and sub-domain URLs by clicking on ‘Add New’.
The Base URL is the main domain under which all your tracked pages exist. For example:
If your website is
https://www.example.com, set the Base URL asexample.com.If you want to track only a subdomain like docs.example.com, then set
docs.example.comas the Base URL.

Add a Page Name for each base URL

Once added, you can create a Segment to view accounts/developers/buyers interacting with website. The page name will appear under the ‘Key Website Pages’ filter while creating segments.
Step 2: Add Key Pages
This is an optional step, but adding your high-intent website pages helps you track activities on specific pages of your website separately.
For example:
Case Study Pages – Visitors researching customer success stories are likely evaluating your solution.
Pricing Page – A strong indicator of purchase intent.
Integration or Solution Pages – Suggests users are exploring how your tool fits into their workflow.
Landing Pages with UTM parameters – Helps track the effectiveness of specific marketing campaigns.
To add key pages:
Add URLs of specific website pages you want to track activities on

Add a Page Name for each URL

You can create a Segment to see accounts/developers/buyers interacting with specific Key Pages. The page name will appear under Key Website Pages filter while creating segments.
Step 3: Install Tracking Pixel
Copy the below tracking code snippet and paste it in the <header> of your site
Here are few more ways you can install JavaScript on your website pages:
Using Google Tag Manager. Here’s the setup guide.
Using NPM Package. Here’s the setup guide.
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
Copy
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.
Last updated
Was this helpful?

