Works with your stack
Cookie consent for Mailchimp on WordPress: forms, pixel, pop-ups and shops
sign-ups, not shadows
Mailchimp reaches a WordPress site in many ways: a sign-up form, a pop-up, the site pixel, a shop connection or a form plugin. Some only talk to Mailchimp when the visitor submits a form. Others load a tracker on the first page and keep a visitor ID in the browser for a year. Cookie Rocks Pro holds the trackers until consent and leaves plain sign-up forms working for everyone.

Mailchimp on WordPress, one by one
The ways Mailchimp gets into your pages
- Embedded sign-up form
- The form code you copy from Mailchimp loads a small checking script (mc-validate.js) and sends data only when the visitor submits. It stores nothing and works for everyone.
- Connected site script
- The script Mailchimp gives when you connect a site (chimpstatic.com/mcjs-connected). It can load the site pixel, the new pop-up and flyout forms, and ad features. It sends page views to Mailchimp from the first page.
- Pop-up and flyout forms
- Mailchimp's current pop-ups keep up to 19 keys in the browser, most for a year: a visitor ID, pages seen, forms seen and filled. Older pop-ups write a cookie when the visitor closes them.
- Mailchimp for WP
- MC4WP forms store nothing in the browser and send data from your server. Its optional Site Tracking adds the Mailchimp pixel to every page. The paid version can set four 14-day cookies to credit orders to emails.
- Mailchimp for WooCommerce
- Mailchimp for WooCommerce prints the connected site script and the pixel on every page of the shop. It also sets 28-day campaign cookies from your server when a visitor arrives from a Mailchimp email.
- Form plugins
- Contact Form 7, Fluent Forms, WPForms, Gravity Forms, Elementor Pro and Ninja Forms send entries to Mailchimp from your server after submission. Nothing loads in the page.
- Form builders for Mailchimp
- Mailchimp Forms by MailMunch loads its own tracker on every page. It keeps a visitor ID and a page count in the browser for a year.
What matters for consent with Mailchimp on WordPress
The pixel starts before any click
Mailchimp's site pixel stores a visitor ID with no expiry in the browser and reports every page view. After a sign-up, it can keep the subscriber's email address in the browser too.
Held wherever it comes from
Cookie Rocks Pro finds the connected site script whether you pasted it, or Mailchimp for WP or Mailchimp for WooCommerce added it. It waits for the choice, then starts on the same page.
Forms keep working
A plain sign-up form, and form plugins that send to Mailchimp from your server, need no consent to show. Visitors can always subscribe.
Nothing after a refusal
After Reject all, no request reaches Mailchimp from the pixel or the pop-ups, on the page and on the next ones.
Cookies from your server
Campaign cookies set by your server on the first page cannot be held by any banner. The free Audit lists them so you can decide what to keep.
What our tests found on Mailchimp on WordPress
Good to know · Mailchimp for WooCommerceCookie Rocks holds the Mailchimp for WooCommerce e-mail and cart cookies
The e-mail and cart cookies wait for marketing consent.
Seen in our tests, 13 November 2026, Mailchimp for WooCommerce 6.3.
Full detail
Cookie Rocks removes mailchimp_user_email, mailchimp_user_previous_email, mailchimp_cart_token and mailchimp.cart.previous_email until the visitor accepts marketing, and expires copies already in the browser after a refusal or a withdrawal. The small cookies.js test cookie, written and removed by the plugin itself, is left alone.
Before the choice · Mailchimp for WooCommerceMailchimp for WooCommerce campaign cookies now wait for consent
A visitor arriving from a Mailchimp email link (?mc_cid=&mc_eid=) on a shop with Mailchimp for WooCommerce 6.3 used to get mailchimp_campaign_id and mailchimp_email_id for 28 days from the server before the banner was answered (Cookie Rocks 2.11.6-beta.1). With Cookie Rocks 2.11.6, neither cookie is set before the choice nor after Reject all. Limit: a page served from a page cache.
Seen in our tests, 12 November 2026, Mailchimp for WooCommerce 6.3.
Before the choice · Mailchimp for WooCommerceMailchimp for WooCommerce: nothing reaches Mailchimp after a refusal
With Cookie Rocks 2.11.6 and Mailchimp for WooCommerce 6.3 connected to a real Mailchimp account, a shopper who clicks Reject all, adds a product and types an email at checkout sends nothing: no request to admin-ajax.php (mailchimp_set_user_by_email), no mailchimp.cart.current_email, mailchimp_user_email or mailchimp_cart_token, and no cart job for Mailchimp in the extension's queue. Mailchimp's own script stays held. After Accept all, the same steps set the three cookies and send the cart to Mailchimp.
Seen in our tests, 12 November 2026, Mailchimp for WooCommerce 6.3.
Before the choice · Elementor ProElementor Pro keeps counting page views after a refusal
When a site has at least one Elementor Pro pop-up template (drafts included), Elementor Pro writes the browser storage key 'elementor' on every page for every visitor: a page-view counter and a visit counter in localStorage, and a session flag in sessionStorage. In our test with Cookie Rocks 2.11.6 and its default settings, the key was written before the choice, and after Reject all the page-view counter kept rising on each page (1, 2, 3): nothing erased it.
Seen in our tests, 12 November 2026, Elementor Pro 3.29.2.
See the 45 other findings
Before the choice · Mailchimp connected siteMailchimp connected site script: held until consent, no reload after Accept
Without a consent tool, Mailchimp's connected site script (chimpstatic.com/mcjs-connected) loads the pixel or the sign-up forms on the first page and sends page views and form events to Mailchimp before any choice. Cookie Rocks Pro holds it, whether pasted in the page, printed by Mailchimp for WooCommerce or added by Mailchimp for WP. After Accept all it loads on the same page; after Reject all, no request reaches Mailchimp and nothing is stored, on the next page too.
Seen in our tests, 11 November 2026, Mailchimp connected site pixel 1.26.0 ; forms snippet 1.0.0 ; MC4WP 4.15.0 ; MC4WC 6.3.
Good to know · Mailchimp connected site (pixel)Mailchimp's pixel stores its visitor ID in local storage, not cookies
Mailchimp's site pixel (pixel-reporting-sdk 1.22.0 to 1.26.0, loaded by the connected site script) sets no cookie. It keeps a random visitor ID with no expiry in local storage (intuit_pixel_sdk_user_data), the visit in session storage (intuit_pixel_sdk_session_data, new visit after 30 minutes idle) and unsent events in an IndexedDB database (intuit_pixel_sdk_storage). Each page view goes to chimpstatic.com/pixel/v1/track. The cookies _mcid and _mcvid appear in no version of its code.
Seen in our tests, 11 November 2026, Mailchimp connected site (pixel) pixel-reporting-sdk 1.26.0.
Before the choice · Mailchimp for WPMailchimp for WP with a real account: the pixel waits, the email follows consent
With a real API key and Site Tracking on, Cookie Rocks Pro held the Mailchimp script added by Mailchimp for WP 4.15: nothing reached Mailchimp and nothing was stored before the choice, nor after Reject all. After Accept all, the pixel loaded without a reload. After a sign-up through the plugin's form, the plugin passed the address to the pixel, which stored it in clear in local storage and sent it to Mailchimp. No cookie was set by Mailchimp.
Seen in our tests, 11 November 2026, Mailchimp for WP 4.15.
Before the choice · Mailchimp for WPMailchimp for WP: the Site Tracking pixel waits
With Site Tracking on and a real Mailchimp pixel script, Mailchimp for WP 4.15.0 adds the script to every page. Cookie Rocks Pro holds it until consent and loads it after Accept all, without a reload; it then stores a visitor ID in local storage and sends page views to Mailchimp. After Reject all, nothing reaches Mailchimp and nothing is stored. After a sign-up, the plugin's script sends the subscriber's email to the pixel only once the pixel has loaded.
Seen in our tests, 11 November 2026, Mailchimp for WP 4.15.0.
Good to know · Mailchimp for WPMailchimp for WP registers the site in Mailchimp on its own
When Site Tracking is turned on with an API key, Mailchimp for WP 4.15 registers the site as a connected site in the Mailchimp account and adds its script to every page. The script stays empty until site tracking is also started in Mailchimp; then it loads Mailchimp's pixel. Turning the option on is not enough on its own, and turning it off in WordPress does not remove the connected site from Mailchimp.
Seen in our tests, 11 November 2026, Mailchimp for WP 4.15.
Before the choice · Mailchimp for WooCommerceMailchimp for WooCommerce sets campaign cookies even when not connected
A visitor who arrives with ?mc_cid= or ?mc_eid= in the address (links in Mailchimp emails) gets mailchimp_campaign_id and mailchimp_email_id for 28 days, set by PHP on the first page, even when the extension is not yet connected to a Mailchimp account. In our test they were there before the choice and stayed after Reject all. The extension asks the filter mailchimp_allowed_to_use_cookie before setting them; a site can return false there until consent.
Seen in our tests, 11 November 2026, Mailchimp for WooCommerce 6.3.
Before the choice · Mailchimp for WooCommerceBefore 2.11.6: the checkout email reached Mailchimp after a refusal
With Cookie Rocks 2.11.6-beta.1, a shopper who clicked Reject all and then typed an email at checkout still triggered Mailchimp for WooCommerce 6.3: its site script set mailchimp.cart.current_email and sent the address to admin-ajax.php (mailchimp_set_user_by_email); the server set mailchimp_user_email and mailchimp_cart_token for 28 days and sent the cart to Mailchimp, where the address appeared as a contact. Fixed in Cookie Rocks 2.11.6, which answers the extension's mailchimp_allowed_to_use_cookie filter, also during AJAX calls.
Seen in our tests, 11 November 2026, Mailchimp for WooCommerce 6.3.
Good to know · Connect Contact Form 7 to Mailchimp (Chimpmatic Lite)Contact Form 7 to Mailchimp (Chimpmatic Lite) adds nothing to the page
Connect Contact Form 7 to Mailchimp (Chimpmatic Lite 26.11.01.19) sends form entries to Mailchimp from the server after submission. In our test it added no script, request or storage to the page. The same holds for the Mailchimp links of form plugins that use Mailchimp's API from the server (Fluent Forms, code read; WPForms, Gravity Forms, Elementor Pro and Ninja Forms through paid add-ons, not tested).
Seen in our tests, 11 November 2026, Connect Contact Form 7 to Mailchimp (Chimpmatic Lite) 26.11.01.19.
Before the choice · Mailchimp Forms by MailMunchMailchimp Forms by MailMunch loads its tracker before the choice
Mailchimp Forms by MailMunch 3.3.1 prints MailMunch's script (a.mailmunch.co/app/v1/site.js) on every page once connected. It loads jQuery from ajax.googleapis.com, asks forms.mailmunch.co for a visitor ID and the visitor's country, and stores four keys for 365 days in local storage (cookies if local storage fails): _mailmunch_visitor_id, _mailmunch_lead_quality, mailmunch_pageview_count, mailmunch_second_pageview. Form events go to MailMunch with the visitor ID. Cookie Rocks 2.11.6-beta.1 does not hold it: all of this happened before the choice and after Reject all.
Seen in our tests, 11 November 2026, Mailchimp Forms by MailMunch 3.3.1.
Good to know · WooCommerceThe wc key of WooCommerce is a storage test
WooCommerce: wc is written then deleted at once (storage test), nothing stays.
Name Kept in Category What it is for wclocalStorage Necessary Checks that browser storage works, deleted at once wcsessionStorage Necessary Checks that browser storage works, deleted at once Read in the code of WooCommerce, 4 November 2026.
Full detail
WooCommerce cart fragments write wc = test in local and session storage and delete it in the same statement, to check that storage works. Nothing stays. The Audit 2.9.11 lists wc as an unknown key; a key written and deleted at once should not be listed.
Good to know · Drag and Drop Multiple File Upload for Contact Form 7What Drag and Drop Multiple File Upload for Contact Form 7 stores in browsers
Drag and Drop for CF7: dnd_wpcf7_session_id and dnd_cf7_token_* (necessary, 24 h, upload field only).
Name Kept in Category What it is for dnd_wpcf7_session_idlocalStorage Necessary Keeps the visitor's upload folder for the form, 24 hours dnd_cf7_token_*localStorage Necessary Keeps the token of the visitor's upload folder, 24 hours *_count_fileslocalStorage Necessary Counts the files added to the upload field Read in the code of Drag and Drop Multiple File Upload for Contact Form 7, 4 November 2026.
Full detail
On a page with its upload field, the plugin keeps in local storage dnd_wpcf7_session_id (a random upload folder and the time it was made), dnd_cf7_token_<folder> (a random token for that folder) and <field>_count_files. It deletes the folder and token after 24 hours. They let the visitor's files reach the form; nothing is sent elsewhere. The Audit 2.9.11 shows the observed dnd_cf7_token_<uuid> under the site's own name as an identifier to check, although the same plugin's code pattern dnd_cf7_token_* is in its list.
Good to know · WooCommerceWhat WooCommerce stores in visitors' browsers
WooCommerce: 11 cookie(s) or browser key(s) for visitors, recognised by Cookie Rocks from 2.9.8.
Name Kept in Category What it is for WOOCOMMERCE_CHECKOUT_IS_CUSTOMER_DATA_DIRTYlocalStorage Necessary Keeps the shopping cart and the checkout working storeApiCartHashlocalStorage Necessary Keeps the shopping cart and the checkout working storeApiNoncelocalStorage Necessary Keeps the shopping cart and the checkout working wc_cart_createdsessionStorage Necessary Keeps the shopping cart and the checkout working woocommerce_geo_hashcookie Necessary Serves the cached page that matches the visitor's country (taxes, shipping) woo-sharecookie Necessary Lets a visitor with a share link see a store that is not launched yet tk_aicookie Statistics Anonymous identifier for WooCommerce usage statistics (Automattic Tracks) tk_lrcookie Statistics Automattic Tracks usage statistics (referrer) tk_orcookie Statistics Automattic Tracks usage statistics (original referrer) tk_r3dcookie Statistics Automattic Tracks usage statistics tk_tccookie Statistics Automattic Tracks usage statistics (session) Read in the code of WooCommerce, 2 November 2026.
Full detail
WooCommerce can store 11 cookies or browser keys for visitors: WOOCOMMERCE_CHECKOUT_IS_CUSTOMER_DATA_DIRTY, storeApiCartHash, storeApiNonce, wc_cart_created, woocommerce_geo_hash, woo-share, tk_ai, tk_lr, tk_or, tk_r3d, tk_tc. Cookie Rocks recognises them from 2.9.8 and lists them in the cookie policy, each with its category and purpose, when it sees them.
Good to know · Fluent FormsWhat Fluent Forms stores in visitors' browsers
Fluent Forms: 1 cookie(s) or browser key(s) for visitors, recognised by Cookie Rocks from 2.9.8.
Name Kept in Category What it is for ff_nominatim_geocode_cachelocalStorage Necessary Keeps the address lookups of a conversational form Read in the code of Fluent Forms, 2 November 2026.
Full detail
Fluent Forms can store these in a visitor's browser: ff_nominatim_geocode_cache (localStorage, necessary: Keeps the address lookups of a conversational form). Cookie Rocks recognises them from 2.9.8, with this category and purpose, and lists them in the cookie policy when it sees them.
Good to know · Elementor ProWhat Elementor Pro stores in visitors' browsers
Elementor Pro: 3 cookie(s) or browser key(s) for visitors, recognised by Cookie Rocks from 2.9.8.
Name Kept in Category What it is for popup-*-impressions-countsessionStorage Preferences Remembers which pop-ups the visitor has seen, to show them only as often as set *-evergreen_due_datelocalStorage Preferences Keeps the end time of a countdown for this visitor *-evergreen_intervallocalStorage Preferences Keeps the end time of a countdown for this visitor Read in the code of Elementor Pro, 2 November 2026.
Full detail
Elementor Pro can store these in a visitor's browser: popup-*-impressions-count (session, preferences: Remembers which pop-ups the visitor has seen, to show them only as often as set); *-evergreen_due_date (local, preferences: Keeps the end time of a countdown for this visitor); *-evergreen_interval (local, preferences: Keeps the end time of a countdown for this visitor). Cookie Rocks recognises them from 2.9.8, with this category and purpose, and lists them in the cookie policy when it sees them.
Good to know · About Cookie RocksCookie Rocks 2.9.5 tested on PHP, WooCommerce and multisite
- No PHP error on PHP 7.4 and 8.3.
- WooCommerce cart and checkout work before and after the choice.
- Multisite: settings, choice cookie and tables per site.
- Uninstall removes options, tables, task and files.
Seen in our tests, 1 November 2026, Cookie Rocks.
Full detail
Cookie Rocks 2.9.5 with the Audit and Pro showed no PHP error on PHP 7.4 and 8.3. On WooCommerce, cart and checkout work before and after the choice, and strict payments keep Stripe out of other pages only. On a multisite network, settings, the choice cookie (cr_consent_2) and tables are per site, including sites created later. Uninstall removes options, tables, the scheduled task and files.
Good to knowCookie Rocks lists Wordfence, Forminator, WP WhatsApp and WPForms Pro cookies
- Each appears in its cookie list with its purpose.
- Wordfence: wfCBLBypass, wf_loginalerted_*, wfls-remembered-*.
- Forminator: poll-cookie-*, forminator_stripe_payment_owner.
- WP WhatsApp: nta-wa-gdpr. WPForms Pro: _wpfuuid.
Read in the code, 18 October 2026.
Full detail
Cookie Rocks lists the site cookies of Wordfence (wfCBLBypass, wf_loginalerted_*, wfls-remembered-*), Forminator (poll-cookie-*, forminator_stripe_payment_owner), WP WhatsApp (nta-wa-gdpr) and WPForms Pro (_wpfuuid) in the cookie list it writes, with their purpose.
Good to know · Contact Form 7, WPForms Lite, Forminator, Fluent Forms, Ninja FormsFive form plugins set nothing on a default home page
by default: Default settings
With default settings and no form on the page, Contact Form 7, WPForms Lite, Forminator, Fluent Forms and Ninja Forms set no cookie, store nothing and load no known third-party tool.
Seen in our tests, 17 October 2026, Contact Form 7, WPForms Lite, Forminator, Fluent Forms, Ninja Forms 6.2.2, 2.0.2.2, 1.58.2, 6.2.16, 3.15.6.
Full detail
On a fresh WordPress home page with default settings, Contact Form 7, WPForms Lite, Forminator, Fluent Forms and Ninja Forms set no cookie, keep nothing in the browser's storage and load no known third-party tool, before or after Accept all (no form or captcha placed on the page).
Good to know · MC4WP: Mailchimp for WordPressMC4WP Mailchimp forms set no cookie and store nothing in the browser
The forms work on cached pages. Form data is sent to Mailchimp by the server when the form is submitted.
Read in the code of MC4WP: Mailchimp for WordPress 4.14.1, 16 October 2026.
Full detail
MC4WP: Mailchimp for WordPress 4.14.1 contains no setcookie, document.cookie, localStorage, sessionStorage, IndexedDB, WP Consent API or gtag('consent') code (outside minified and vendor files). Forms use a timestamp field accepted for 90 days instead of a nonce, so they work on cached pages. Form data is sent to Mailchimp by the server on submission.
A setting to know · MC4WP: Mailchimp for WordPressMC4WP's tracking pixel loads on every page with no wait for consent
setting “Enable Site Tracking” · by default: off
Off by default. After a sign-up, the email is sent to Mailchimp only if the pixel is already loaded, so it is lost if the pixel is held and accepted later on that page.
Read in the code of MC4WP: Mailchimp for WordPress 4.14.1, 16 October 2026.
Full detail
MC4WP's Site Tracking Pixel (off by default) enqueues Mailchimp's script chimpstatic.com/mcjs-connected/js/users/<id>.js (handle mc4wp-mailchimp-site-tracking-pixel, defer) on every public page, with no setting to wait for consent. After a sign-up, an inline footer script calls $mcSite.pixel.api.identify with the subscriber's email only if the pixel is already loaded, so it is lost if the pixel is held and accepted later on the same page.
From your server · Mailchimp for WooCommerceMailchimp for WooCommerce sends the typed email to the site before any order
setting “Cart tracking” · by default: all
With cart tracking on (the default), leaving the email field sets mailchimp.cart.current_email and sends the address to the site. The server then passes cart data to Mailchimp.
Read in the code of Mailchimp for WooCommerce 6.3, 16 October 2026.
Full detail
With cart tracking on (all, by default), Mailchimp for WooCommerce's site script sets the session cookie mailchimp.cart.current_email when the visitor leaves the email field at checkout, login or registration, then sends the address to admin-ajax.php?action=mailchimp_set_user_by_email, before any order. The server then passes cart data to Mailchimp's API.
From your server · Mailchimp for WooCommerceMailchimp for WooCommerce sets 28-day cookies that banners cannot hold
- mailchimp_campaign_id and mailchimp_email_id when the visitor arrives with ?mc_cid= or ?mc_eid=.
- mailchimp_user_email, mailchimp_user_previous_email and mailchimp_cart_token for cart recovery.
- mailchimp_landing_site on the first page, only if landing page tracking is on (off by default).
- All go through the mailchimp_allowed_to_use_cookie filter.
Read in the code of Mailchimp for WooCommerce 6.3, 16 October 2026.
Full detail
Mailchimp for WooCommerce sets its cookies from PHP for 28 days (2 419 200 s, Secure, SameSite=Strict): mailchimp_campaign_id and mailchimp_email_id when a visitor arrives with ?mc_cid= or ?mc_eid=, mailchimp_user_email, mailchimp_user_previous_email and mailchimp_cart_token (HttpOnly) for cart recovery, and mailchimp_landing_site on the first page only if landing page tracking is on (off by default). A consent plugin cannot hold them; all go through the mailchimp_allowed_to_use_cookie filter.
Before the choice · Mailchimp for WooCommerceMailchimp for WooCommerce loads Mailchimp scripts on every page by default
setting “Mailchimp script” · by default: on
Mailchimp's site snippet and pixel load on every page, and a logged-in customer's email is written into the page for identification. No WP Consent API or Google consent code.
Read in the code of Mailchimp for WooCommerce 6.3, 16 October 2026.
Full detail
Mailchimp for WooCommerce prints Mailchimp's connected-site snippet (chimpstatic.com/mcjs-connected) inline in wp_footer on every page by default (option mailchimp-woocommerce-code-snippet, filter mailchimp_add_inline_footer_script). The Mailchimp pixel scripts are enqueued on every page unless MAILCHIMP_PIXEL_ENABLED is false, and the logged-in customer's email is written into window.mcPixel for identification. No WP Consent API or Consent Mode code.
A setting to know · Microsoft ClarityClarity's Brand Agents loads a Microsoft script and sets a cookie on stores
setting “Brand Agents” · by default: not connected
With Brand Agents connected and front-end injection on, a script loads from an Azure address on every front page for visitors not logged in. On WooCommerce stores, brandagent_attrs is set for 2 hours.
Read in the code of Microsoft Clarity 0.10.35, 16 October 2026.
Full detail
With Brand Agents connected and front-end injection on, the Microsoft Clarity plugin loads a script module from adsagentclientafd-b7hqhjdrf3fpeqh2.b01.azurefd.net on every front page for visitors who are not logged in. On WooCommerce stores, a REST endpoint called by that script sets the brandagent_attrs cookie for 2 hours (session, customer and conversation IDs, Clarity data, language, currency, country).
Good to know · JetpackWooCommerce Analytics assumes consent when WP Consent API is missing
It checks for statistics consent before each event. Without WP Consent API, its requests to pixel.wp.com and stats.wp.com are sent for every visitor.
Read in the code of Jetpack 16.3.1, 16 October 2026.
Full detail
WooCommerce Analytics (Jetpack module, on with WooCommerce) checks wp_has_consent('statistics') before each event, on the server and in the browser. Without WP Consent API, consent is assumed and pixel.wp.com/t.gif and stats.wp.com/s-*.js are sent for every visitor.
Before the choice · KlaviyoKlaviyo sends checkout details to Klaviyo even when its addresses are held
On the WooCommerce checkout, scripts served by the site set __kla_id (email and name, 2 years) and send profile data when the email or name is typed, or on load for logged-in customers.
Read in the code of Klaviyo 3.8.3, 16 October 2026.
Full detail
On the WooCommerce checkout, wck-started-checkout.js (classic) and includes/blocks/build/events.js (block checkout), both served by the site, set the __kla_id cookie (base64 of email, first and last name, 2 years) and POST profile and Started Checkout data to a.klaviyo.com/client/profiles/ and client/events/ without klaviyo.js: on load for a logged-in customer, otherwise when the email or name is typed. Holding Klaviyo's own addresses does not stop them.
From your server · KlaviyoKlaviyo's server sends Added to Cart events while __kla_id exists
Without the cookie nothing is sent, so removing __kla_id on withdrawal stops it.
Read in the code of Klaviyo 3.8.3, 16 October 2026.
Full detail
When a product is added to the cart and the __kla_id cookie is present, the Klaviyo plugin's server sends an Added to Cart event to a.klaviyo.com/client/events/ (wp_remote_post). Without the cookie nothing is sent, so removing __kla_id on withdrawal stops it.
From your server · Matomo for WordPressMatomo for WordPress sends WooCommerce carts and orders from the server
setting “Track ecommerce” · by default: on
With Track ecommerce on (default), carts and orders are sent from PHP in some cases, with no consent check. A browser-side consent signal does not hold these hits. The server tracker sets no cookie.
Read in the code of Matomo for WordPress 5.13.1, 16 October 2026.
Full detail
With Track ecommerce on (default), Matomo for WordPress sends WooCommerce carts and orders from PHP during AJAX or REST requests, in Tag Manager mode, or with MATOMO_TRACK_ECOMMERCE_SERVER_SIDE, with no consent check in that code; the PHP tracker sets no cookie but reads _pk_id. A browser-side consent signal does not hold these hits. Use server generated Visitor ID (off by default) starts the WooCommerce session for visitors without _pk_id.
From your server · OptinMonsterOptinMonster sends order revenue from the server using the _omra cookie
setting “Revenue Attribution”
With Revenue Attribution on, OptinMonster's server reads the _omra cookie at a WooCommerce or EDD order and sends the revenue to the OptinMonster API (v2/revenue). If _omra survives a refusal, sending continues.
Read in the code of OptinMonster 2.17.1, 16 October 2026.
Good to know · WooCommerceWooCommerce writes one visitor's marketing consent into cached pages
With WP Consent API, the attribution consent value is in the page, so a cached page carries it for everyone until a footer script corrects it. Session and cart storage do not depend on consent.
Read in the code of WooCommerce 11.2.1, 16 October 2026.
Full detail
With WP Consent API, WooCommerce writes the result of wp_has_consent('marketing'), read from the request's cookies, into the page as the attribution allowTracking value, so a cached page carries the value of the visitor who generated it. Its footer script wp-consent-api-integration corrects it only at the wp_consent_type_defined event and on each consent change. Only order attribution reads consent; the session cookie wp_woocommerce_session_<hash> (HttpOnly, 2 days, 7 when logged in) and the cart fragments storage (wc_cart_hash_<md5> in localStorage, wc_fragments_<md5> in sessionStorage) do not depend on it.
From your server · WooCommerceWooCommerce geolocation can send the visitor's IP to an outside lookup site
setting “Default customer location”
When it needs the country and no MaxMind key or CDN header gives it, the server asks ipinfo.io or api.country.is. With page caching support, woocommerce_geo_hash is set for 1 hour.
Read in the code of WooCommerce 11.2.1, 16 October 2026.
Full detail
When WooCommerce needs the visitor's country (default customer location set to Geolocate, or taxes by geolocation) and neither a MaxMind key nor a CDN country header gives it, its server looks the country up at ipinfo.io or api.country.is, sending the visitor's IP address. With Geolocate (with page caching support), it sets woocommerce_geo_hash for 1 hour from the first page and adds a v= parameter to addresses.
Good to know · WooCommerceWooCommerce attribution cookies are session cookies, except sbjs_session
sbjs_session lasts 30 minutes. The cookies are set on the domain without www., while WooCommerce's removal on withdrawal uses the full host name.
Read in the code of WooCommerce 11.2.1, 16 October 2026.
Full detail
WooCommerce passes a lifetime of 0.00001 month to its sourcebuster library, which converts and truncates it to 0 minutes: the sbjs_ attribution cookies are session cookies, except sbjs_session (30 minutes). sourcebuster sets them on the host name without www. (domain=.<domain>), while WooCommerce's own removal on withdrawal uses domain=.<hostname>.
Before the choice · Contact Form 7Contact Form 7 loads reCAPTCHA on every page, not only form pages
Once keys are saved, reCAPTCHA runs on each page load. Turnstile also loads on every page, and Stripe wherever CF7 scripts load. A filter can switch reCAPTCHA to www.recaptcha.net.
Read in the code of Contact Form 7 6.2.2, 16 October 2026.
Full detail
Once reCAPTCHA keys are saved, Contact Form 7 enqueues google-recaptcha (api.js?render=) and wpcf7-recaptcha on every page, not only pages with a form, and calls grecaptcha.execute on each page load. Turnstile (challenges.cloudflare.com/turnstile/v0/api.js) also loads on every page once its keys are saved, and js.stripe.com/v3/ wherever CF7 scripts load when Stripe is set up. The filter wpcf7_use_recaptcha_net switches reCAPTCHA to www.recaptcha.net.
Good to know · Contact Form 7Cookie Rocks asks for reCAPTCHA permission above Contact Form 7 forms
Sending waits until reCAPTCHA is allowed, the page reloads without losing what was typed, and reCAPTCHA loads from recaptcha.net. A setting can treat it as necessary.
Read in the code of Contact Form 7 6.2.2, 16 October 2026.
Full detail
On Contact Form 7 forms protected by reCAPTCHA, Cookie Rocks shows a permission request above the form, holds the send until reCAPTCHA is allowed, reloads without losing what was typed, and loads reCAPTCHA from recaptcha.net. A setting can treat reCAPTCHA as necessary.
Good to know · Contact Form 7Contact Form 7 sets no cookie and contacts no other site by default
Other sites are contacted only when reCAPTCHA, Turnstile, Akismet, Stripe or a mailing tool is on. A submission records time, IP address, port, browser and page address.
Read in the code of Contact Form 7 6.2.2, 16 October 2026.
Full detail
Contact Form 7 reads and sets no cookie and sends nothing to other sites unless reCAPTCHA, Turnstile, Akismet, Stripe or a mailing tool is turned on. A submission records timestamp, IP address, port, user agent and page URL. The nonce is added only for logged-in users, so a cached form page stays valid for visitors. It does not use WP Consent API.
Good to know · Contact Form 7Without reCAPTCHA loaded, Contact Form 7 files messages as spam
The form is then sent without a token, filed as spam and no e-mail is sent. An empty Turnstile token is also treated as spam.
Read in the code of Contact Form 7 6.2.2, 16 October 2026.
Full detail
If grecaptcha is missing, Contact Form 7's wpcf7-recaptcha script stops with an error before it wraps the submit, so the form is sent without a token and CF7 files it as spam ('reCAPTCHA response token is empty.') and sends no email. An empty Turnstile token is also treated as spam.
Before the choice · WPForms LiteWPForms loads its captcha only on pages with a form that uses it
It loads reCAPTCHA, hCaptcha or Turnstile in the footer of those pages only. Its No-Conflict mode removes other captcha scripts, but not those from recaptcha.net.
Read in the code of WPForms Lite 2.0.2.2, 16 October 2026.
Full detail
WPForms loads its captcha only on pages that show a form using it, in the footer: reCAPTCHA (www.google.com/recaptcha/api.js), hCaptcha (hcaptcha.com/1/api.js) or Turnstile (challenges.cloudflare.com); the address can be changed with the wpforms_frontend_captcha_api filter. Its No-Conflict mode dequeues other scripts from google.com/recaptcha, gstatic.com/recaptcha and hcaptcha.com/1, but not recaptcha.net. It sends a Permissions-Policy header for private state tokens on every request.
Good to know · WPForms LiteWPForms Lite sets no cookie for visitors
Lite does not write its _wpfuuid cookie unless a consent function allows it. Form analytics send views to the site itself, with no cookie or storage. It does not use WP Consent API.
Read in the code of WPForms Lite 2.0.2.2, 16 October 2026.
Full detail
WPForms Lite sets no cookie for visitors: its front script writes _wpfuuid (random ID, 3,999 days, SameSite=Strict) only if uuid_cookie is true, which Lite hardcodes to false, or if a wpforms.hasRequiredConsent JavaScript function exists and returns true. Form analytics (2.0) send form-view data to the site's own admin-ajax.php by sendBeacon, with an in-memory session ID, no cookie or storage, and skip authors, editors and administrators. It does not use WP Consent API.
Good to know · WooCommerceWooCommerce order attribution starts on the page where the visitor accepts
A visitor who lands from a campaign link and accepts on a later page is recorded as a direct visit.
Seen in our tests, 15 October 2026, WooCommerce 11.2.1.
Full detail
When order attribution waits for consent, it starts on the page where the visitor accepts. A visitor who lands from a campaign link and accepts on a later page is recorded as a direct visit. This respects the choice, but shops that follow their campaigns should know it.
Good to know · WooCommerceWooCommerce block cart and checkout use the browser's local storage
They keep storeApiNonce, storeApiCartData and storeApiCartHash, plus one more key on the checkout page. The classic checkout keeps nothing there.
Seen in our tests, 15 October 2026, WooCommerce 11.2.1.
Full detail
The WooCommerce block cart and block checkout keep storeApiNonce, storeApiCartData and storeApiCartHash in the browser's local storage, plus WOOCOMMERCE_CHECKOUT_IS_CUSTOMER_DATA_DIRTY on the checkout page. The classic checkout keeps nothing in local storage.
Before the choice · WooCommerceWooCommerce cart cookies are necessary and never held
by default: Default settings
Browsing sets no cookie. Adding a product sets woocommerce_items_in_cart, woocommerce_cart_hash and wp_woocommerce_session_* before any choice; they keep the cart.
Seen in our tests, 15 October 2026, WooCommerce 11.2.1.
Full detail
Browsing a WooCommerce shop sets no cookie. Adding a product to the cart sets woocommerce_items_in_cart, woocommerce_cart_hash and wp_woocommerce_session_* before any choice. They keep the cart, so they are necessary cookies and Cookie Rocks never holds them.
Good to know · WooCommerceWooCommerce checkout works after Reject all or Accept all
With Cookie Rocks, orders go through with the WooCommerce block checkout and the classic checkout alike, after Reject all or Accept all, with no error and no request to another site.
Seen in our tests, 15 October 2026, WooCommerce 11.2.1.
Good to know · WooCommerceWith Cookie Rocks, WooCommerce order attribution waits for marketing consent
After Reject all, an order goes through with no origin data; after Accept all, it has it. Withdrawing marketing consent deletes the sbjs_ cookies at once.
Seen in our tests, 15 October 2026, WooCommerce 11.2.1.
Full detail
With Cookie Rocks, WooCommerce order attribution (the sbjs_ cookies) waits for consent to marketing, with or without WP Consent API. After Reject all, a cash on delivery order goes through and carries no origin data; after Accept all, it does. Withdrawing marketing consent deletes the sbjs_ cookies at once.
Good to know · WooCommerceCookie Rocks is not flagged as incompatible with WooCommerce order storage
setting “HPOS”
With WooCommerce's order storage (HPOS) on, WooCommerce only judges extensions that declare they target WooCommerce: Cookie Rocks, which declares nothing, is not listed as incompatible, and no declaration is needed.
Seen in our tests, 10 October 2026, WooCommerce.
Before the choice · WooCommerceWooCommerce order attribution sets seven cookies on arrival, before any choice
setting “Order attribution” · by default: on
Without a consent integration, the sbjs_ cookies are set as soon as the visitor arrives and stay after a refusal.
Seen in our tests, 9 October 2026, WooCommerce 11.2.
Full detail
Without a consent integration, WooCommerce order attribution sets seven sbjs_ cookies (sbjs_migrations, sbjs_current_add, sbjs_first_add, sbjs_current, sbjs_first, sbjs_udata, sbjs_session) as soon as the visitor arrives, before any choice, and they stay after a refusal.
Newsletters and popups
Other plugins of the same kind.
Questions
Do Mailchimp sign-up forms need consent?
A plain sign-up form sends data only when the visitor subscribes, which is their own action. Pop-ups and the site pixel follow visitors across pages, so they wait for consent.
Does Mailchimp set the cookies _mcid and _mcvid on my site?
Not today. The current Mailchimp pixel keeps its visitor ID in the browser's local storage, not in cookies. Cookie Rocks lists what Mailchimp really stores, from its code and our tests.
Will my pop-up still show?
Yes, once the visitor accepts. Until then, the pop-up waits with the rest of Mailchimp tracking. Your embedded form stays visible for everyone.
What happens after the 30-day trial?
The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.
For sites with Mailchimp
Your forms stay open, the tracking waits for the choice.
subscribers keep subscribing
Every feature of the complete plugin for 30 days, no card. Your forms and pop-ups keep their place.
- During the trial: everything, including the full settings and the scans
- After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
- What waits for a key: most settings, updates and support

Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.