Google Data Manager API returns EVENT_TIME_INVALID when an event did not occur inside the acceptable time window. Replacing the original timestamp with retry time changes business truth, while retrying the same invalid row wastes quota and keeps the queue blocked.
Use this for WordPress forms, WooCommerce orders, CRM-qualified leads, offline conversions, queue workers, backfills, and any Data Manager API integration that can retry after an outage.
Quick answer
Data Manager API EVENT_TIME_INVALID Window and Retry Policy should be handled with a narrow evidence-first workflow: preserve all timestamps, check utc and clock drift, stop blind retries, then verify the result before making broader changes.
What to check first
- Preserve source event time, enqueue time, first attempt time, retry time, timezone, and request ID as separate fields.
- Compare application, database, queue worker, and host clocks against UTC and identify future timestamps or timezone conversion errors.
- Classify EVENT_TIME_INVALID as a data correction or dead-letter case instead of a normal transport retry.
- Correct only a provable parsing, unit, or timezone defect while retaining the original source timestamp for audit.
- Replay one corrected synthetic row, retrieve request status, and monitor invalid-time rate by source and queue age.
Diagnostic table
Use this table to keep the work practical. It connects the symptom to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|
| Preserve all timestamps | Preserve source event time, enqueue time, first attempt time, retry time, timezone, and request ID as separate fields. | A valid synthetic event succeeds without changing its original occurrence time. |
| Check UTC and clock drift | Compare application, database, queue worker, and host clocks against UTC and identify future timestamps or timezone conversion errors. | An old or future-dated fixture enters a visible dead-letter path and does not retry forever. |
| Stop blind retries | Classify EVENT_TIME_INVALID as a data correction or dead-letter case instead of a normal transport retry. | Request status links the final result to the same internal event ID and source record. |
| Correct proven defects | Correct only a provable parsing, unit, or timezone defect while retaining the original source timestamp for audit. | Dashboards separate queue delay, clock drift, parsing errors, and permanent window rejects. |
Why this usually happens
- Seconds can be parsed as milliseconds or a local timestamp can be labeled UTC.
- A queue outage can hold events beyond the product's accepted window.
- A worker can overwrite original event time with the current retry timestamp.
- Clock drift can create future-dated events even when the source application looks correct.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
event_id: order-1842-purchase
source_event_time: 2026-07-15T13:02:11Z
enqueued_at: 2026-07-15T13:02:13Z
first_attempt_at: 2026-07-15T13:02:20Z
retry_at: null
error_reason: EVENT_TIME_INVALID
action: dead_letter_for_timestamp_review
Safe fix order
Do the work in a sequence that makes each result easy to prove. Stop if a step produces new evidence that changes the incident scope.
- Preserve all timestamps
- Check UTC and clock drift
- Stop blind retries
- Correct proven defects
- Replay and monitor
What to tell the client or owner
Provide redacted event ID, source type, all UTC timestamps, source timezone, queue age, request ID, error reason, clock comparison, correction decision, and replay result.
Production verification checklist
- A valid synthetic event succeeds without changing its original occurrence time.
- An old or future-dated fixture enters a visible dead-letter path and does not retry forever.
- Request status links the final result to the same internal event ID and source record.
- Dashboards separate queue delay, clock drift, parsing errors, and permanent window rejects.
Mistakes to avoid
- Do not judge the fix by one browser or the homepage only.
- Do not delete evidence before recording usernames, file paths, timestamps, and response headers.
- Do not add a cache, security, or tracking plugin while the original problem is still unclear.
- Do not leave test users, temporary debug logs, or broad API keys active after verification.
When HandL WP should help
Bring in help when this affects leads, checkout, search visibility, malware risk, paid media reporting, or a client production site. HandL WP can trace the issue through WordPress, hosting, cache, tracking, and Search Console, then verify the workflow after the technical fix.
If this is active on a production site, fix a Data Manager API conversion queue.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references