{
  "acceptance": "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.",
  "automated_checks": true,
  "batch_id": "analytics-editorial-20261104-v1",
  "built_at": "2026-11-04T11:50:28.566595+00:00",
  "claims": [
    {
      "id": "c1",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "script-src controls permitted JavaScript sources."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "A policy containing default-src or script-src blocks inline JavaScript unless additional measures authorize it."
    },
    {
      "id": "c3",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "A nonce or hash can authorize an inline script under the documented CSP approach."
    }
  ],
  "description": "Use the browser policy violation and the delivered page policy to locate a tracker execution failure without weakening site security.",
  "diagram": [
    "Markup: tracker is present",
    "Console: identify policy violation",
    "Policy: match the failing script",
    "Collector: verify a test event"
  ],
  "draft_hash": "dbf7a4e3bbb99f079b13ab83f3c6833d35e81ee4dbab6501e3d80e61a462865a",
  "evidence": {
    "observed_at": "2026-11-02T17:15:16.084600+00:00",
    "period": {
      "end": "2026-11-02T17:15:16.084600+00:00",
      "start": "2026-11-02T17:15:16.084600+00:00",
      "timezone": "UTC"
    },
    "rows": [],
    "scope": "Official documentation; no customer or own-site traffic measurement"
  },
  "evidence_kind": "documentation",
  "figure_caption": "Original explanatory diagram based on the dated sources below. Any example values are hypothetical; this is not a screenshot, customer measurement or AI platform result.",
  "figure_kind": "decision",
  "figure_notes": [
    "Inspect the deployed markup; presence alone does not prove execution.",
    "Record the failing directive and blocked resource.",
    "Use the established nonce or hash approach where appropriate.",
    "Confirm an authorized event arrives after script execution."
  ],
  "figure_title": "Diagnose an analytics script blocked by CSP",
  "group": "Collection diagnostics",
  "human_review_claim": false,
  "intent": "csp-blocked-analytics-script",
  "interpretation": "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.",
  "keyword_volume": "Not obtained",
  "limits": "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.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/csp-blocked-analytics-script/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "The analytics script is present in page markup but does not execute under the delivered Content Security Policy.",
  "product": "/ai-analytics",
  "published_at": "2026-11-04T12:05:03.826099+00:00",
  "reader": "Site owners and analysts investigating the analytics script is present in page markup but does not execute under the delivered Content Security Policy.",
  "related": [
    "collector-heartbeat-vs-zero-traffic"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/collector-heartbeat-vs-zero-traffic/",
      "title": "Distinguish zero traffic from a collection failure"
    }
  ],
  "research_document_ids": [
    "6463cd4406c0d8ba5e6d54a9e8c39167"
  ],
  "slug": "csp-blocked-analytics-script",
  "source_signature": "a7da096e4884637352417586825b7a2fcc282a7b9f5cf5b8a114b76764dc2785",
  "sources": [
    {
      "hash": "4a72a98374f28c1aff284ad9f205c5b231039cc064a031dea415e3de24fffeb9",
      "locator": "Fetch directives / b107; Fetch directives / b117; Fetch directives / b53",
      "observed_at": "2026-11-02T17:15:16.084600+00:00",
      "title": "Content Security Policy (CSP)",
      "url": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP"
    }
  ],
  "sources_required": [],
  "steps": [
    "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."
  ],
  "title": "Diagnose an analytics script blocked by CSP",
  "worked_example": "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."
}