Works with your stack

Cookie consent for Jetpack

many modules, many servers

Jetpack is a bundle of modules, and many of them load from WordPress.com. Stats counts every visit by default. Comments, likes, videos, fonts and images can come from other servers before the visitor chooses.

By Automattic · jetpack.com · WordPress.org

Tested with Jetpack Stats 16.4: its script and pixel wait for Accept, then load with no reload. Nothing is sent after a refusal. Cookie Rocks 2.10.0, 6 November 2026

Is this your product? Tell us if anything here is out of date. Write to us

Start your free trial

Get the free audit

Jetpack

WordPress plugin

Tested

Tested version: 16.4
How: Tested automatically around each Cookie Rocks version
Last test: 7 November 2026
Latest version: 16.4 tested
Active installs: 3,000,000+

See it on WordPress.org

What Jetpack adds to your visitors’ browser

Not testable without an account: Jetpack Stats needs a WordPress.com connection.

What matters for consent with Jetpack

Stats count by default

Jetpack Stats loads on every page view. It waits for consent only if a hidden option is switched on, with no switch in the dashboard. Then it asks the WP Consent API for statistics consent.

Modules from other servers

Comments, Likes, VideoPress, the fonts module and the image accelerator load from WordPress.com or Google servers, without reading any consent signal. See fonts for that part.

Jetpack’s own banner

Jetpack’s Cookie Consent block has a single button. It does not pass the choice to the WP Consent API, so other plugins do not see it.

WooCommerce Analytics

On shops, this module checks the WP Consent API before each event. Without it, consent is assumed and every visitor is counted.

Cookie Rocks with Jetpack

Warns when WP Consent API is missing, with a link to install it: this plugin expects to read the visitor’s choice there.

What the Audit checks

What our tests found on Jetpack

Set before the choice · Cookie RocksCookie Rocks holds Jetpack Stats 16.4 until the visitor accepts
Script and pixel wait for Accept, no reload is needed, and nothing is sent after Refuse.
Seen in our tests, 5 November 2026, Cookie Rocks.
Full detail
Cookie Rocks 2.10.0 holds both the Jetpack Stats 16.4 script and its inline code before any choice, with or without WP Consent API. After Accept, the script loads and the pixel is sent without a page reload. After Refuse, nothing goes to stats.wp.com or pixel.wp.com.
Depends on a setting · JetpackJetpack Stats 16.4 waits for WP Consent API, but its script still loads first
The pixel waits for statistics consent; the script from stats.wp.com loads before the choice. Without WP Consent API nothing waits.
Seen in our tests, 5 November 2026, Jetpack 16.4.
Full detail
Since Jetpack 16.4 the honor_cookie_consent option is gone. With the WP Consent API plugin active, Jetpack Stats sends its pixel (pixel.wp.com/g.gif) only once wp_has_consent('statistics') allows it, and listens for a change of consent. Its script stats.wp.com/e-*.js still loads before any choice. Without the WP Consent API plugin, Stats counts every page view as before.
Set before the choice · JetpackWP Consent API alone does not make Jetpack Stats 16.4 wait
With no banner on the site, the script and the pixel both go out on the first page view.
Seen in our tests, 5 November 2026, Jetpack 16.4.
Full detail
With the WP Consent API plugin active but no consent banner on the site, Jetpack Stats 16.4 still loads its script and sends its pixel on the first page view: nothing refuses, so the gate lets it through. Installing WP Consent API alone does not make Stats wait.

Good to know · JetpackWhat Jetpack stores in visitors' browsers

Jetpack: 21 cookie(s) or browser key(s) for visitors, recognised by Cookie Rocks from 2.9.8.

Name	Kept in	Category	What it is for
`eucookielaw`	cookie	Necessary	Remembers the visitor's choice on the Jetpack cookie banner
`personalized-ads-consent`	cookie	Necessary	Remembers the visitor's choice on the Jetpack cookie banner
`tk_ai`	cookie	Statistics	Anonymous identifier for Jetpack and WooCommerce usage statistics (Automattic Tracks)
`wp-jp-premium-content-session`	cookie	Necessary	Gives a subscriber access to paid or subscriber-only content
`jetpack-subscription-modal-on-comment-scroll-to`	localStorage	Preferences	Limits how often the subscription pop-up is shown to the visitor
`jetpack-subscription-modal-shown-count`	sessionStorage	Preferences	Limits how often the subscription pop-up is shown to the visitor
`jetpack_blog_subscribe_*`	cookie	Necessary	Shows the visitor the result of a subscription
`jetpack_comments_subscribe_*`	cookie	Necessary	Shows the visitor the result of a subscription
`jpp_math_pass`	cookie	Necessary	Remembers that the visitor solved the anti-robot sum on the login form
`verbum-wp-postpass`	cookie	Necessary	Lets the visitor comment on a password-protected post
`jetpack_sso_nonce`	cookie	Necessary	Keeps the sign-in with WordPress.com going
`jetpack_sso_original_request`	cookie	Necessary	Keeps the sign-in with WordPress.com going
`jetpack_sso_redirect_to`	cookie	Necessary	Keeps the sign-in with WordPress.com going
`jetpack_sso_wpcom_gravatar_*`	cookie	Necessary	Keeps the sign-in with WordPress.com going
`jetpack_sso_wpcom_name_*`	cookie	Necessary	Keeps the sign-in with WordPress.com going
`jetpack_sso_wpcom_referrer`	cookie	Necessary	Keeps the sign-in with WordPress.com going
`tk_lr`	cookie	Statistics	Automattic Tracks usage statistics (referrer)
`tk_or`	cookie	Statistics	Automattic Tracks usage statistics (original referrer)
`tk_r3d`	cookie	Statistics	Automattic Tracks usage statistics
`tk_tc`	cookie	Statistics	Automattic Tracks usage statistics (session)
`devicePixelRatio`	cookie	Preferences	Serves images sized for the visitor's screen

