{
  "acceptance": "The test demonstrates the intended association in the relevant reporting context, or the report clearly marks the join unverified. The original business event and its analytics linkage remain distinct records.",
  "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": [
        2
      ],
      "statement": "Measurement Protocol supplements data collected through tagging or the Firebase SDK."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        2
      ],
      "statement": "Use cases have identifier and timing requirements."
    },
    {
      "id": "c3",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Events intended to join client-side events have additional receipt-time guidance."
    },
    {
      "id": "c4",
      "section": "Explanation and verification steps",
      "source_numbers": [
        3
      ],
      "statement": "session_id and engagement_time_msec matter for activity in reports such as Realtime."
    }
  ],
  "description": "Separate event acceptance from the evidence needed to join a server event to an earlier online interaction.",
  "diagram": [
    "Offline action record",
    "Authorized original session context",
    "Use-case timing and validation",
    "Verify linkage in the report"
  ],
  "draft_hash": "6592904508321a56e9138b2506a4a726359af1b39bcbdb066678cf22e8cf7dff",
  "evidence": {
    "observed_at": "2026-11-02T12:45:39.899864+00:00",
    "period": {
      "end": "2026-11-02T12:45:39.899864+00:00",
      "start": "2026-11-02T12:45:39.899864+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": [
    "Keep the original business event as its own record.",
    "Do not fabricate missing session identifiers.",
    "Check the requirements for the intended reporting use case.",
    "Event delivery alone does not establish correct attribution."
  ],
  "figure_title": "Preserve session context for offline GA4 events",
  "group": "Event validation and attribution",
  "human_review_claim": false,
  "intent": "ga4-offline-event-session-context",
  "interpretation": "Google describes Measurement Protocol as a way to supplement data already collected through tagging or the Firebase SDK. Its use-case guidance includes session identifiers and timing conditions, while the sending guide gives additional guidance for events intended to join client-side events. This means syntactic event acceptance is not enough to demonstrate correct session context. Preserve the authorized context at the time of the online interaction instead of reconstructing it from an unrelated later visit.",
  "keyword_volume": "Not obtained",
  "limits": "Backdating eligibility does not guarantee session attribution. This is a method for testing an existing authorized integration, not a recommendation to collect additional personal identifiers.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/ga4-offline-event-session-context/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "An offline event is accepted but the report assumes it inherited the intended online session and attribution.",
  "product": "/ai-analytics",
  "published_at": "2026-11-04T14:10:12.441160+00:00",
  "reader": "Site owners and analysts investigating an offline event is accepted but the report assumes it inherited the intended online session and attribution.",
  "related": [
    "missing-ai-referral-data",
    "ga4-delayed-event-timestamps"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/missing-ai-referral-data/",
      "title": "Handle missing AI referrers without inventing attribution"
    },
    {
      "path": "/ai-analytics/guides/ga4-delayed-event-timestamps/",
      "title": "Check timestamp units and age before replaying GA4 events"
    }
  ],
  "research_document_ids": [
    "35eb00af329a2074dcdd3cd716e2439a",
    "4541c61b351c428a3ae7d04585b9012c",
    "6112800a450ff66a7687246de7f74a2f"
  ],
  "slug": "ga4-offline-event-session-context",
  "source_signature": "8712c0f8631ac530f96a2acc24a8275298e065c739a0e0cb9ede2968b3029e5b",
  "sources": [
    {
      "hash": "aadcc3650743d383da7fdadce4ff2f9c207fb76474559e5a426335b0d643cc2f",
      "locator": "Validation behavior for past events and user properties / b58",
      "observed_at": "2026-11-02T13:15:26.657565+00:00",
      "title": "Send Measurement Protocol events to Google Analytics",
      "url": "https://developers.google.com/analytics/devguides/collection/protocol/ga4/sending-events"
    },
    {
      "hash": "7fdf3755328b17a464ddcc991b1b6eb57bf7f018e6e4bef4a973293f970d5832",
      "locator": "Page Summary / b3; Page Summary / b6",
      "observed_at": "2026-11-02T13:45:41.483481+00:00",
      "title": "Measurement protocol use cases",
      "url": "https://developers.google.com/analytics/devguides/collection/protocol/ga4/use-cases"
    },
    {
      "hash": "481853cd73c44de90ea5965e26813c56aadc57b7a784dee19afc27772919c1f3",
      "locator": "Page Summary / b4",
      "observed_at": "2026-11-02T12:45:39.899864+00:00",
      "title": "Measurement Protocol reference",
      "url": "https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference"
    }
  ],
  "sources_required": [],
  "steps": [
    "Define the exact goal: recording an offline action, associating it with an online interaction, or inspecting Realtime activity. These goals have different acceptance evidence.",
    "Check the documented identifiers and timing requirements for that use case. Preserve only context that the implementation is authorized to collect; do not fabricate a session link from IP or device guesses.",
    "Validate the event structure, then test the intended linkage with an isolated authorized scenario. Inspect the relevant session or attribution result rather than stopping at a transport response.",
    "Record unresolved linkage separately from event-delivery status. If the business record exists but analytics context is missing, report that distinction rather than assigning a confident acquisition source."
  ],
  "title": "Preserve session context for offline GA4 events",
  "worked_example": "Hypothetical example: a server receives confirmation of an action after the original browser session. The operator attaches a convenient new session identifier just to make the event visible. That can change the question the report answers. A more defensible workflow retains the intended linkage data when permitted, verifies the relevant use-case requirements and marks the join unverified when the original context is unavailable."
}