GCLID, GBRAID, and WBRAID CSV IDs
GCLID, GBRAID, and WBRAID fields are click identifiers used in offline conversion workflows. Check that identifier columns exist, are not blank, are not malformed, and are not accidentally combined before upload.
Last updated: June 6, 2026. Re-check the official Google Ads documentation before changing production import workflows.
Use a usable identifier for each row
Click-ID upload rows usually need a usable Google Click ID, GBRAID, or WBRAID. Rows without a valid click identifier or eligible user-data workflow are high risk because Google Ads may not be able to match them.
Use exactly one click ID in API-style click conversion rows
For the click-conversion workflow this checker models, each row should provide exactly one of GCLID, GBRAID, or WBRAID. If the same row contains multiple click IDs, the checker treats that as a blocker in click-ID workflow mode. Confirm edge cases in the official Google Ads workflow or API documentation before changing production imports.
Keep GCLID, GBRAID, and WBRAID in separate columns
Do not combine identifiers into one free-text field. Separate columns make the CSV easier to validate, troubleshoot, and map during the Google Ads upload preview.
Do not edit captured IDs manually
Click identifiers should be exported exactly as captured by the lead form, CRM, or landing page system. Trimming, lowercasing, splitting, or reformatting IDs can reduce match quality.
Do not mix click-ID imports with PII unless the workflow requires it
Legacy click-ID file imports and user-data preflight workflows have different assumptions. Use the workflow selector in the checker so the report does not apply user-data rules to a click-only file or click-only age rules to a user-data file.
What this local checker cannot verify
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.
Official sources used
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.
- Google Ads API sample: Upload offline conversion
Used for the exactly-one click identifier boundary in API-style click conversion rows.
- Google Ads API: Offline conversion troubleshooting
Used for click-conversion troubleshooting boundaries, including rows that combine multiple click IDs.
- Google Ads Help: Import conversions from ad clicks using files
Used for file-level timezone parameters, supported conversion time formats, file import boundaries, and scheduled upload hashing notes.
- Google Ads Help: Guidelines for importing offline conversions
Used for upload timing windows, old conversion review signals, and final Google Ads validation boundaries.
Check identifier fields before import
Use the local CSV checker to find missing click IDs, malformed click IDs, duplicate conversion records, mixed identifiers, and Order ID risks before previewing the upload in Google Ads.
Open the checker