Cookie consent for Google for WooCommerce

What Google for WooCommerce adds to your visitors’ browser

What matters for consent with Google for WooCommerce

What our tests found on Google for WooCommerce

• Set before the choice · Google for WooCommerceGoogle for WooCommerce's badge waits only with WP Consent API

  With WP Consent API it waits for marketing consent. Without it, the script loads at once on every page.

  Seen in our tests, 5 November 2026, Google for WooCommerce 3.10.0.

  Full detail

  Google for WooCommerce 3.10.0 creates its reviews badge script www.gstatic.com/shopping/merchant/merchantwidget.js in JavaScript. With the WP Consent API plugin active, the script waits for marketing consent and loads after Accept without a reload, and nothing loads after Refuse. Without that plugin it loads at once on every page.

• Depends on a setting · Google for WooCommerceGoogle for WooCommerce adds its own consent default after the banner's

  Once a Google Ads conversion exists, its tag loads on every page with its own default consent for 32 European countries, set after the consent banner's default.

  What to do: Return an empty string from woocommerce_gla_gtag_consent so only the consent plugin sets the defaults.

  Read in its code, 5 November 2026, Google for WooCommerce 3.10.0.

  Full detail

  Google for WooCommerce adds gtag.js with its AW- ID to every page once a Google Ads conversion action exists, at wp_head priority 999999, with its own gtag('consent','default'): ad_storage, analytics_storage, ad_user_data and ad_personalization denied for 32 European countries (EU, IS, LI, NO, GB, CH), wait_for_update 500. It arrives after a banner's default; the filter woocommerce_gla_gtag_consent replaces or removes it, and woocommerce_gla_disable_gtag_tracking removes the whole tag. The filter woocommerce_gla_gtag_consent changes or empties that default.

• Depends on a setting · Google for WooCommerceGoogle for WooCommerce enhanced conversions print the address in clear text

  setting “Enhanced conversions” · by default: off

  Off by default. When on, each page of a known customer prints the email, names and phone hashed, but the street, city, postal code and country in clear text.

  Read in its code, 16 October 2026, Google for WooCommerce 3.9.6.

  Full detail

  With Google for WooCommerce's enhanced conversions on (off by default), every page of a known customer's session prints gtag('set','user_data') with the email, first name, last name and phone hashed (SHA-256), but the street, city, region, postal code and country in clear text in the HTML.

• Good to know · Google for WooCommerceGoogle for WooCommerce passes WP Consent API choices to Google

  When WP Consent API is present, its script reads the statistics and marketing choices, sends Google's consent update and follows later changes. It does not register with WP Consent API.

  Read in its code, 16 October 2026, Google for WooCommerce 3.9.6.

  Full detail

  When WP Consent API is present and Google Analytics for WooCommerce is not, Google for WooCommerce loads wp-consent-api.js, which reads the WP Consent API statistics and marketing cookies and sends gtag('consent','update') at DOMContentLoaded (statistics to analytics_storage; marketing to ad_storage, ad_user_data, ad_personalization), and listens for wp_listen_for_consent_change. It sets wp_consent_type to optin if empty and does not register with WP Consent API.

Google

Other plugins of the same kind.

Every plugin and theme we test →