Skip to guide
Nodkeeper

Installation guide

Install and verify your consent banner.

Connect the services your site uses, then check what a visitor’s choice actually changes in their browser.

Open your websites

Prepare your services

Walk through the public pages, forms, booking flow and embedded content. Include browser storage alongside cookies. For each declared cookie, enter its name, provider, purpose, storage duration, data used and first- or third-party status in the service record. Identify any recipients of personal data in your own notice.

In Services, give each integration a stable ID and explain its purpose in words a visitor would use. A trainer’s booking form might need a session cookie to keep a requested booking together. A pixel that measures advertising conversions serves a separate purpose.

Publish the full inventory in your own cookie notice. Link that notice or your privacy page from the banner. Review it whenever a provider, purpose or storage period changes.

Connect the banner

  1. Set the language and appearance. Preview the banner over your own page on desktop and mobile. If the site restricts embedding, use a screenshot of the same page as the backdrop.
  2. Publish your configuration. Check the site’s registered domain and the purpose of each service. Open Installation and select a delivery method. Add its site-specific snippet to the shared page head.
  3. Connect optional integrations. Replace each original script or frame with the corresponding installation example. Remove duplicate loading paths in your theme, plugins and tag manager. Registering a service in the catalogue alone leaves existing tags running.
  4. Keep settings within reach. Provide a persistent way for visitors to reopen their choices from every page. Try it with a keyboard and on a phone.

Test visitor choices

Use a fresh browser profile and open the network and storage panels before navigating. Exercise the paths where each integration normally runs. Repeat on a subpage that visitors can enter directly.

Before a choice
Only services you have justified as necessary should run. Check requests, cookies and browser storage before clicking the banner.
After declining
Try the same content and booking flow. Optional tags should stay dormant after navigation and a reload.
After a partial choice
Enable one purpose only. Check that its registered integrations run and that other optional integrations remain dormant.
After withdrawal
Reopen settings and withdraw the earlier permission. Revisit the affected page and check for further requests. Confirm any provider-specific shutdown and cookie cleanup your integration requires.

Use Website scans to verify a domain and review the evidence collected for it. Repeat the checks after template changes and provider updates. Record the page, policy version, time and actions tested. A page can load additional services after a video plays, a form opens or a visitor signs in.

Read the records

For a hosted installation, Consent activity counts received choice events against published versions. Someone who saves a choice and later changes it can contribute more than once. The totals describe decisions, so they cannot tell you how many distinct people visited or prove a particular person consented.

A self-hosted ZIP sends no choice events to the service. Its visitors’ decisions stay in their browsers and do not appear in the workspace.

Keep a copy of what you asked visitors, the published version and your verification results. If a separate service relies on consent to process personal data, assess what evidence that processing requires. Matching people by IP address or browser fingerprint is outside the activity report.

Read how Nodkeeper handles data

Swedish and EU guidance

In Sweden, storing or reading information on a visitor’s device generally requires prior consent. The strictly necessary exception depends on the service the visitor requests. Where personal data is processed, the site operator must also establish the applicable GDPR basis and meet its transparency obligations.