Matomo integration
Connect Matomo Cloud or a self-hosted Matomo, and how tracking follows each rule.
Matomo Analytics
Your Matomo, in step with consent.
Connect the Matomo you already run, Cloud or self-hosted. Kukie.io loads the tracker from your server and starts or stops tracking by your region rule and each visitor's choice.
The Matomo integration is available on every plan.
Watch the explainer
How Matomo follows each visitor's choice.
Two fields to connect it, what the tracker does before and after a choice, and how to check it in your own Matomo.
2 minutes 17 seconds, narrated, with captions in the player. The sites and rules in it are examples.
Read the transcript
- 0:00 Matomo is web analytics you own. It runs on your own server, or on Matomo Cloud, and the data stays with you.
- 0:08 Matomo has its own consent commands. But something has to tell it, on every page, what each visitor chose.
- 0:15 That's what Kukie.io does. In the Banner Editor, open Integrations, turn on Matomo, and enter your Matomo URL and site ID. Two fields, and no new code on your pages.
- 0:27 Kukie.io never sees your analytics. The tracker loads from your server, and every page view goes straight from the visitor's browser to your Matomo.
- 0:37 Under an opt-in rule, Matomo waits. Before a choice, the browser sends it nothing at all.
- 0:43 When the visitor accepts Analytics, Kukie.io loads the tracker, gives consent, and records the page view. No page reload.
- 0:51 On the next visit, a visitor who accepted is tracked from the first page, with no banner.
- 0:57 Change of mind? Kukie.io sends forget consent given, and Matomo stops on the same page. The Analytics cookies on your cookie list are deleted too.
- 1:08 Under an opt-out or notice-only rule, Matomo tracks from the first page, with its Do Not Track support on. And a Global Privacy Control signal your site respects counts as a refusal.
- 1:20 Your region rules decide which one applies, visitor by visitor.
- 1:24 The numbers stay right. Only a change from no to yes records a page view, so saving the same choice again sends nothing.
- 1:32 The cookie scanner knows Matomo too. It files Matomo's cookies under Analytics, and the Providers tab lists Matomo with its privacy policy and data processing agreement.
- 1:44 Already have Matomo code on your pages? Remove it, so each visit counts once. Or keep it, leave the integration off, and Auto-block Scripts holds it until the visitor consents.
- 1:55 Then check it. Filter your browser's network panel for matomo, accept, and the visit appears in your Matomo Visits Log.
- 2:04 The Matomo integration is included on every plan, including Free. Your Matomo, in step with consent.
Your data
Your analytics stay in your Matomo.
Matomo's requests go from the visitor's browser straight to your Matomo server. Kukie.io decides when the tracker may run, and never receives what it collects.
-
Kukie.io's banner
Decides when Matomo may load and sends its consent commands.
-
Your Matomo
Your dataReceives every page view, from the visitor's browser, at the URL you entered.
-
Kukie.io
No analyticsKeeps the visitor's consent record, as on every site. It receives none of Matomo's data.
Rule by rule
What Matomo does under each rule.
Your region rules decide when Matomo may track. These are the commands Kukie.io sends at each moment.
Built in
Details that keep your numbers right.
What Kukie.io takes care of around the tracker, so Matomo counts what your visitors allowed and nothing twice.
One page view per yes
Only a change from no to yes records a page view. Saving the same choice again sends nothing.
A withdrawal stops tracking
forgetConsentGiven stops Matomo on the same page, and the Analytics cookies on your cookie list are deleted.
Do Not Track respected
Under an opt-out or notice-only rule, Matomo's own Do Not Track support is on.
Your own snippet, held
With the integration off, Auto-block Scripts holds a hand-added Matomo snippet until the visitor consents.
HTTPS, on a public address
Your visitors' browsers load the tracker from your Matomo URL. Local and private addresses are refused when you save.
The JavaScript tracker
Kukie.io loads matomo.js from your server. It does not load Matomo Tag Manager containers.
Check it yourself
Check it in two minutes.
You need your site under an opt-in rule, your browser's developer tools and your Matomo.
1. The requests
Open Network and filter for matomo. Before a choice the list is empty. Select Accept all and two requests appear:
Use a private window, so an earlier choice does not answer for you.
2. Your Matomo
In Matomo, open Visitors, then Visits Log. The visit appears with the page you accepted on:
The Site ID is in Matomo under Administration, then Websites, then Manage.
Setup
Connect it in three steps.
Two fields in the Banner Editor, and one line of code to remove.
-
Step 1: Add your site
Create an account, add your website and put the Kukie.io embed code on your pages. -
Step 2: Connect your Matomo
In Banner Editor, open Integrations, turn on Enable Matomo Integration and enter your Matomo URL and Site ID. -
Step 3: Remove your old snippet
If your pages already load Matomo, remove that code, so each visit is counted once.
Works with either kind of Matomo, and beside the other consent signals
- Matomo Cloud
- Self-hosted Matomo
- Google Consent Mode v2
- Microsoft Clarity
- Google Tag Manager
Documentation
Guides to setting it up.
Step-by-step guides in the Help Centre.
-
-
Consent models explained
Opt-in, opt-out and notice only, and which one each region needs.
-
Microsoft Clarity Consent Mode
Send the same choice to Clarity, with its two signals.
Questions about Matomo and Kukie.io
Do I need my own Matomo?
Yes. Kukie.io does not host Matomo or show Matomo reports. It connects the Matomo you already use, Matomo Cloud or a self-hosted Matomo, to your cookie banner.
Does Kukie.io see my analytics data?
No. Matomo's requests go from the visitor's browser to your Matomo server. Kukie.io loads the tracker and sends Matomo's consent commands, and never receives the data.
What happens before a visitor chooses under an opt-in rule?
Nothing reaches Matomo. Kukie.io loads the tracker only once the visitor accepts Analytics, then records the page view with consent given. A returning visitor who accepted is tracked from the first page of the visit.
What happens under an opt-out or notice-only rule?
Matomo loads and tracks as the page loads, with its Do Not Track support on. If the visitor opts out of Analytics, tracking stops on that page and Matomo does not load on later pages.
What happens when a visitor withdraws consent?
Kukie.io sends forgetConsentGiven, so Matomo stops tracking. It also deletes the cookies your cookie list puts under Analytics, such as Matomo's _pk_id once a scan has found it.
Will a page view be counted twice?
Not by Kukie.io. It records a page view only when consent changes from no to yes, so saving the same choice again sends nothing. Remove any Matomo code you added to your pages by hand, or both copies count.
Can I keep my own Matomo code instead?
Yes. Leave the integration off and place your Matomo snippet below the Kukie.io script in the head. Auto-block Scripts treats Matomo as an Analytics script and holds it until the visitor consents.
Does it work with Matomo Tag Manager?
No. The integration loads the Matomo JavaScript tracker, matomo.js. It does not load Matomo Tag Manager containers.
Does Matomo use Google Consent Mode?
No. Matomo has its own consent commands, requireConsent, setConsentGiven and forgetConsentGiven, and those are what Kukie.io sends.
Which plans include the Matomo integration?
The Matomo integration is available on every plan. The pricing page lists what each plan includes.
Let Matomo follow your visitors' choices.
Connect your Matomo in a few minutes, with two fields and no new code on your pages.
Disclaimer
Kukie.io provides tools to collect and record consent. It is not legal advice, and using it does not by itself make a website compliant with any law.
