UNPARSEABLE_GCLID
Google Ads couldn't parse the GCLID you provided. Learn why GCLIDs become unparseable — truncation, URL encoding, GBRAID confusion — and how to fix each cause.
Common Causes
| # | Cause | Likelihood | Details |
|---|---|---|---|
| 1 | Truncated GCLID | Very Common | Your CRM or form tool has a field length limit that cuts off the GCLID. GCLIDs are typically 50-100 characters, but many CRM text fields default to 50 or even 32 characters. The truncated value is syntactically invalid. |
| 2 | URL double-encoding | Common | The GCLID was URL-encoded during capture (e.g., special characters replaced with %3D, %2B) and not decoded before storage. The encoded version is a different string than the original GCLID. |
| 3 | GBRAID or WBRAID sent as GCLID | Common | Post-iOS 14.5, Google may use GBRAID or WBRAID instead of GCLID. These are different identifiers with different formats. If your system captures whichever click ID is present and puts it in the GCLID field, the API will reject GBRAID/WBRAID values as unparseable GCLIDs. |
| 4 | CMS or redirect stripping characters | Moderate | Some CMS platforms, URL shorteners, or redirect chains strip or modify URL parameters. Characters like underscores (_), hyphens (-), or padding (=) in Base64-encoded GCLIDs may be removed during redirects. |
| 5 | Manual copy-paste errors | Less Common | When GCLIDs are manually copied between systems, extra whitespace, line breaks, or partial selections can corrupt the value. |
What It Means (Plain English)
The GCLID string you sent to Google Ads is malformed — Google’s system cannot decode it into a valid click identifier. Unlike CLICK_NOT_FOUND (which means the GCLID is valid but doesn’t match a click), UNPARSEABLE_GCLID means the string itself is corrupted or in the wrong format.
This is always an error that needs fixing. Every unparseable GCLID represents a conversion that cannot be attributed to any ad click.
How to Fix It
Step 1: Check Your CRM Field Length
This is the #1 cause. Check the character limit on whatever field stores the GCLID in your CRM, form tool, or database:
- HubSpot: Default custom property limit may be too short — set to “Single-line text” with no character limit
- Salesforce: Custom field → increase to 255 characters
- Google Sheets: No limit (unlikely to be the issue)
- Custom database: Set column to
VARCHAR(255)orTEXT
Step 2: Check for URL Encoding
If your GCLID contains % characters (like %3D, %2B, %2F), it was URL-encoded and needs to be decoded. Most programming languages have a decodeURIComponent() or equivalent function.
// Before (encoded — will fail):
EAIaIQobChMI%3Dexample%2B123
// After (decoded — correct):
EAIaIQobChMI=example+123Step 3: Verify You’re Not Sending GBRAID/WBRAID
Check if the value starts with known GCLID patterns (usually EAIaIQob). If it’s shorter and doesn’t match this pattern, it might be a GBRAID or WBRAID. These must be sent in their own dedicated fields in the API request:
gclid→ GCLID onlygbraid→ GBRAID onlywbraid→ WBRAID only
Step 4: Audit Your Redirect Chain
If you use URL shorteners, tracking redirects, or CMS-level redirects, test the full chain by clicking an actual ad and checking the stored GCLID at each step. Some tools strip or modify URL parameters during redirects.
Step 5: Validate Before Upload
Use the TUOCA GCLID Decoder to validate stored GCLIDs before uploading. Batch-check your CRM export to identify patterns (all truncated at the same length = field limit issue).
How TUOCA Prevents This
The Upload Offline Conversions App includes multiple safeguards:
- Automatic GCLID validation — Every GCLID is checked for format validity before upload. Invalid GCLIDs are flagged in the activity log.
- Click ID type detection — TUOCA identifies whether a value is a GCLID, GBRAID, or WBRAID and routes it to the correct API field automatically.
- URL decoding — Encoded GCLIDs are automatically decoded before validation.
- Pre-upload filtering — Unparseable GCLIDs are excluded from the upload batch to prevent the entire request from failing, with fallback to Enhanced Conversions when PII is available.