Read in its code, 2 November 2026, Jetpack.

Full detail

Jetpack can store 21 cookies or browser keys for visitors: eucookielaw, personalized-ads-consent, tk_ai, wp-jp-premium-content-session, jetpack-subscription-modal-on-comment-scroll-to, jetpack-subscription-modal-shown-count, jetpack_blog_subscribe_*, jetpack_comments_subscribe_*, jpp_math_pass, verbum-wp-postpass, jetpack_sso_nonce, jetpack_sso_original_request, jetpack_sso_redirect_to, jetpack_sso_wpcom_gravatar_*, jetpack_sso_wpcom_name_*, jetpack_sso_wpcom_referrer, tk_lr, tk_or, tk_r3d, tk_tc, devicePixelRatio. 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.

Set before the choice · JetpackSeveral Jetpack modules contact WordPress.com without any consent check
- Comments (jetpack.wordpress.com), Likes (widgets.wp.com) and VideoPress (videopress.com).
- Google Fonts module: fonts.gstatic.com. Site Accelerator: images from i0.wp.com.
- Jetpack's own visitor cookies are set only after an action.
Read in its code, 16 October 2026, Jetpack 16.3.1.
Full detail
Several Jetpack modules contact WordPress.com without reading any consent signal: Comments loads an iframe from jetpack.wordpress.com, Likes from widgets.wp.com, VideoPress from videopress.com, the Google Fonts module loads from fonts.gstatic.com, and Site Accelerator serves images from i0.wp.com. Jetpack's own visitor cookies (comment_author_*, jetpack_*_subscribe_*, jpp_math_pass) are set only after an action.
Good to know · JetpackJetpack's Cookie Consent block does not pass the choice to WP Consent API
Its single button only sets eucookielaw. With WordAds' own consent tool on, euconsent-v2 is set for 1 year and the Jetpack banner is turned off.
Read in its code, 16 October 2026, Jetpack 16.3.1.
Full detail
Jetpack's Cookie Consent block has a single button that only sets eucookielaw and fires eucookielaw-dismissed; it never calls wp_set_consent. With wordads_cmp_enabled, WordAds loads its own IAB consent tool, sets euconsent-v2 (1 year, server-side through admin-ajax) and disables the Jetpack banner. No gtag('consent') call was found.
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 its code, 16 October 2026, Jetpack 16.3.1.
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.

How we test it

Around each version, with its latest release

Around each Cookie Rocks version, a fresh WordPress installs its latest version from WordPress.org next to Cookie Rocks and runs the same checks. A new version joins the next run on its own.

Jetpack 16.4, tested on 7 November 2026.
The banner shows, the trackers of the test page wait for consent and load after it, and Cookie Rocks raises no PHP error.
Settings of the test: Default settings after activation.
Last run: Jetpack 16.4 on 7 November 2026, with WordPress 7.1.4.

Analytics and ad pixels

Other plugins of the same kind.

Meta Pixel for WordPressThe Meta pixel, plus Meta cookies sent from your server.tested 5.2.2Adds: Meta Pixel Meta for WooCommercePixel and server events, with a hold switch for consent.tested 3.7.8 Pixel CaffeineThe Meta pixel on every page, with no consent setting.tested 2.3.3Adds: Meta Pixel TikTok for BusinessThe TikTok pixel held, server events to decide.tested 1.4.3Adds: TikTok Pixel Microsoft ClarityClarity on every page, with no consent signal.tested 0.10.37 HotjarHotjar held until the visitor agrees.tested 1.0.16 HubSpotHubSpot’s loader on every page, consent only in HubSpot.tested 11.3.75 Ad pixel pluginsMeta and TikTok pixels, and what your server sends.MatomoStatistics from your own site, consent through Matomo’s API.tested 5.13.1 Koko AnalyticsStatistics on your own site, with a cookie by default.tested 2.5.3 Independent AnalyticsNo cookie, but returning visitors are still recognised.tested 2.16.2 Burst StatisticsWaits for statistics consent when WP Consent API is there.tested 3.7.4 SlimStat AnalyticsNo consent check by default; one setting changes that.tested 6.0.0Adds: Slimstat Analytics Statistics on your own siteStatistics plugins that count on your own server.Pixel ManagerUp to ten shop pixels from one script, held until the visitor agrees.tested 1.72.0 Plausible AnalyticsStatistics with no cookie, from plausible.io or your own site.tested 2.6.4 Fathom AnalyticsStatistics with no cookie, from cdn.usefathom.com.PixelYourSiteMeta and Google tags, plus first-party cookies of its own.tested 11.4.5Adds: Google Tag Manager, Google Analytics / Google Ads (gtag.js), Meta Pixel WP StatisticsVisitor counts on your own server, without cookies.tested 14.16.18

Every plugin and theme we test →

Questions

Which Jetpack modules should I check?

Stats, Comments, Likes, VideoPress, the fonts module and the image accelerator. Switch off the ones you do not need. Cookie Rocks holds known trackers until consent.

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 Jetpack users

One choice for every module.

stats after a yes

Every feature of the complete plugin for 30 days, no card.

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

How the trial works, in detail

Get your trial key

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