Event validation and attribution · FIELD GUIDE
Check timestamp units and age before replaying GA4 events
Preserve when an event actually happened and understand the documented handling of backdated Measurement Protocol events.
What the evidence can establish
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.
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.
The saved evidence used here
This guide interprets dated official documentation. It does not report traffic from a customer or a measured AI answer. Each material claim is mapped to a source below.
- c1 · Explanation and verification steps
- timestamp_micros uses microseconds and supports documented backdating. Source 2
- c2 · Explanation and verification steps
- Timestamp selection follows a documented priority order. Source 1
- c3 · Explanation and verification steps
- Event or user-property timestamps have first priority. Source 1
- c4 · Explanation and verification steps
- For older-than-window data, relaxed validation can adjust the timestamp. Source 1
- c5 · Explanation and verification steps
- Strict recommendation enforcement rejects older-than-window data. Source 1
- c6 · Explanation and verification steps
- The request timestamp follows event-level timestamps in the documented priority. Source 1
- c7 · Explanation and verification steps
- Receipt time is used after the explicit timestamps in the documented priority. Source 1
The diagram explains the investigation or a clearly labeled hypothetical example. No measured counts or platform outcomes are added.
AI answer visibility: Not measured. No original platform answers or verified citation records were collected for this guide. A request count is not an audience, ranking or citation count.
What to do next
- 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.
How to check the result
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.
Limits of this conclusion
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.
This is a saved, dated edition. Source documentation can change. This edition retains the original retrieval dates and claim mapping; follow the sources before applying version-specific guidance.
Sources and publication checks
Automated checks validate source availability, supported fields, duplicate wording, numeric figures and page configuration. This guide was prepared with AI assistance and checked against saved source passages in the same authoring session. The batch importer checks source fingerprints, quotation locations, wording overlap and required fields. No paid generation API or separate model-review pass was used for this batch. These checks can miss errors and are not expert or human review.
Obtained: 2026-11-02T13:15:26.657565+00:00
Location: 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
Saved source fingerprint
aadcc3650743d383da7fdadce4ff2f9c207fb76474559e5a426335b0d643cc2fObtained: 2026-11-02T12:45:39.899864+00:00
Location: timestamp_micros / b32
Saved source fingerprint
481853cd73c44de90ea5965e26813c56aadc57b7a784dee19afc27772919c1f3