Solution skill
Diag: RUM SDK silent, check console, blockers, and intake requests
Complete solution
Shows how to fix diag: RUM SDK silent, check console, blockers, and intake requests. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Disable all extensions / test in a clean profile. Fix: add the SDK and intake domains to the CSP, move the snippet ahead of the consent gate (or accept that gated users produce no sessions), fix the token pair.
Steps
- Symptom (exact): snippet present in the page, but devtools Network shows no requests to Datadog intake and Sessions stay empty.
- Likely causes: (a) ad/privacy blocker eating the SDK, (b) Content Security Policy blocking the script or the intake domain, (c) snippet never executes (consent gate, wrong route), (d) wrong clientToken/applicationId.
- Browser console first: CSP violations name the blocked URL explicitly. 4xx on intake requests means the token/ID pair is wrong.
- Disable all extensions / test in a clean profile. Sessions appearing means (a); this is the most common false negative in RUM debugging.
- View source on the tested page: is the snippet actually there? Behind a consent banner that was never accepted is still never executed.
- Compare the token and application ID in the snippet against the application settings in the Datadog app, character by character.
- Verify: devtools shows intake requests on page load and on actions, and a session appears in the explorer within a minute. Keep one clean-profile browser around for every future RUM check.
When to use
You are seeing this: Symptom (exact): snippet present in the page, but devtools Network shows no requests to Datadog intake and Sessions stay empty. Use this skill when you run into "Diag: RUM SDK silent, check console, blockers, and intake requests".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
The RUM browser setup docs: the SDK needs the clientToken and applicationId from the created application; browser console shows CSP violations and failed intake requests when blocked. Verified against live docs 2026-09-26.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_IZtJqkHQFTZm-7DgLq-q3A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Diag: RUM SDK silent, check console, blockers, and intake requests <span>— Vectle</span></a>