Skip to content

Works with your stack

Cookie consent for Pirsch Analytics on WordPress

two ways to count

← Cookie Rocks for your stack

The Pirsch Analytics plugin counts visits without cookies, in one of two ways. Its script, api.pirsch.io/pa.js, runs in the browser: Cookie Rocks Pro holds it until consent. Its server mode sends each page view from your server to Pirsch, with the visitor’s IP address and browser details: that request never reaches the browser, so no banner can hold it.

By Pirsch · pirsch.io · WordPress.org

Also in: Statistics on your own site

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

The two ways the Pirsch plugin counts

The script
With an identification code and the script option, pa.js loads from api.pirsch.io on every page: Pirsch.
The server mode
With a client access key, your server sends each page view to Pirsch, with the IP address, browser and page, before the page reaches the visitor.

What matters for consent with Pirsch Analytics

The script waits

In script mode, Pirsch reads information from the visitor’s device, so EU cookie rules (ePrivacy) apply even without cookies. Cookie Rocks Pro holds pa.js until the visitor accepts statistics, then loads it without a reload, except where a country allows exempt audience measurement. After Reject all, nothing reaches Pirsch.

The server mode counts everyone

In server mode, nothing is read on the device, but each page view still goes to Pirsch with the visitor’s IP address, whatever the visitor chose. Name Pirsch in your privacy policy, and make sure a visitor who refuses statistics is not counted: today, only the script mode does that with Cookie Rocks.

No cookie either way

In our test, Pirsch set no cookie and stored nothing in the browser.

What our tests found on Pirsch Analytics

  • Before the choice · Pirsch AnalyticsPirsch: a script that waits, a server count that cannot

    The Pirsch Analytics plugin 2.2.1 counts visits in two ways. With an identification code and the script option on, it adds api.pirsch.io/pa.js: Cookie Rocks Pro holds it until consent, loads it after Accept all without a reload, and nothing after Reject all. No cookie and no browser storage were set. With a client access key, the plugin sends each page view from the site’s server to Pirsch, with the visitor’s IP address and browser details: that request never passes through the browser, so no banner can hold it.

    Seen in our tests, 11 November 2026, Pirsch Analytics 2.2.1.

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.9Pixel 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.38HotjarHotjar held until the visitor agrees.tested 1.0.16HubSpotHubSpot’s loader on every page, consent only in HubSpot.tested 11.3.82JetpackStats, 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.3Burst StatisticsWaits for statistics consent when WP Consent API is there.tested 3.7.5SlimStat AnalyticsNo consent check by default; one setting changes that.tested 6.1.2Adds: 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.74.3Plausible AnalyticsStatistics with no cookie, from plausible.io or your own site.tested 2.6.4Fathom AnalyticsStatistics with no cookie, from cdn.usefathom.com.Nelio A/B TestingA/B tests with one cookie, only while a test runs.StatifyPage views counted in your own database, no cookie.UmamiCookieless analytics that wait for consent.StatCounterVisitor counts that wait for consent.Agile CRMSession cookies of the tracking script, removed until consent.CallRail Phone Call TrackingSwaps your phone number to tell which source brought a call.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.19

Every plugin and theme we test →

Questions

Which mode should I use with a banner?

The script mode. It is the one Cookie Rocks can hold until the visitor’s choice.

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

Cookieless counting that follows the choice.

script mode

Every feature of the complete plugin for 30 days, no card. Pirsch counts visitors who accept.

  • 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

Cookie Rocks

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.