Collection diagnostics · FIELD GUIDE
Diagnose an analytics script blocked by CSP
Use the browser policy violation and the delivered page policy to locate a tracker execution failure without weakening site security.
What the evidence can establish
The presence of a tracker tag does not establish that the browser executed it. MDN documents script-src as the policy directive that controls allowed JavaScript sources. It also explains that policies containing default-src or script-src normally block inline JavaScript unless additional authorization is supplied. This gives a concrete starting point: identify the blocked resource or inline bootstrap, then inspect the policy delivered with that specific page. A screenshot of the tag alone cannot resolve an execution failure.
Hypothetical example: a site adds a small inline bootstrap that loads its analytics bundle. The external bundle’s hostname is permitted, but the browser reports an inline-script violation. Adding more external hosts would not address the observed failure. The relevant question is whether the bootstrap follows the site’s existing nonce or hash design. The example illustrates a decision path; it does not report a test of your deployment.
The saved evidence used here
This guide interprets dated official documentation. It does not report traffic from a customer or a measured AI answer. Each material claim is mapped to a source below.
- c1 · Explanation and verification steps
- script-src controls permitted JavaScript sources. Source 1
- c2 · Explanation and verification steps
- A policy containing default-src or script-src blocks inline JavaScript unless additional measures authorize it. Source 1
- c3 · Explanation and verification steps
- A nonce or hash can authorize an inline script under the documented CSP approach. Source 1
The diagram explains the investigation or a clearly labeled hypothetical example. No measured counts or platform outcomes are added.
AI answer visibility: Not measured. No original platform answers or verified citation records were collected for this guide. A request count is not an audience, ranking or citation count.
What to do next
- Reproduce one authorized page load with the browser console and Network panel open. Save the violation’s directive, blocked resource description, page URL and time. Exclude any personal console data.
- Retrieve the final HTML response and its Content-Security-Policy header. Compare the deployed policy with the expected template, including whether the failing code is inline or external.
- Ask the site maintainer to align the tracker integration with the established policy mechanism. Avoid replacing a narrow policy with a wildcard or removing security controls merely to make the counter move.
- Retest the exact page and an unrelated page after the scoped change. Confirm the expected script executes and separately verify an authorized event reaches the collector. Keep both pieces of evidence.
How to check the result
The original policy violation is absent for the approved integration, the expected script loads, and a collector record confirms the test event. These checks establish execution and delivery for the tested pages only.
Limits of this conclusion
Other failures can occur after a script loads. This guide addresses script execution policy, not every network, consent or application error. It does not prescribe a universal CSP or claim that security review occurred.
This is a saved, dated edition. Source documentation can change. This edition retains the original retrieval dates and claim mapping; follow the sources before applying version-specific guidance.
Sources and publication checks
Automated checks validate source availability, supported fields, duplicate wording, numeric figures and page configuration. This guide was prepared with AI assistance and checked against saved source passages in the same authoring session. The batch importer checks source fingerprints, quotation locations, wording overlap and required fields. No paid generation API or separate model-review pass was used for this batch. These checks can miss errors and are not expert or human review.
Obtained: 2026-11-02T17:15:16.084600+00:00
Location: Fetch directives / b107; Fetch directives / b117; Fetch directives / b53
Saved source fingerprint
4a72a98374f28c1aff284ad9f205c5b231039cc064a031dea415e3de24fffeb9