{
  "acceptance": "The report explains its context categories, includes missing values, and reproduces totals from the retained records. A browser-context field is never presented as verified AI crawler identity.",
  "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": "Fetch Metadata communicates request context."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "The destination field describes the request destination as defined by Fetch."
    },
    {
      "id": "c3",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "The mode field describes the request mode."
    }
  ],
  "description": "Add browser request context to an investigation while keeping it separate from visitor identity and verified crawler classification.",
  "diagram": [
    "Raw context headers",
    "Normalize known values",
    "Retain an unknown category",
    "Compare roles without claiming identity"
  ],
  "draft_hash": "570d1aa78b8280f6de1ec94b5445ff27e42febcc0c4f2e71ab28dd62e68e341b",
  "evidence": {
    "observed_at": "2026-11-02T20:15:34.069227+00:00",
    "period": {
      "end": "2026-11-02T20:15:34.069227+00:00",
      "start": "2026-11-02T20:15:34.069227+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": "comparison",
  "figure_notes": [
    "Use only fields actually retained by the approved logger.",
    "Explain how raw values become report categories.",
    "Missing context stays unknown; it is not silently discarded.",
    "Request context does not authenticate a client."
  ],
  "figure_title": "Use Fetch Metadata to explain request context",
  "group": "Collection diagnostics",
  "human_review_claim": false,
  "intent": "fetch-metadata-analytics-request-context",
  "interpretation": "MDN describes Fetch Metadata as request headers that communicate the context in which a request is made. The documented destination and mode fields can help an analyst explain why a browser requested a document or supporting resource. These are contextual observations, not a substitute for the site action being measured. A report should also preserve an unknown category because not every request source will supply the same headers.",
  "keyword_volume": "Not obtained",
  "limits": "This is a diagnostic use of recorded headers. It does not supply a bot-authentication rule or establish that a request was made by a person. Historical coverage depends on what was actually logged.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/fetch-metadata-analytics-request-context/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "An access-log investigation cannot distinguish a document navigation from a supporting resource request using the URL alone.",
  "product": "/ai-analytics",
  "published_at": "2026-11-04T12:15:11.453421+00:00",
  "reader": "Site owners and analysts investigating an access-log investigation cannot distinguish a document navigation from a supporting resource request using the URL alone.",
  "related": [
    "browser-pageviews-vs-log-requests",
    "crawler-user-agent-verification"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/browser-pageviews-vs-log-requests/",
      "title": "Reconcile browser pageviews with server requests"
    },
    {
      "path": "/ai-analytics/guides/crawler-user-agent-verification/",
      "title": "Separate crawler names from verified request identity"
    }
  ],
  "research_document_ids": [
    "85505293a2c500f9b6c7443259def3a8"
  ],
  "slug": "fetch-metadata-analytics-request-context",
  "source_signature": "fcbe4fc0f86aabeabdf5b2ebbfb0c016e07b4c981d678eef73c8fcf4ac5cea6f",
  "sources": [
    {
      "hash": "d0b5db0eaf263af95827fe38d0148defd22708f1bc632ca5bed0a6959e88094a",
      "locator": "Fetch metadata / b1; Sec-Fetch-Dest / b8; Sec-Fetch-Mode / b17",
      "observed_at": "2026-11-02T20:15:34.069227+00:00",
      "title": "Fetch metadata",
      "url": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Fetch_metadata"
    }
  ],
  "sources_required": [],
  "steps": [
    "Check whether your approved logging configuration retains the relevant Fetch Metadata fields. Inspect a controlled browser request before assuming the field exists in historical logs.",
    "Build a small dictionary that separates raw recorded values, normalized report categories and missing values. Preserve the raw value in a restricted diagnostic record when needed.",
    "Compare a document navigation, a resource load and an application request from a controlled session. Describe the observed context without claiming that it authenticates the client.",
    "Use the context dimension to investigate a specific discrepancy, then reconcile totals including the unknown category. Do not silently remove requests just because their context differs from a browser example."
  ],
  "title": "Use Fetch Metadata to explain request context",
  "worked_example": "Hypothetical example: a page navigation and its supporting script request appear in the same time window. Keeping the recorded destination values alongside the paths helps explain that these requests played different roles. It does not turn the navigation into a verified person or the script request into a second visit. If a field is absent, keep the request unclassified rather than filling a value from the URL suffix."
}