Features Pricing GDPR cookie banner Google Consent Mode v2 WordPress plugin Cookiebot alternative For Agencies GDPR ePrivacy About Contact
RO | EN
Start Free →
Preferences

plausible_ignore — Plausible Analytics Cookie

plausible_ignore is a localStorage entry set by the Plausible Analytics script, not a traditional HTTP cookie, used to mark a visitor (typically a site admin or someone who manually enabled the option) as excluded from the site's traffic statistics. It does not contain identifying data and is not used for tracking or advertising.

Name
plausible_ignore
Provider
Plausible Analytics
Category
Preferences
Type
localStorage
Lifetime
Persistent
Consent
Yes, before it is set (GDPR / ePrivacy)

What is the plausible_ignore cookie?

plausible_ignore is a value stored by the Plausible Analytics script in the browser's localStorage rather than a conventional HTTP cookie. It is set by Plausible's JavaScript script when loaded on a page, but it typically only appears when a visitor explicitly enables exclusion from stats — for example via the ?plausible_ignore=true URL parameter commonly used by site owners or developers to keep their own visits out of traffic data.

It is not set automatically for every visitor of a site — it only appears in browsers where this exclusion has been manually triggered.

What data it stores

The stored value is a simple text value (for example „true”), with no unique identifiers, IP addresses, or personal data attached. Plausible Analytics is known for its cookie-free, non-tracking approach with no persistent cross-site fingerprinting of users.

This entry stays local to the visitor's browser and is not sent to Plausible's servers along with traffic events — its only role is to stop the local script from sending measurement data while the value is present.

What it is used for

The purpose is purely technical and functional: it allows a visitor (typically a site owner, developer, or team member) to be excluded from the traffic statistics shown in the Plausible dashboard, so internal visits don't skew real audience numbers.

This is useful for sites that want to test changes or browse their own site frequently without those visits showing up in analytics reports.

Does it require consent?

In CookieFix's classification, plausible_ignore falls under preferences (functional). Although Plausible Analytics is marketed as a „cookieless” solution with no cross-site tracking, any storage on a user's device — including localStorage — falls under Article 5(3) of the ePrivacy Directive 2002/58/EC (implemented in Romania via Law 506/2004) and is treated similarly to HTTP cookies for consent purposes by data protection authorities such as ANSPDCP.

Site administrators should assess whether this type of storage qualifies as „strictly necessary” (unlikely, since it is an optional feature rather than essential to site function) or whether it requires prior consent. In any case, it must be clearly disclosed in the site's cookie policy, including its purpose and duration.

How to block or delete plausible_ignore

Visitors can manually delete or block this entry through browser settings: Chrome/Edge — Settings → Privacy and security → Cookies and other site data → See all site data; Firefox — Settings → Privacy & Security → Cookies and Site Data; Safari — Preferences → Privacy → Manage Website Data. Clearing local browsing data (localStorage) also removes this value.

For site administrators, the safest approach is to load the Plausible script only after obtaining relevant consent, through a CMP such as CookieFix, which can automatically block the analytics script from running until the visitor makes a choice, avoiding premature storage of any local data.

Frequently asked questions

It is a localStorage entry set by the Plausible Analytics script to mark a visitor as excluded from a site's traffic statistics, usually enabled manually via the plausible_ignore=true URL parameter.

No. It contains no personal identifiers and is not used for advertising or cross-site tracking — Plausible Analytics is designed as a tracking-cookie-free analytics solution.

Since it is local storage tied to an optional feature (excluding oneself from stats) rather than something strictly necessary for the site to function, it typically requires consent under ePrivacy/GDPR and should be disclosed in the cookie policy.

In your browser's privacy settings, find the site data management section (cookies and locally stored data), search for the relevant site's domain, and delete its associated data.

Updated 8 September 2026 · Information comes from the provider’s public documentation and CookieFix scans; it is not legal advice.