-
Session Attributes vs GCLID capture?
Posted by on September 20, 2025 at 1:42 amSo, I am familiar with GCLID capture and passback for conversions and even having GCLID sent in invisible form fields with email form submissions but then I saw this on session attributes. Is GCLID capture outdated and not good enough anymore? https://support.google.com/google-ads/answer/16194756#capture&zippy=%2Cadvanced
-
1 Reply
-
GCLID is often stripped by privacy features in browsers or ad blockers and can be lost for other reasons too like redirects that don’t handle passing the query string forward. So I’d say you lose a lot of trackability by only relying on GCLID and the session attributes seems to be Google’s way to try and fix that.
I hadn’t heard of session attributes before this thanks for sharing the news!
-
GCLID is not outdated … it’s still the main click ID for Google Ads conversion tracking and offline imports. Keep capturing and passing it back.
1. New identifiers: WBRAID/GBRAID are used when GCLID isn’t available (e.g., iOS privacy restrictions).
2. Enhanced Conversions for Leads: lets you send hashed user data (email, phone, etc.) to improve match rates and is Google’s recommended upgrade.
3. Session attributes: an additional fallback signal in the Google Ads API when you don’t have a click ID or full user data.
keep GCLID capture, add WBRAID/GBRAID, implement Enhanced Conversions, and use session attributes as a backup.
Log in to reply.