Overview
The Surfside Digital SDK has a consent framework built in. It reads consent from your Consent Management Platform (CMP) and from the shopper's browser, turns what it finds into one clear decision, and applies that decision to every event before it leaves the page. You don't have to install anything extra.
CMP & Browser Signals
The SDK reads three standard consent signals automatically: IAB TCF, IAB GPP and Global Privacy Control. All three are on by default. You can turn any of them off for a source in Configuration.
Setting Consent from Your Site
If your site runs an IAB TCF or GPP CMP, the SDK reads it automatically and you may not need anything on this page. Use the consent API when:
Enforcement
The SDK enforces consent itself. You don't need to wrap your tracking calls in consent checks: call setUser, setCommerceAction and the rest as usual, and the SDK decides what can leave the page.
Configuration & Storage
The consent framework works with no configuration. Every signal reader is on, stored decisions never expire, and nothing needs to be set up. The options below are there for when a source needs something different.
Consent Data in Your Events
The SDK records consent in two places, so you can show what was collected under what permission:
Testing & Troubleshooting
You can check everything on this page from your browser's developer console, on any page where the Surfside tag is installed.
Privacy Regulations & Signals
This page shows how the main privacy regimes relate to the signals the Surfside SDK reads. It's a technical map, not legal advice. Your legal team decides which regimes apply to your business and what your consent experience has to do. The SDK's job is to honour the decisions your CMP and your shoppers make.