Samtykkr
Cookie consent that is correct under Norwegian law (Electronic Communications Act section 3-15) and the GDPR. English, Bokmal, Nynorsk.
Solid choice
Samtykkr is a solid plugin choice in 2026, with a few things worth checking first. It runs on 60+ sites, is rated 5/5 and was last updated 2 weeks ago, and scores 75/100 on our health check.
- Actively developed — last update 2 weeks ago
- Tested with the latest WordPress (7.1)
- Small user base (60+ active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & supportDaily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Samtykkr stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| consent mode | #99 |
| cookie banner | >100 |
| cookie consent | >100 |
| GDPR | >100 |
| privacy | >100 |
Version adoption
Share of active sites per release.
Rating breakdown
★★★★★★★★★★ 5 from 1 reviews
About Samtykkr
From the official readme · v1.1.0Description
Samtykkr is a lightweight cookie consent banner built to be correct under Norwegian law out of the box. Since 1 January 2025, the Norwegian Electronic Communications Act section 3-15 requires consent that is valid under the GDPR before cookies and similar technologies are used. Most banners get the details wrong. Samtykkr ships with defaults that follow the requirements, so you do not have to be a privacy expert to set it up correctly.
Correct by default
Accept and Reject are placed in the first layer, with the same size and contrast, as the Norwegian Data Protection Authority requires. There are no pre-ticked boxes, and consent is specific, with a separate choice per purpose.
No tracking before consent
Google Consent Mode v2 starts at denied for every category and is updated only when the visitor consents. Tracking scripts are blocked until then. Samtykkr runs Basic consent mode, so no data is sent to Google before consent.
Withdraw at any time
A permanent button lets visitors change or withdraw their choice whenever they want. Every choice is recorded in a local consent log that serves as documentation.
Norwegian and English
The banner, the choice window and the settings are available in English, Bokmal and Nynorsk, and follow the language of the site. A site in any other language gets English. The purpose texts are written for Norwegian law, not generically translated.
Lightweight and accessible
The banner is small, reads client-side, and does not break caching or Core Web Vitals. It works with common caching plugins and page builders. It follows WCAG, is keyboard friendly, and is accessible.
Your data stays on your site
The consent log lives in your own WordPress database. It is not sent to us or to a cloud abroad.
Pro
Samtykkr Pro adds a tracker scanner, automatic tracker and rule updates, an audit PDF for documentation, white-label, and multi-site management for agencies. Learn more at https://samtykkr.no
Samtykkr is a product of Northflow Technologies AS.
Installation
- Upload the plugin through Plugins > Add New, or install it directly from the WordPress plugin directory.
- Activate the plugin.
- Open Settings > Samtykkr and run the short setup wizard: choose your default language, confirm which services your site uses, and adjust the appearance.
- Save. The banner appears on the front end with lawful defaults already in place.
Changelog
Initial release.
1.1.0
- New design: the banner is now a full-width strip at the bottom of the screen, with a choice window per purpose. Agree and disagree stay identical in size and contrast. Your colours, texts, services and saved consents carry over, and visitors are not asked again. The old banner can be chosen under Settings, Samtykkr.
- New: the admin is available in English, and the banner language can follow the site. A site in a language we have no text for gets English, not Norwegian. Cookie descriptions in the declaration are now in English on an English site.
- Fix: button text reaches AA contrast on mid-grey accent colours too.
1.0.9
- Fix: on themes with a button reset, such as Hello Elementor, the cookie button in the corner became a wide empty box. It is now a small round icon, and the banner keeps its shape on those themes.
- Fix: the banner buttons are now the same size, also when one label is longer than the others.
- Fix: the banner no longer opens with a focus ring around the privacy link. Keyboard users start from the dialog itself.
- Fix: a page with a very large inline script could come out blank. The page pass now reads the markup with a linear scanner, and if anything goes wrong in it the visitor gets the page as it was.
- Privacy fix: a tracker added by JavaScript is now stopped before the request leaves the browser, also after the page has loaded. This covers createElement, new Image(), setAttribute, innerHTML and document.write.
- Privacy fix: rejecting after accepting, or changing your choice, now removes the cookies of the categories you turned off and reloads the page, so scripts that were already running stop. Consent Mode is updated to denied. On a page reached by a form post, or with a half-filled form, the next page finishes this instead.
- Privacy fix: the page pass now catches tags without quotes around attributes, delayed scripts from page-speed plugins, srcset and lazy-load attributes, picture and video sources, embeds and hardcoded iframes.
- Fix: an inline script is only held back when it is plainly a tracker loader, and never when it is larger than 16 KB. A theme setting or a template that mentions a service keeps working, and anything such code tries to load is still stopped in the browser. deadline.com no longer counts as adline.com.
- Privacy fix: a top-level @import or @font-face against a selected service in inline CSS now waits for consent. The rest of the CSS stays where it is.
- New: a tag with the data-nf-ignore attribute is left alone, for code you know is safe.
- Fix: a page with too little memory left to rewrite it now passes through unchanged.
- Fix: a held script that calls document.write could wipe the page after consent. What it writes now goes where the script stands.
- Fix: the consent log kept working only until a cached page’s nonce expired. The log endpoint no longer depends on one. It takes JSON from the site’s own pages only, with a rate limit per address and for the whole site, and refused requests are shown in the admin. Records use the server’s clock, and a retried request does not add a row.
- New: consent records are removed after a period you choose, 730 days by default and at least 366, and the whole log can be downloaded as CSV.
- New: a warning in the admin when no services are selected, since nothing is blocked then.
- Change: Stripe, Klarna and Vipps are now necessary and are never blocked, so checkout works for visitors who reject. reCAPTCHA is never ticked for you and shows a warning.
- Fix: a service missing from a downloaded service list no longer stops being blocked. The two lists are merged per service, every entry is checked, and a service marked necessary stays necessary.
- Change: visitors are asked again when the services on your site change, not every time the service list is updated.
- Fix: saving settings on a site with centrally managed settings no longer turns them into local ones.
- Fix: a corrupt consent cookie no longer stops the banner.
1.0.8
- Fix: the accent colour chosen in the setup wizard is now actually applied. The colour was written to a scope the banner never read, so the banner stayed green whatever you picked. Button hover and button text colour now follow your accent too, so a pale colour no longer leaves unreadable white text.
- Privacy fix: a blocked service is now stopped before consent even when it does not load through WordPress. Only enqueued scripts and oEmbeds were caught before, so a stylesheet, a tracking pixel, a script tag written straight into a theme template, or a conversion snippet pasted into a page could all still load on the very first paint while the service was switched on for blocking. Google Fonts was the worst of them: it is listed as a third-country transfer that can pass Google the visitor’s IP address, and it always arrives as a stylesheet. Samtykkr now checks the finished page as well, and removes the DNS-prefetch and preconnect hints that point at a blocked service. Developers can switch the page pass off with the samtykkr_use_output_buffer filter.
- Two services added to the service list: Adline (marketing) and Umami (statistics).
- Fix: themes that uppercase or letterspace every button no longer rewrite the banner’s own text.
- Fix: the internal version constant had fallen behind the plugin version, so updates could keep serving previously cached scripts and styles.
1.0.7
- English as a full site language: you can now choose English as the default language in the setup wizard, so the banner, cookie declaration and generated pages are all in English for every visitor. Useful for Norwegian companies with an international audience. Norwegian (Bokmål/Nynorsk) is unchanged, and the “show English to English browsers” fallback still works when the default is Norwegian.
1.0.6
- Fix: the consent blocker no longer runs in wp-admin. This prevents a conflict where the block editor (and other plugins’ blocks) could fail to render.
1.0.5
- Banner: the buttons and the floating manage button are now isolated from the host theme’s button styling, so they always show the correct colours. The manage button is a touch smaller and tidier.
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Samtykkr alternatives
All consent mode plugins →FAQ
Samtykkr: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Nov 16, 2026
Is Samtykkr free?
Yes. Samtykkr is free to download and use from the official WordPress.org plugin directory.
Is Samtykkr safe to use in 2026?
Samtykkr is a solid plugin choice in 2026, with a few things worth checking first. It runs on 60+ sites, is rated 5/5 and was last updated 2 weeks ago, and scores 75/100 on our health check.
How many websites use Samtykkr?
Samtykkr is active on 60+ WordPress websites and has been downloaded 863 times since it launched in June 2026. It was downloaded 385 times in the last 30 days.
Does Samtykkr work with WordPress 7.1?
Yes. The developer has tested Samtykkr up to WordPress 7.1.4, the latest release. It requires WordPress 6.4 or newer.
What PHP version does Samtykkr need?
Samtykkr requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Samtykkr last updated?
The latest version, 1.1.0, was released on November 1, 2026 (2 weeks ago).
Who makes Samtykkr?
Samtykkr is developed and maintained by Northflow Technologies.
What are the best alternatives to Samtykkr?
The most popular alternatives to Samtykkr are tarteaucitron.io (10K+ installs), Cookie Choices (for EU Cook… (9K+ installs) and GAinWP Google Analytics Int… (7K+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card



