Skip to content

Works with your stack

Cookie consent for Burst Statistics

waits if the api is there

← Cookie Rocks for your stack

Burst Statistics counts visits on your own site. By default it recognises visitors with a cookie, set once tracking is allowed. With WP Consent API on the site, it waits for statistics consent in every mode. Without it, it tracks at once.

By Burst Statistics · burst-statistics.com · WordPress.org

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

Burst Statistics

WordPress plugin

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

What Burst Statistics adds to your visitors’ browser

Trackers it loads

Cookies seen in our test

burst_uid

What matters for consent with Burst Statistics

It waits for WP Consent API

With WP Consent API present, Burst tracks nothing, page views included, until statistics consent is given. It reads the statistics category only, not the anonymous one.

Without the API, it starts at once

If WP Consent API is not installed, Burst counts every visitor from the first page, whatever the visitor chooses.

Cookie or daily hash

Its daily hash mode recognises visitors without any cookie, from the IP address, the browser and a salt renewed each day.

The fingerprint mode can call out

Its fingerprint mode includes a library that, now and then, sends the fingerprint and the page address to that library’s own servers. Burst does not turn this off. The daily hash mode does not include it.

What our tests found on Burst Statistics

  • Set before the choice · Cookie RocksThree statistics plugins held until consent

    Cookie Rocks 2.11.1 holds Independent Analytics, Burst Statistics and Slimstat until consent. Before the choice and after Refuse, none of them records a visit. After Accept, Independent Analytics and Burst count the page without a reload. Slimstat starts without a reload but only counts from the next page.

    Seen in our tests, 6 November 2026, Cookie Rocks.

  • Good to know · Burst StatisticsWhat Burst Statistics stores in visitors' browsers

    Burst Statistics: 2 cookie(s) or browser key(s) for visitors, recognised by Cookie Rocks from 2.9.8.

    NameKept inCategoryWhat it is for
    _tmjs_lsessionStorageStatisticsBurst Statistics: counts the visit without cookies, within the session
    burst_error_reportedsessionStorageStatisticsBurst Statistics: counts the visit without cookies, within the session

    Read in its code, 2 November 2026, Burst Statistics.

    Full detail

    Burst Statistics can store these in a visitor's browser: _tmjs_l (sessionStorage, statistics: Burst Statistics: counts the visit without cookies, within the session); burst_error_reported (sessionStorage, statistics: Burst Statistics: counts the visit without cookies, within the session). Cookie Rocks recognises them from 2.9.8, with this category and purpose, and lists them in the cookie policy when it sees them.

  • Set before the choice · Burst StatisticsBurst Statistics fingerprint mode sometimes sends data to ThumbmarkJS

    About once in 10,000 fingerprints, at most once per session, it posts the fingerprint and page path to api.thumbmarkjs.com. Burst does not turn this off. The daily-hash mode does not include it.

    Read in its code, 16 October 2026, Burst Statistics 3.7.2.

    Full detail

    Burst Statistics' cookieless fingerprint mode bundles ThumbmarkJS 1.2.0, which about once in 10,000 fingerprint computations, at most once per session (sessionStorage _tmjs_l), sends a POST to api.thumbmarkjs.com/log with the fingerprint, its components and the page path. Burst does not turn this logging off. The daily-hash mode does not include it.

  • Depends on a setting · Burst StatisticsBurst Statistics uses a 30-day visitor cookie by default

    setting “How Burst recognizes visitors” · by default: cookie

    burst_uid is set once tracking is allowed. The daily-hash mode uses no cookie, only a hash of IP and browser with a salt renewed each day.

    Read in its code, 16 October 2026, Burst Statistics 3.7.2.

    Full detail

    Burst Statistics recognises visitors with a cookie by default: burst_uid, 32 random hex characters, 30 days (filter burst_cookie_retention_days), SameSite=Strict, set by JavaScript once tracking is allowed. Its daily-hash mode uses sha256 of IP, user agent and a salt renewed each day, with no cookie. Its script is a combined file at /wp-content/uploads/burst/js/burst.min.js by default; ghost mode gives it a random 8-character name.

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.

  • Burst Statistics 3.7.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: Burst Statistics 3.7.4 on 7 November 2026, with WordPress 7.1.3.

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 PixelMeta for WooCommercePixel and server events, with a hold switch for consent.tested 3.7.8Pixel CaffeineThe Meta pixel on every page, with no consent setting.tested 2.3.3Adds: Meta PixelTikTok for BusinessThe TikTok pixel held, server events to decide.tested 1.4.3Adds: TikTok PixelMicrosoft ClarityClarity on every page, with no consent signal.tested 0.10.37HotjarHotjar held until the visitor agrees.tested 1.0.16HubSpotHubSpot’s loader on every page, consent only in HubSpot.tested 11.3.75JetpackStats, comments, videos and images from WordPress.com.tested 16.4Ad pixel pluginsMeta and TikTok pixels, and what your server sends.MatomoStatistics from your own site, consent through Matomo’s API.tested 5.13.1Koko AnalyticsStatistics on your own site, with a cookie by default.tested 2.5.3Independent AnalyticsNo cookie, but returning visitors are still recognised.tested 2.16.2SlimStat AnalyticsNo consent check by default; one setting changes that.tested 6.0.0Adds: Slimstat AnalyticsStatistics 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.0Plausible AnalyticsStatistics with no cookie, from plausible.io or your own site.tested 2.6.4Fathom 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 PixelWP StatisticsVisitor counts on your own server, without cookies.tested 14.16.18

Every plugin and theme we test →

Questions

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 Burst Statistics users

Statistics that wait for the choice.

statistics, after yes

Every feature of the complete plugin for 30 days, no card. Burst Statistics keeps counting on your own site.

  • 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.

One trial per domain. Local and staging sites never use up your key.

We keep your e-mail address to send your key and help you with it, as explained in our privacy policy. No newsletter, nothing else.