Cookie Consent Integration with Telemetery.js
The Cookie Consent Integration with Telemetery.js feature is under Public Preview for customers with solution packaging only. Please contact your account representative or OneTrust Support to request early access.
Using Telemetry.js with the OneTrust CMP enables continuous runtime monitoring to help identify tracking technologies that execute during real user sessions.
Telemetry.js enhances web scanning by observing tracking technologies as they run on your site. This helps provide a more complete view of technologies that may not appear during a scheduled scan, such as technologies triggered after page load, during navigation, or after a user interaction.
What is Telemetry.js?
Telemetry.js is a lightweight script that works with OneTrust Cookie Consent to help detect tracking technologies during normal website activity. It complements scheduled scans by observing activity that happens in the browser while users interact with your site.
When should I use Telemetry.js?
| Scenario | How Telemetry.js helps |
|---|---|
| Dynamic websites or single-page applications | Helps detect technologies that load during navigation or after page updates. |
| Logged-in or authenticated experiences | Because Telemetry.js runs on the page where it is deployed, it can help observe technologies inside pages that require sign-in or authentication, provided the user can access the page normally. For logged-in or authenticated pages, deploy Telemetry.js on the authenticated page or template you want to evaluate, then complete the relevant user journey. Telemetry.js can be used as a standalone script for those pages so that technologies running behind authentication can be observed during normal access. |
| Interaction-based tracking | Helps detect technologies that run after actions such as selecting buttons, opening menus, or completing a flow. |
| Scan completeness review | Helps compare what is configured or scanned against what runs during real website usage. |
Before you begin
| Requirement | Description |
|---|---|
| Website access | Confirm you can deploy OneTrust scripts to the website or through your approved tag management process. |
| Test plan | Identify the pages and user journeys you want to validate, such as checkout flows, authenticated areas, or SPA navigation. |
| Tracking technologies review process | Confirm who will review and categorize newly detected technologies. |
To enable Telemetery.js
- On the Cookie Consent menu, select Integration > Website scripts. The Website scripts screen appears.
- Select the the domain where script will be implemented.
- Generate or copy the Telemetry.js script provided by the OneTrust platform.
Add the script to the website using your approved deployment process. Script publication is not required. For authenticated areas, deploy the script on the logged-in page or shared template that supports the experience you want to evaluate.
- Open your site and complete the user journeys you want Telemetry.js to observe. For authenticated experiences, sign in normally and navigate through the pages included in your validation plan.
To validate Telemetry.js is running
Technical users can optionally confirm that Telemetry.js is running by checking browser developer tools after the script is deployed. Use this validation only if your organization normally validates website scripts this way.
For logged-in or authenticated pages, complete the normal sign-in flow first, then open the page or journey you want to validate. This helps confirm Telemetry.js is running in the authenticated experience where the script was deployed.
- In your browser's developer tools, check the telemetry eligibility request.
A successful eligible response confirms the domain is enabled for telemetry collection.
- Check for telemetry collection requests after completing the page journey.
A collect request indicates that eligible tracking technology signals are being sent for processing.
To review newly detected technologies
- On the Cookie Consent menu, select Tracking technologies.
The Tracking technologies screen appears.
- Select a technology record.
Behavior and troubleshooting
Expected behavior
- Runtime detection
- Telemetry.js helps capture tracking technologies that execute during real user journeys.
- Pending review workflow
- Newly detected technologies may require review before they are fully categorized.
- Processing delay
- Newly detected technologies may not appear immediately after a user journey is completed.
- Customer-controlled deployment
- Your organization controls where the script is deployed and which journeys are validated.
Known considerations
- Results may take time to appear
- Allow time for detected technologies to be processed before reviewing results.
- Deployment should be intentional
- Deploy Telemetry.js only on approved domains and pages included in your validation plan.
- Network/security controls may affect collection
- If your site blocks outbound calls or scripts, coordinate with your security or web team.
Troubleshooting
- Telemetry.js does not appear to run
- Confirm the script is deployed on the page and the page can load OneTrust resources.
- No new technologies appear
- Confirm the test journey triggered technologies that were not already in your inventory, then allow time for processing.
- Authenticated pages do not show results
- Confirm Telemetry.js is deployed on the logged-in page or template, then sign in and complete the authenticated journey normally.
- Only limited results appear
- Test additional pages and user journeys, especially dynamic, authenticated, or interaction-based flows.
- Network or security errors occur
- Review firewall, CSP, CDN, or tag management rules that may prevent OneTrust scripts or calls from loading.
Frequently asked questions
Does Telemetry.js replace scheduled scanning?
No. Telemetry.js is intended to complement scheduled scanning by helping observe technologies that run during real user activity.
Can Telemetry.js be used on logged-in pages?
Yes. Telemetry.js can be used on authenticated pages where the script is deployed and the user can access the page normally. This helps observe technologies that may only execute after sign-in.
Where do newly detected technologies appear?
New technologies appear on the Tracking technologies screen for review.
For more information, see Managing Tracking Technologies.
Will newly detected technologies be automatically categorized?
Known technologies will be categorized. Unknown tracking technologies will display as Unknown.
Can Telemetry.js help with dynamic websites?
Yes. Telemetry.js is designed to help observe technologies that execute during runtime behavior, including dynamic or interaction-based activity.