{
  "acceptance": "One test action has an explainable chain from browser permission check to submission and collector result. The dashboard labels OPTIONS separately and does not add it to conversions. An absent or rejected submission remains explicitly unresolved or rejected.",
  "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": "Some cross-origin requests require an OPTIONS permission check before the actual request."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Some requests do not trigger a CORS preflight."
    }
  ],
  "description": "Separate OPTIONS checks, event requests and accepted records when a browser collector appears to receive twice the expected traffic.",
  "diagram": [
    "OPTIONS: permission check",
    "POST: submission attempt",
    "Collector: accept or reject",
    "Business action: separate evidence"
  ],
  "draft_hash": "88516624ac13408f888e7e91e93798077245e8ef2c1f42c6760fdf410ff9a32e",
  "evidence": {
    "observed_at": "2026-11-02T13:00:11.392791+00:00",
    "period": {
      "end": "2026-11-02T13:00:11.392791+00:00",
      "start": "2026-11-02T13:00:11.392791+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": "sequence",
  "figure_notes": [
    "Read requested method and headers; this is a permission check.",
    "Confirm that the actual event submission follows.",
    "Match the test to a collector acceptance or rejection record.",
    "Verify the underlying action independently of transport success."
  ],
  "figure_title": "CORS preflights are not delivered analytics events",
  "group": "Collection diagnostics",
  "human_review_claim": false,
  "intent": "cors-preflight-vs-event-delivery",
  "interpretation": "A browser can ask permission before sending a cross-origin event request. MDN describes this preflight as an OPTIONS request that declares the intended method and headers. The permission check and the event submission answer different questions. Counting every request to the collection path as an event therefore mixes transport activity with the action you intended to measure. Start with the request method and the collector’s actual acceptance record; a successful preflight establishes neither payload validation nor a completed business action.",
  "keyword_volume": "Not obtained",
  "limits": "Not every cross-origin request requires a preflight. A missing OPTIONS row is not proof of a collection failure. This procedure does not establish user identity, Google indexing or AI citations.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/cors-preflight-vs-event-delivery/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "A cross-origin collector shows more HTTP requests than the application shows events.",
  "product": "/ai-analytics",
  "published_at": "2026-11-04T12:00:11.476325+00:00",
  "reader": "Site owners and analysts investigating a cross-origin collector shows more HTTP requests than the application shows events.",
  "related": [
    "analytics-event-retry-deduplication",
    "server-confirmed-analytics-events"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/analytics-event-retry-deduplication/",
      "title": "Prevent delivery retries from inflating outcomes"
    },
    {
      "path": "/ai-analytics/guides/server-confirmed-analytics-events/",
      "title": "Measure completed actions separately from clicks"
    }
  ],
  "research_document_ids": [
    "6b36a3f1e01a1c6b3e1525b1b34c3cb9"
  ],
  "slug": "cors-preflight-vs-event-delivery",
  "source_signature": "4124b60599554f7ff50b11b80dbb74a2f6526038fbef55db76843f11d048c02f",
  "sources": [
    {
      "hash": "1ea5441964610865aaa9a011c10ba99d4d11ee64134a92c29be33464d7a3d1ff",
      "locator": "Functional overview / b12; Simple requests / b16",
      "observed_at": "2026-11-02T13:00:11.392791+00:00",
      "title": "Cross-Origin Resource Sharing (CORS)",
      "url": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS"
    }
  ],
  "sources_required": [],
  "steps": [
    "Open the browser Network panel for one authorized test action. Preserve the collector URL, method, status and time for each request; remove cookies, authorization headers and personal payload fields before sharing evidence.",
    "Inspect the OPTIONS request and response together. Compare the requested method and headers with the permitted values. Record whether the actual POST follows; do not infer it from the preflight status.",
    "Find the corresponding collector acceptance or rejection record. Use a test correlation value your own implementation supports, then distinguish an accepted analytics event from the server-confirmed business action.",
    "Change the report definition so preflights are counted as transport checks. Repeat the same test and verify that the HTTP totals and accepted-event totals each reconcile to their own source."
  ],
  "title": "CORS preflights are not delivered analytics events",
  "worked_example": "Hypothetical example: one controlled signup causes an OPTIONS request followed by a POST. A path-only access report contains two rows. Your investigation worksheet should contain one permission check, one submission attempt and, only if the application records it, one accepted signup event. If OPTIONS succeeds but the POST never appears, investigate the browser’s next step. If both arrive but validation rejects the payload, the accepted-event count remains zero. These are diagnostic categories, not measurements from Future InTech."
}