{
  "acceptance": "The timestamp fixture round-trips correctly, field precedence is intentional, and out-of-window events are handled explicitly. A delayed replay does not silently rewrite historical observations.",
  "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": "timestamp_micros uses microseconds and supports documented backdating."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Timestamp selection follows a documented priority order."
    },
    {
      "id": "c3",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Event or user-property timestamps have first priority."
    },
    {
      "id": "c4",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "For older-than-window data, relaxed validation can adjust the timestamp."
    },
    {
      "id": "c5",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Strict recommendation enforcement rejects older-than-window data."
    },
    {
      "id": "c6",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "The request timestamp follows event-level timestamps in the documented priority."
    },
    {
      "id": "c7",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Receipt time is used after the explicit timestamps in the documented priority."
    }
  ],
  "description": "Preserve when an event actually happened and understand the documented handling of backdated Measurement Protocol events.",
  "diagram": [
    "Original occurrence time and unit",
    "Event versus request timestamp",
    "Age and validation behavior",
    "Observed reporting time"
  ],
  "draft_hash": "cb65c45994c9c6c16d28b6fded60ea29bd04159ece88c4dc64a168f044ec2abe",
  "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": [
    "Check microseconds rather than copying milliseconds.",
    "Make the controlling timestamp explicit.",
    "Handle old events according to documented validation behavior.",
    "Do not silently substitute replay time for occurrence time."
  ],
  "figure_title": "Check timestamp units and age before replaying GA4 events",
  "group": "Event validation and attribution",
  "human_review_claim": false,
  "intent": "ga4-delayed-event-timestamps",
  "interpretation": "The Measurement Protocol reference specifies timestamp_micros in microseconds, not milliseconds. Google also documents a timestamp priority: an event or user-property timestamp takes precedence over the request-level timestamp, followed by receipt time when no explicit timestamp is supplied. The sending guide describes a 72-hour backdating window and different behavior beyond it under relaxed and strict validation. A replay process must therefore preserve event time and validation behavior as explicit inputs.",
  "keyword_volume": "Not obtained",
  "limits": "The documented backdating window is not a guarantee of every attribution or joining use case. This guide does not authorize replaying personal data or assert that an old event can be recovered unchanged.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/ga4-delayed-event-timestamps/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "A delayed event queue sends timestamps with the wrong units or replays events beyond the documented backdating window.",
  "product": "/ai-analytics",
  "published_at": "2026-11-04T12:20:09.600779+00:00",
  "reader": "Site owners and analysts investigating a delayed event queue sends timestamps with the wrong units or replays events beyond the documented backdating window.",
  "related": [
    "ga4-measurement-protocol-validation",
    "analytics-event-retry-deduplication"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/analytics-event-retry-deduplication/",
      "title": "Prevent delivery retries from inflating outcomes"
    }
  ],
  "research_document_ids": [
    "35eb00af329a2074dcdd3cd716e2439a",
    "6112800a450ff66a7687246de7f74a2f"
  ],
  "slug": "ga4-delayed-event-timestamps",
  "source_signature": "110fd4941df0afcddab8dadb22f5bf644c42cbb1db2f67057407a38a470b6d22",
  "sources": [
    {
      "hash": "aadcc3650743d383da7fdadce4ff2f9c207fb76474559e5a426335b0d643cc2f",
      "locator": "Override timestamp / b44; Override timestamp / b45; Override timestamp / b46; Override timestamp / b47; Validation behavior for past events and user properties / b56; Validation behavior for past events and user properties / b57",
      "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": "481853cd73c44de90ea5965e26813c56aadc57b7a784dee19afc27772919c1f3",
      "locator": "timestamp_micros / b32",
      "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": [
    "Document the original event clock, stored unit and conversion applied at submission. Verify a known timestamp fixture by converting it back to a human-readable UTC time.",
    "Inspect both event-level and request-level timestamp fields. Confirm which one should control the event and remove accidental contradictory values.",
    "Classify queued events by age before replay. Apply the documented validation behavior and retain an explicit rejected or unsupported-history outcome where appropriate.",
    "Compare an authorized test event’s intended occurrence time with its observed reporting time. Keep submission time, occurrence time and any processing adjustments in separate fields."
  ],
  "title": "Check timestamp units and age before replaying GA4 events",
  "worked_example": "Hypothetical example: a queue stores event time in milliseconds and copies that integer into a microsecond field. The payload may look numeric while representing the wrong instant. A separate case is an old event replayed under relaxed validation: the documented handling can change the timestamp rather than preserve the original occurrence time. Neither problem should be hidden by relabeling replay time as event time."
}