{
  "acceptance": "The page and export state the same observation period, and the report explains whether it is live or historical. Delivery cache age is reported separately when relevant.",
  "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": "Age reports time in seconds associated with an object in a proxy cache."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Age is represented as a non-negative number of seconds."
    }
  ],
  "description": "Separate proxy-cache residence from the observation window shown inside a saved report.",
  "diagram": [
    "Fetch time: when you requested it",
    "Age: delivery cache residence",
    "Evidence cutoff: observed data window",
    "Page contract: live or historical"
  ],
  "draft_hash": "0aaf72fa22d30bcafc3a7699e5c31436a1039ac2b85660214a0b28fc0683a5c1",
  "evidence": {
    "observed_at": "2026-11-03T19:30:57.869115+00:00",
    "period": {
      "end": "2026-11-03T19:30:57.869115+00:00",
      "start": "2026-11-03T19:30:57.869115+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": [
    "Record this separately from the report’s observation period.",
    "This describes delivery caching, not the dataset’s age.",
    "Keep the original measured or documented interval visible.",
    "An immutable incident edition is different from a live view."
  ],
  "figure_title": "An Age header is not the age of your analytics data",
  "group": "Collection diagnostics",
  "human_review_claim": false,
  "intent": "age-header-vs-analytics-data-freshness",
  "interpretation": "MDN defines Age as time in seconds associated with an object in a proxy cache. That is a delivery-layer signal. The observation period inside an analytics report is a different fact that must come from the report data or saved evidence. A newly delivered response can contain an old reporting window, while a cached response can still contain the intended immutable historical edition. Compare the two clocks instead of collapsing them into one freshness label.",
  "keyword_volume": "Not obtained",
  "limits": "Age is not a complete cache-history record and does not establish when every underlying measurement was collected. This method does not imply that a dated report must always be regenerated.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/age-header-vs-analytics-data-freshness/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "A report labels its underlying analytics data as fresh or stale using only the HTTP Age response header.",
  "product": "/ai-analytics",
  "published_at": "2026-11-04T11:50:31.943675+00:00",
  "reader": "Site owners and analysts investigating a report labels its underlying analytics data as fresh or stale using only the HTTP Age response header.",
  "related": [
    "saved-analytics-report-freshness",
    "analytics-incident-recovery-evidence"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/saved-analytics-report-freshness/",
      "title": "Check the freshness of a saved analytics report"
    },
    {
      "path": "/ai-analytics/guides/analytics-incident-recovery-evidence/",
      "title": "Document recovery without rewriting an incident"
    }
  ],
  "research_document_ids": [
    "73d740bac5525901242d468fa0cc507a"
  ],
  "slug": "age-header-vs-analytics-data-freshness",
  "source_signature": "3baf02756fd15e6e55843d270d1e46c1d7c815e5af871a698c40b0da2671cb43",
  "sources": [
    {
      "hash": "7ee649dfe383193d46a78fdf72cc94ad43dbf15df07894edea24c3331a60df3c",
      "locator": "Age header / b2; Directives / b4",
      "observed_at": "2026-11-03T19:30:57.869115+00:00",
      "title": "Age header",
      "url": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Age"
    }
  ],
  "sources_required": [],
  "steps": [
    "Record the final response headers and the reporting interval visible in the page or evidence export. Keep the fetch time separate from both values.",
    "Identify the page contract: live dashboard, periodically refreshed summary or immutable historical edition. State the expected update behavior for that contract.",
    "Compare the saved evidence cutoff and publication version with the intended interval. Use Age only to investigate delivery caching, together with the relevant cache configuration.",
    "After a scoped correction, verify that the requested report version and observation interval are delivered. Preserve the prior historical edition when it is part of the audit trail."
  ],
  "title": "An Age header is not the age of your analytics data",
  "worked_example": "Hypothetical example: a report response has Age: 120, but the report body explicitly summarizes last week. The header describes cache residence, not a two-minute-old dataset. Conversely, a saved incident edition may remain useful precisely because it preserves last week’s observations. Decide whether the page promises a live view or a dated snapshot before calling that behavior defective."
}