What is genuinely necessary
WooCommerce can set cookies to hold the basket, keep a session coherent across checkout and remember recently viewed items. A basket or checkout cookie used only to provide the shopping flow a visitor requested will commonly fit the strictly-necessary exception; recently viewed and other convenience or measurement features need a separate purpose-specific assessment.
Conversion tags, remarketing pixels, analytics and behavioural abandoned-cart tracking are ordinarily optional. Review widgets and other store features must be classified by their actual purpose and loading behaviour rather than by the plugin name. On many stores these services arrive through a mix of plugins and a tag manager.
Conversion tags fire on a page a homepage scan never sees
Scan the order-received page
Purchase conversion tags fire once, on the thank-you page, after a real order. A scan of your homepage and a product page will report a clean store and miss the single highest-value tracking event on it. Include the checkout flow in your verification, or capture it as a HAR file from a real test order.
Setting it up
- 1
Install the plugin and pair the site
Same as any WordPress install.
- 2
Classify the WooCommerce cookies
Cart and session as necessary; anything analytical or promotional as optional.
- 3
Inventory conversion tags across each loader
Check the theme, the plugins, and any tag manager container for purchase events.
- 4
Verify through a test order
Complete a purchase with consent refused and confirm no conversion event fired.
Common questions
Do WooCommerce cart cookies need consent?
A cookie used only to hold the basket a visitor requested will commonly fit the strictly-necessary exception. Confirm the cookie does not also support analytics, profiling or an unrelated convenience, and check the rule in the visitor’s jurisdiction.
How do I test a conversion tag without a real order?
Most stores have a test payment mode. Failing that, place a real low-value order and refund it. The point is to reach the order-received page with a genuine order behind it.
Sources and verification
Verified on . Product-behaviour statements were checked against the current implementation and tests. The links below are the verification basis recorded for this article. They support the stated facts, not a legal conclusion for every site or configuration; recheck changing vendor behaviour before relying on it in production.
- WP Consent API project documentation
Official documentation
Checked
- StrongPrivacy documentation
Product documentation
Checked
See what your own site is loading
A browser scan reports the requests and storage it observed during the sampled journey. Use configured workspace scans to compare the states and pages that matter to your implementation.