Finding an _gcl_au cookie does not prove that a WordPress form captured a Google Ads click ID or that a CRM lead can be attributed to an ad. Cookie presence, click-ID capture and conversion reporting are separate observations. Verify the complete lead path instead of renaming a cookie value to GCLID.
Keep the identifiers separate
Google's cookie explanation describes the advertising-measurement purpose of the _gcl_ family. That is not a promise that every cookie in the family contains the raw identifier required by your integration. A landing-page gclid parameter and an _gcl_au value are not interchangeable fields.
| Evidence |
What it establishes |
| Click identifier reaches landing URL |
That value survived this part of the visit |
| Advertising cookie exists |
A tag stored that particular cookie |
| Form entry contains the expected value |
Capture reached the submission record |
| CRM field retains the value |
The integration preserved the mapping |
| Ads reports an eligible conversion |
The destination processed its attribution rules |
Do not infer the final row from the second. Likewise, a missing visible cookie alone does not describe all possible measurement behavior under every consent model.
Test the handoff with synthetic data
Create a staging test with a clearly synthetic marker in the field your own capture code reads. Follow the actual path through redirects, a second page and the form. A marker can test transport through your code; it cannot demonstrate valid Google attribution and must never be uploaded as a real ad click.
Inspect the form after it renders, especially in a popup. Submit a harmless test entry and compare the stored identifier with the outbound integration payload and final CRM field. Record whether a subsequent automation replaces the value with blank data. Keep first-touch and later-touch policies explicit rather than letting the last script to run decide them.
Identity: Do not rename cookie as GCLID. Synthetic marker: Transport test only. Consent: Respect approved choices. Destination: Verify actual mapped field. Explanatory checklist, not a customer test result.
Check the Google tag setup without duplicating it
Google's Conversion Linker documentation explains how ad-click information is stored and how cookie prefix overrides must agree with consuming tags. It also states that a container loading a Google tag on every page does not additionally need a Conversion Linker tag. Inspect the installed setup before adding another tag based on an older checklist.
If a custom prefix is used, document why and confirm that the consuming tags use the same configuration. Do not change a prefix to _gcl_au simply because that is the cookie you can see. Prefixes, complete cookie names and click-ID fields serve different purposes.
Respect the approved consent state
Repeat permitted tests for no choice, rejection and acceptance according to the site's approved implementation. Do not force advertising storage to make a debugging screenshot look successful. Use redacted evidence, not full visitor cookie strings, in support tickets.
For missing fields, continue with GCLID capture in WordPress forms. When browser capture succeeds but the CRM loses the value, HandL WP can inspect the attribution mapping without treating a cookie's existence as a completed measurement audit.
References reviewed October 12, 2026. Examples are explanatory, not customer test results.