Works with your stack
Cookie consent for Koko Analytics
counted at home, cookie included
Koko Analytics counts visits on your own site and contacts no other company. By default it uses a cookie: the page view leaves at once, and your server answers with a short-lived cookie. Its cookieless method keeps a session file on the server instead. It has no WP Consent API code.
By ibericode BV · kokoanalytics.com · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
Koko Analytics
WordPress plugin
- Tested version
- 2.5.3
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
- Latest version
- 2.5.3 tested
- Active installs
- 70,000+
What Koko Analytics adds to your visitors’ browser
Trackers it loads
- Koko Analytics →Statistics
Cookies seen in our test
_koko_analytics_pages_viewed
What matters for consent with Koko Analytics
A cookie from the first page
In its default mode, the page view is sent as soon as the page loads, and the server’s answer sets the cookie. That happens before any choice, unless the tracking script is held.
The cookieless method
Koko Analytics can count without a cookie. The server then keeps a session file named from a hash of the IP address and the browser, removed the next day. Nothing is written in the browser.
An inline script
Its tracking code is printed in the page footer, not loaded as a file. A rule that looks for a script address does not find it.
It does not read the choice
Koko Analytics has no WP Consent API code, so it does not read the visitor’s choice by itself. To wait for a choice, its tracking script has to be held.
What our tests found on Koko Analytics
Depends on a setting · Cookie RocksExempt measurement for Koko and Independent Analytics
With exempt audience measurement on, in a country that allows it, Cookie Rocks 2.11.1 lets Koko Analytics in fingerprint mode and Independent Analytics with a daily salt count a visit before the choice, with no cookie. After Refuse they stop. Koko in cookie mode, and Independent Analytics without the daily salt, stay held until consent.
Seen in our tests, 6 November 2026, Cookie Rocks.
Good to know · Koko AnalyticsKoko Analytics stays silent for automated browsers
A driven browser sees nothing, while a real visitor gets the cookie in the default mode.
Seen in our tests, 6 November 2026, Koko Analytics 2.5.3.
Full detail
Koko Analytics sends no page view when navigator.webdriver is true, or when the user agent looks like a bot. An automatic test in a driven browser therefore sees no request and no cookie, although a real visitor gets the cookie in the default mode.
Depends on a setting · Koko AnalyticsKoko Analytics: use_cookie set to false does nothing with the default method
The default method is also cookie, so a banner must change the method too.
Read in its code, 6 November 2026, Koko Analytics 2.5.3.
Full detail
Koko Analytics 2.5.3 still reads window.koko_analytics.use_cookie, which a comment keeps for cookie banners. Its script sends m = use_cookie ? 'c' : method[0], and the default method is cookie, so setting use_cookie to false changes nothing on a default site: the method must change too.
Depends on a setting · Koko AnalyticsKoko Analytics sets a cookie from the server by default
setting “tracking_method” · by default: cookie
Its default method sends each page view to the site, whose reply sets _koko_analytics_pages_viewed until midnight. No third-party host is contacted.
Read in its code, 16 October 2026, Koko Analytics 2.5.3.
Full detail
Koko Analytics defaults to the cookie tracking method. Its inline footer script sends the page view at once by sendBeacon (or fetch) to the site itself, and the server response sets _koko_analytics_pages_viewed (HttpOnly, path /, expires at the next midnight in the site's time zone). The JavaScript writes no cookie or storage, and no third-party host is contacted.
Good to know · Koko AnalyticsKoko Analytics cookieless mode keeps a daily session on the server
The session file is named by a hash of a daily seed, the user agent and the IP address, and deleted after midnight. Its tracker is now in the page, so address patterns no longer match it.
Read in its code, 16 October 2026, Koko Analytics 2.5.3.
Full detail
Koko Analytics' cookieless method keeps a server-side session file named by a hash of a daily seed, the user agent and the IP address, deleted after midnight. Since 2.x the tracking script is printed inline in wp_footer, so address patterns on assets/dist/js/script.js no longer match anything. It has no WP Consent API code.
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.
- Koko Analytics 2.5.3, 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: Koko Analytics 2.5.3 on 7 November 2026, with WordPress 7.1.3.
Analytics and ad pixels
Other plugins of the same kind.
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 Koko Analytics users
Light statistics, clear consent.
no other company
Every feature of the complete plugin for 30 days, no card. Koko Analytics 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
Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.