{
  "acceptance": "The tracker URL serves the expected JavaScript representation with an appropriate media type, and the controlled event is accepted by the collector. The evidence includes the tested release or asset fingerprint.",
  "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": "JavaScript should be served with text/javascript; arbitrary media types should not be assumed to work."
    }
  ],
  "description": "Diagnose a tracker URL that serves an HTML fallback or the wrong media type before treating the response as successful JavaScript delivery.",
  "diagram": [
    "200 status: response received",
    "Content-Type: expected JavaScript",
    "Body: approved asset version",
    "Runtime: test event accepted"
  ],
  "draft_hash": "df859287f0c9a2be6bd3b1e67fd9cba9ab4205caa4fbc51dd2fbd955b11726ab",
  "evidence": {
    "observed_at": "2026-11-02T20:45:49.841495+00:00",
    "period": {
      "end": "2026-11-02T20:45:49.841495+00:00",
      "start": "2026-11-02T20:45:49.841495+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": [
    "A successful status alone does not prove asset delivery.",
    "Check the delivered media type, not only the filename.",
    "Detect an HTML fallback or the wrong bundle version.",
    "Execution and collector acceptance need separate checks."
  ],
  "figure_title": "A tracker URL returns 200: check the content type and body",
  "group": "Collection diagnostics",
  "human_review_claim": false,
  "intent": "analytics-script-mime-type",
  "interpretation": "An HTTP status is only one part of a script-delivery check. MDN recommends text/javascript for JavaScript content and warns against assuming that other media types will always load or run as scripts. A deployment or routing problem can also send a page body at the expected asset path. Inspect the final URL, Content-Type and actual response together. A green 200 row does not establish that the expected tracking code was delivered or executed.",
  "keyword_volume": "Not obtained",
  "limits": "Content-Type alone cannot prove that a script is correct or safe. Caching, CSP, consent and runtime errors may still prevent collection after asset delivery is repaired.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/analytics-script-mime-type/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "A tracker request returns HTTP 200 but delivers a different representation from the JavaScript file the page expects.",
  "product": "/ai-analytics",
  "published_at": "2026-11-04T11:55:09.117718+00:00",
  "reader": "Site owners and analysts investigating a tracker request returns HTTP 200 but delivers a different representation from the JavaScript file the page expects.",
  "related": [
    "csp-blocked-analytics-script",
    "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": [
    "6a58d1a89a8d66f03189bdbde82786eb"
  ],
  "slug": "analytics-script-mime-type",
  "source_signature": "10d19def64689c92e2be071a44faeef2a4a4c1d5977872707beb081235aab592",
  "sources": [
    {
      "hash": "99b3fb8d0abdc380c2106917055d39502273f929029e36687e6b771c6e3ecc40",
      "locator": "text/javascript / b34",
      "observed_at": "2026-11-02T20:45:49.841495+00:00",
      "title": "Media types (MIME types)",
      "url": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/MIME_types"
    }
  ],
  "sources_required": [],
  "steps": [
    "Inspect the final tracker response in the browser Network panel. Save its URL, status, Content-Type and a non-sensitive indication of whether the body matches the intended asset.",
    "Compare the delivered asset with the approved release manifest or expected bundle fingerprint. Use a version marker when your build supplies one; do not rely only on the filename.",
    "Correct the missing asset, fallback route or media-type configuration at the responsible layer. Keep script-security controls enabled while fixing the delivered representation.",
    "Reload in a controlled session and verify both script execution and one accepted test event. Record those as separate checks so delivery success cannot conceal an application failure."
  ],
  "title": "A tracker URL returns 200: check the content type and body",
  "worked_example": "Hypothetical example: /assets/analytics.js is absent from a release, and the site serves its ordinary HTML fallback at that path. The Network panel shows 200, but the response starts with page markup rather than the expected bundle. This observation points to asset routing or deployment as the next investigation, not to an unexplained reporting delay. It is not a claim about the current Future InTech asset route."
}