Set up your bannerConfigure Your ToolsAnalytics

Snowplow

How to configure Snowplow at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Improve the service, Support marketing analytics

Overview

This guide explains how to implement different privacy configurations for Snowplow and how to reflect them in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. The Snowplow JavaScript / browser tracker sending events to a Snowplow collector. The collector and pipeline can be self-hosted (open source) or operated by Snowplow as a managed service; the legal role depends on which.

What the service does in this scope. By default, Snowplow captures user and session cookie IDs and the IP address. The tracker uses a domain cookie and a session cookie (default names _sp_id and _sp_ses). Three anonymisation levels exist: client-side anonymisation, client-side anonymisation with session tracking, and full anonymisation / cookieless with server anonymisation (anonymousTracking: { withServerAnonymisation: true }, stateStorageStrategy: 'none'), in which the collector neither sets nor reads its cookie and does not capture IP addresses.

Configurations included.

ConfigurationSummary
Configuration A — Lower riskFull anonymisation / cookieless with server anonymisation; self-hosted collector.
Configuration B — Medium riskAnonymous session tracking (no user identifiers; session in client storage); IP anonymisation enrichment; after consent.
Configuration C — Higher risk (default)Full tracking with _sp_id/_sp_ses, network user ID and IP; after consent.

⚠ Recommendation — Configuration A without consent is legally uncertain. In full anonymisation mode, no identifiers or IP addresses are captured, but the tracker still runs on the device. Have your DPO or independent counsel confirm before running A without consent.

Step 1 — Configure Snowplow

#Configuration areaWhere to configure itConfiguration A — Lower riskConfiguration B — Medium riskConfiguration C — Higher risk (default)
1Processing purposesOperator decisionImprove the serviceImprove the serviceImprove the service; Support marketing analytics
2Anonymous trackingTracker init anonymousTracking{ withServerAnonymisation: true }{ withSessionTracking: true }false (default)
3State storagestateStorageStrategy'none''cookieAndLocalStorage'Default
4IP handlingServer anonymisation header / IP anonymisation enrichmentNot capturedIP anonymisation enrichmentFull IP
5Collector hostingOwn infrastructure or managed serviceSelf-hosted, EUSelf-hosted or managed, EUSelf-hosted or managed
6Toggle on consentenableAnonymousTracking / disableAnonymousTracking—Switch to C after consent if desired—

Step 2 — Map the configuration in the Consenter Manager

Processing location. Location of your collector and warehouse. For the managed service, check Snowplow's hosting region and sub-processors; list the United States as a potential access location where US providers are involved.

Consenter Manager fieldConfiguration A — Lower riskConfiguration B — Medium riskConfiguration C — Higher risk (default)
Processing purposesImprove the serviceImprove the serviceImprove the service, Support marketing analytics
Tracking methodNo trackingFirst party tracking (single session)First party tracking (cross-session)
IdentifierNo identifierNo identifierDevice identifiers, IP address
Data categoriesAggregated site statistics, Browsing and interaction data, Device characteristicsAggregated site statistics, Browsing and interaction data, Device characteristics, IP address anonymisedAggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers, IP address
Legal role of data recipientSelf-hostedSelf-hosted (or Processor for managed)Self-hosted (or Processor for managed)
Personalisation modelNo personalisationNo personalisationNo personalisation
Maximum storage durationPer own retentionPer own retentionPer own retention
Processing locationOwn infrastructureOwn infrastructure / managed regionOwn infrastructure / managed region

Privacy-policy follow-up

  • Hosting model; anonymisation level; cookies (C); IP handling; retention.

Verification checklist

  • A: no _sp_* cookies; requests carry the SP-Anonymous header.
  • C: no tracker requests before consent.

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page