Click ID upload
Use GCLID, GBRAID, or WBRAID fields. Keep one click identifier per click-conversion row when the workflow requires exactly one.
Use this checklist before uploading an offline conversion CSV to Google Ads preview. Google Ads supports additional template formats, but this local checker only validates CSV files.
Last updated: June 6, 2026. Re-check the official Google Ads documentation before changing production import workflows.
Use GCLID, GBRAID, or WBRAID fields. Keep one click identifier per click-conversion row when the workflow requires exactly one.
Use pre-hashed user-provided data where required by your workflow. Plain email, phone, first name, last name, or street address values should be reviewed as blockers.
Manual workflows may allow Google Ads to hash some plain values, but you still need valid email/phone formatting and final preview in Google Ads.
Do not treat this local checker as a Google Ads Data Manager schema validator or an official account setup check.
Every row needs a usable identifier for the chosen workflow: a valid click ID, valid email, valid phone, or complete address-style user data. Location-only fields such as country or postal code are not enough.
Match the conversion action name used in Google Ads. Empty values are a high-risk upload problem.
Use a parseable date and time. Include a row-level timezone or a file-level Parameters:TimeZone row when your export uses one timezone.
Use numeric conversion values and ISO 4217 currency codes such as USD, EUR, GBP, SGD, or JPY.
If your workflow uses consent signals, review Ad User Data and Ad Personalization values before previewing the file.
Use Order ID when appropriate, then check repeated identifier + conversion name + conversion time combinations before importing.
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 the template and file-format boundary. This checker focuses on CSV preflight and does not support every Google Ads template format.
Used for the exactly-one click identifier boundary in API-style click conversion rows.
Used for the enhanced conversions for leads and Data Manager boundary.
Used for upload timing windows, old conversion review signals, and final Google Ads validation boundaries.