When WooCommerce is active, the scan of the Cookies page also opens the shop, cart, checkout and account pages. WooCommerce order attribution sets cookies whose names start with sbjs_. They serve marketing, so they must wait for the visitor’s choice. WooCommerce waits for it when it can read the choice through WP Consent API. With Cookie Rocks Pro With WP Consent API, WooCommerce reads the choice that Cookie Rocks Pro passes to it. Without WP Consent API, Cookie Rocks Pro turns order attribution off by default. It then turns it on or off on each page and at each change, following the marketing choice. The sbjs_ cookies are deleted when a visitor withdraws marketing consent. For the whole shop: Set up consent for an online shop.

WP Consent API: Cookie Rocks documentation

Written for Cookie Rocks 2.9.14, checked on 5 November 2026. The current version is 2.11.2: some details may have changed.

WP Consent API is a free WordPress plugin. It shows nothing to visitors. It passes the visitor’s choice from the cookie banner to other plugins, in a standard way.

Site Kit by Google, WooCommerce, Jetpack and WP Statistics read the choice through it. Without it, they cannot know what the visitor accepted.

Set it up in 3 steps

On the Overview page of Cookie Rocks, click Install WP Consent API. It opens the page of WP Consent API in the WordPress plugin installer, with its Install Now button.
Install and activate the plugin.
Come back to the Overview page. The WP Consent API card says Connected.

If you see “Not needed yet”. No plugin of your site reads the choice through WP Consent API. Install it when you add one, such as WooCommerce.

If you see “… does not support” WP Consent API. WP Consent API passes the choice only if your banner supports it. With your current banner, Site Kit and WooCommerce still cannot read the choice.

What the Audit checks

The WP Consent API card of the Overview says Connected when the plugin is active, Missing when a plugin of your site needs it (Site Kit, WooCommerce, Jetpack or WP Statistics), and Not needed yet otherwise.
When it is missing and needed, the Overview lists it under To fix, with Install WP Consent API.
The Google page shows it as Active or Not installed.
With Site Kit or WooCommerce, the Overview also warns when your current banner does not support WP Consent API, with the date this was checked and its source.

WooCommerce

When WooCommerce is active, the scan of the Cookies page also opens the shop, cart, checkout and account pages.

WooCommerce order attribution sets cookies whose names start with sbjs_. They serve marketing, so they must wait for the visitor’s choice. WooCommerce waits for it when it can read the choice through WP Consent API.

For the whole shop: Set up consent for an online shop.

With Cookie Rocks Pro

Cookie Rocks Pro registers itself with WP Consent API. It passes the visitor’s choice on every page view, before the page is ready, not only when the visitor clicks. So the choice stays right even when the cookies of WP Consent API have expired.

The five categories of WP Consent API follow the banner. functional is Necessary. preferences, statistics and marketing keep their names. statistics-anonymous follows Statistics, or Audience measurement when exempt audience measurement is on.
The consent type is opt-in, or opt-out in information mode. The event wp_consent_type_defined fires once the choice is passed.
The wp_consent_ cookies keep the choice as long as the Cookie Rocks cookie does, and the cookie policy lists them.
WP Statistics reads the choice through WP Consent API as long as no other consent integration is chosen in its settings. It then counts a visit only once statistics are accepted.

For site owners: Cookie Rocks for WP Consent API and Cookie Rocks for WooCommerce.

Next step: Caching plugins.

Cookie Rocks helps you find your way through cookie and privacy rules. It does not replace a lawyer’s advice.