Cloud Product
You can track developers who access your cloud product to analyze their interactions on the product.
Start by clicking on 'Integrations'
Then, click on 'Configure' in the Cloud Product card
Step 1: Configure Cloud Product URL
Add the Cloud Product URLs you want to track in the Cloud Product URL field. You can choose to add multiple cloud instances of your product.
Add a Page Name for every domain under the Page Name field
Once added, you can create a Segment to view accounts/developers/buyers interacting with your product.The page name will appear under the ‘Key Product Pages’ filter while creating segments.
Step 2: Add Key Pages
This is an optional step. But we highly recommend this. Some pages within your product signal high user intent—indicating that users are actively engaging with or setting up your tool. Tracking these Key Pages helps you identify accounts showing high intent.
For example:
Dashboard settings or integrations – Users configuring integrations might indicate onboarding progress.
Account & Subscription pages – Frequent visits to billing or account management suggest decision-making.
API Access or Authentication pages – Developers generating API tokens signal deeper product adoption.
To add the key pages:
Add URLs of specific pages/sections in your product you want to track activities on.
Add a Page Name for each URL
Tracking dynamic URLs with wildcards
If your URLs include dynamic segments — like a project ID or org name — you can track them as a single Key Page by using * as a wildcard in place of the dynamic part.
For example, to track the journeys page across every project - you can set up the URL as /project/*/journeys
Reo will capture all URLs matching this pattern, no matter what sits in place of the *. To set this up:
Add the Key Page URL with
*as the wildcard for the dynamic partHit Save — Reo will start tracking all URLs that match the pattern
Note:
Wildcards mid-URL (like
abc.com/id/*/orgpage) are supportedA trailing wildcard like
abc.com/page/*isn't needed. Reo automatically captures everything after the last/, so it's redundant.
You can create a Segment to see accounts/developers/buyers interacting with specific Key Pages. The page name will appear under ‘Key Product Pages’ filter ****while creating segments.
Step 3: Install Tracking Pixel
Copy the tracking code snippet directly from Reo's UI and paste it in the <header> of your site. Replace "XXXXXXXXXXX" with the client ID.
Note: Here are a few more ways you can install Javascript on your cloud instance:
Using Google Tag Manager. Here’s the setup guide.
Using NPM Package. Here’s the setup guide.
Step 4: Invoke Sign-in Event
This is an essential step to track product logins.
Sign-in flows can be in-house, using a 3rd party or IDP based. Hence we have exposed an event which needs to be invoked in the call-back of your successful sign-in with appropriate payload.
The payload for sign-in needs to contain two mandatory attributes username and type. Invoke identify method to send sign-in details which basically tells Reo who the user is and that they have logged in.
In case of use with NPM, we need to resolve the promise before we can invoke identify method on it. Make sure to initialise the snippet using Reo.init before using Reo.identify
Once Done, click on Save.
Once you’ve set up the entire integration, click on Check status to see if all the URLs are connected.
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.
Important to Note:
By default, we track copy commands in your product environment. This is needed so that you can learn which of your logged in prospects (e.g. free users/ trial users) are showing high intent activities such as copy pasting code blocks or executing CLIs, which are a great proxy to learn their evaluation maturity and intent. We take multiple measures to ensure no sensitive information is captured or stored:
A locally deployed AI model automatically identifies and skips sensitive information such as passwords, API keys, and card numbers, ensuring we skip as much of sensitive information as possible.
Additionally, since the AI model can make mistakes, all captured data, including emails and copied text, is encrypted in our database. Decryption is handled via a tenant hash stored in a remote cloud vault, accessible only where applicableAll captured data, including emails and copied text, is encrypted in our database. Decryption is handled via a tenant hash stored in a remote cloud vault, accessible only where applicable.
To disable tracking for copy commands - use the dnt track flag. Copy the tracking code snippet below:
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
Last updated
Was this helpful?