Date only
2026-05-22
Missing time of day; attribution and import preview may be ambiguous.
Conversion time errors are common in offline conversion CSV files. Check the row timestamp, optional file-level Parameters:TimeZone value, future dates, and old conversion warnings before Google Ads preview.
Last updated: June 6, 2026. Re-check the official Google Ads documentation before changing production import workflows.
| Example | How to use it |
|---|---|
| Parameters:TimeZone=America/Chicago | File-level timezone parameter. Use when rows omit timezone values and the whole file uses one timezone. |
| Parameters:TimeZone=-0500 | File-level GMT offset parameter. Timezone IDs are usually safer around daylight saving changes. |
| 05/22/2026 14:30:00 -0500 | Numeric date and time with a GMT offset. |
| 05/22/2026 02:30:00 PM | US-style date with 12-hour time. Add a file-level timezone if rows do not carry their own offset. |
| 2026-05-22 14:30:00+0800 | ISO-style date and time with a compact numeric offset. |
| 2026-05-22T14:30:00 America/Los_Angeles | ISO-style date and time with an IANA timezone ID. |
2026-05-22
Missing time of day; attribution and import preview may be ambiguous.
05/22/2026 14:30:00
The checker can parse the date, but the intended timezone is unclear.
2099-05-22 14:30:00 +0000
Usually indicates wrong timezone, wrong date column, or bad export logic.
A click-ID row older than the expected import window
Review before upload; the local checker cannot confirm final eligibility.
The checker reads a CSV in your browser and reports file-level risks. It does not connect to Google Ads, Data Manager, Google Ads API, your CRM, or your account. It cannot confirm conversion action ownership, click ownership, account permissions, customer data terms, Data Manager schema rules, template compatibility for every file format, import preview status, or final attribution. Always preview and validate the corrected file in the official Google Ads workflow.
These links support the page boundary and the local checks described here. They are not copied into the checker as a complete Google Ads validator, and the checker should not be described as official Google guidance.
Used for file-level timezone parameters, supported conversion time formats, file import boundaries, and scheduled upload hashing notes.
Used for upload timing windows, old conversion review signals, and final Google Ads validation boundaries.
Used for API-style offline conversion and hashed user-provided data context.
Use the CSV checker to flag date-only, future, old, timezone-less, invalid timezone, and unparseable conversion time values before Google Ads import preview.
Open the checker