SlimStat 6 launchfrom $34.30/yr1 site · 5 sites $83.30 · unlimited sites $139.3030% off every planEnds Nov 16 (UTC)

Get the offer
SlimStat
Configuration

How to integrate with GDPR banner plugins?

By Published Updated

Applies to SlimStat 6.0.0 · checked

SlimStat can use its own consent banner or integrate with a consent management platform through the WP Consent API. Configure the integration before collecting traffic, then test acceptance and refusal on your own site.

Check the defaults first

In SlimStat 6, GDPR compliance mode, Anonymize IP addresses and Hash IP addresses are off by default. Set tracking cookie is on. Updating an existing site preserves its configured settings. Self-hosting does not by itself make collection anonymous or establish legal compliance.

  1. Open SlimStat → Settings → Tracker and find the Consent management section.
  2. Turn on GDPR compliance mode and set Consent plugin integration to the choice that matches your site.
  3. For an external banner, choose Via WP Consent API, install the WP Consent API plugin, and make sure the banner’s statistics choice is the one that allows analytics. Use one banner to manage visitor choices.
  4. For SlimStat’s own banner, choose SlimStat Consent Banner (Recommended) and review its message, button labels and theme.
  5. Choose IP protection and cookie settings, save, and clear page caches.

Using Borlabs Cookie or Real Cookie Banner, or not sure which route fits? See which consent banners work with SlimStat.

Tracking eligibility and permission to store identifying data are separate decisions. With GDPR compliance mode on, SlimStat checks consent only when the configuration collects identifying data: Set tracking cookie on, or IP addresses stored in full. Do not assume that every refused consent choice produces either a complete row or no row at all. The consent banner guide lists what each configuration records before a choice.

Ecommerce and optional heatmap capture

Heatmap recording starts off and must be enabled deliberately with Pro. It follows consent and Do Not Track and does not store typed input. Existing eligible link/button events have their own Events/Goals behavior.

An Ecommerce order-to-visit association needs an existing verified, unexpired tracker cookie and an eligible retained human pageview. It does not introduce IP/email matching or a new browser identifier. A store order can still contribute to the commerce totals without a SlimStat visit association; inspect attribution coverage rather than assuming every order has a tracked journey.

Test these features separately after Ecommerce setup or heatmap opt-in.

Test the complete journey

Use a fresh private browser session for each test:

  • Before a choice: inspect cookies and the Access Log. Confirm behavior matches your selected policy.
  • Reject: check that restricted data and cookies are not collected contrary to your configuration.
  • Accept: visit another page and confirm eligible tracking works.
  • Withdraw: change the choice and verify subsequent tracking changes accordingly.

SlimStat 6 corrects a consent-upgrade path that could duplicate a pageview. Totals may decrease after upgrading because the same pageview is no longer counted twice.

Consent withdrawal does not erase historical rows automatically. Set a retention policy and handle stored data, archives and backups as part of your site’s privacy process.