{
  "acceptance": "The report defines both units, records the test separately and explains coverage differences without relabeling an unknown gap as lost customers.",
  "automated_checks": true,
  "built_at": "2026-11-01T17:45:04.202695+00:00",
  "description": "Browser pageviews and log requests have different scopes. Reconcile collection rules before treating the difference as missing traffic.",
  "diagram": [
    "Define counting units",
    "Check eligibility",
    "Align time and paths",
    "Explain remaining gaps"
  ],
  "evidence": {
    "observed_at": "2026-11-01T16:09:23+00:00",
    "period": {
      "end": "2026-11-01T16:09:23+00:00",
      "start": "2026-10-31T15:00:00+00:00",
      "timezone": "UTC"
    },
    "rows": [
      {
        "label": "Log requests",
        "unit": "requests",
        "value": 458
      },
      {
        "label": "Browser pageviews",
        "unit": "pageview events",
        "value": 16
      }
    ],
    "scope": "own_site_selected_public_paths",
    "self_tests_excluded": false
  },
  "figure_caption": "Original explanatory workflow. Numeric callouts reproduce dated own-site evidence; they are not an AI platform test.",
  "figure_title": "Reconcile browser pageviews with server requests",
  "group": "Measurement operations",
  "human_review_claim": false,
  "intent": "browser-pageviews-vs-log-requests",
  "interpretation": "A log request belongs to a server observation layer; a browser pageview follows browser and consent rules. Resources, robots, repeats and cache behavior can affect the populations. Dividing the totals does not produce a visibility rate.",
  "keyword_volume": "Not obtained",
  "limits": "The aggregate cannot reconstruct individual journeys. Controlled checks may appear in both populations.",
  "path": "/ai-analytics/guides/browser-pageviews-vs-log-requests/",
  "policy": "analytics-evidence-v1",
  "problem": "Browser pageviews and log requests have different scopes. Reconcile collection rules before treating the difference as missing traffic.",
  "product": "/ai-analytics",
  "published_at": "2026-11-02T05:05:11.667115+00:00",
  "reader": "Website owners, SEO analysts and site operators",
  "related": [
    "/learn/ai-crawler-logs-vs-ai-visibility/",
    "/research/ai-crawler-analytics/"
  ],
  "slug": "browser-pageviews-vs-log-requests",
  "source_signature": "e12f24686422382f1d8a29cdbadcf4b196a18f0bb37ce1a1c67a3990c29eafdc",
  "sources": [
    {
      "hash": "54a7b1645b80ae3466689f04be544208ae7cba23239d2b80199317616123f92a",
      "locator": "populations",
      "observed_at": "2026-11-01T16:09:23+00:00",
      "title": "Saved own-site monitoring evidence",
      "url": "https://future-intech.com/research/ai-crawler-analytics/"
    }
  ],
  "sources_required": [],
  "steps": [
    "Inventory included paths, event types and consent conditions for each dataset.",
    "Run one labeled, permitted test visit and check its expected request and browser event.",
    "Align the observation intervals and page scope before looking for missing records.",
    "Keep unmatched evidence unresolved; do not publish private identifiers to force a join."
  ],
  "title": "Reconcile browser pageviews with server requests",
  "worked_example": "The saved metrics below preserve requests and pageview events as different units. Their difference is a reconciliation question, not a count of people who declined consent."
}