Debug Google Ads Conversion in Chrome DevTools

What Google Ads Conversion traffic looks like

Conversion hits carry their ID in the URL path, and the path segment tells you the conversion type.

Endpoint pattern

googleads.g.doubleclick.net and www.googleadservices.com under /pagead/, with the conversion ID embedded in the path (/pagead/conversion/123456789/?...); the segment gives the type: /conversion/ click conversions, /viewthroughconversion/ view-through, /1p-conversion/ the first-party redirect flow, /conversion_async/ the async variant. Newer consent-mode setups additionally route through google.com/ccm/collect with a tid=AW-... parameter

Key parameters

label (or l): the conversion label that pairs with the AW- ID to identify the specific conversion action · value, currency, oid conversion value, currency, and order ID (the dedup key)

Identity

ec_mode enhanced conversions mode (hashed user data accompanies the hit) · auid, gclaw, gcldc identity and click-ID linkage (gclaw carries the gclid)

Consent signals

gcs and gcd: Google Consent Mode state; gcs=G111 means ad storage and analytics storage granted, gcs=G100 denied

Debugging Google Ads Conversion with Event Watcher

• Ships a dedicated parser: each hit is labeled with its conversion type and ID, for example Click 123456789.
• The detail view groups the decoded request: conversion label, value, currency, order ID, and enhanced-conversions mode under Conversion; click IDs and cookie linkage under Identity; Chrome UA-CH fields under User Agent; GTM hash, frame, and transport flags under Request.
• Consent Mode parameters are read out as consent signals on the event, so the gcs/gcd state is visible without decoding it by hand.

Google Ads Conversion and consent

The extension checks these hits against marketing consent, with the Consent Mode nuance that separates Google tags from every other ad pixel.

Under Consent Mode, the conversion tag still fires when marketing consent is denied, but as a cookieless ping: gcs=G100, no identifying cookies attached.

Event Watcher reads the CMP state and the Consent Mode signals together, so a legitimate cookieless ping is distinguishable from a mis-gated tag sending full conversion data pre-consent.

A hit carrying gcs=G111 before the user answered the banner means consent defaults are configured wrong. Walk through debug Google Consent Mode v2, including the gcd string that encodes default versus updated states.

Common debugging scenarios

• Conversions double-count. Compare oid across purchase hits. A missing or regenerated order ID on refresh means transaction dedup cannot work.
• Conversion fires with no value. Check the Conversion group for value and currency; when the tag reads the dataLayer, trace the source push with which script pushed the dataLayer event.
• Enhanced conversions silently inactive. Look for ec_mode on the hit. Its absence means the user-data configuration never engaged and match rates will not improve.
• Everything routes through ccm/collect. That is the consent-aware pathway. Verify the tid=AW- parameter and consent signals rather than expecting the classic /pagead/conversion shape.
• View-through hits confuse the report. Filter by event name to separate View-Through from Click conversions; they are distinct paths on the wire, not one tag.