In a world of increasing privacy regulation, managing user consent is no longer optional – it’s a critical part of your data infrastructure. Datahappy is designed with a privacy-native architecture where consent is a first-class citizen, enforced universally by our server-first design.

​
Governance by Design

Unlike traditional client-side approaches where consent logic can be fragmented and inconsistent, Datahappy makes the server the ultimate arbiter of consent.
  1. Client-Side Capture: The Datahappy Pixel has native adapters for leading Consent Management Platforms (CMPs). It listens for consent signals from your CMP and forwards them to our server API
  2. Server-Side Enforcement: The server references your central project configuration and the consent signals captured by the Pixel. It then applies an “effective consent” model for every single event, for every single destination
This means that even if a misconfigured client-side event were to fire, the server would still block it from being sent to a destination for which the user has not given consent.

​
Key Features

  • Per-Destination Consent: Define which consent categories (e.g. advertising, analytics) are required for each of your downstream destinations
  • Event Queuing & Replay: If a user visits your site but hasn’t yet given consent, the Pixel will safely queue any events. If and when the user provides consent later in their session, the queued events are replayed and sent through the appropriate integrations
  • Google Consent Mode v2: The Pixel automatically captures and sends the required Google Consent Mode signals, ensuring your Google destinations remain compliant
  • PII Minimisation by Design: Our entire architecture is built to minimise the amount of Personally Identifiable Information (PII) handled on the client side. We do not scrape forms, fingerprint browsers, or store PII in cookies
With Datahappy, compliance is not a complex add-on, but an inescapable result of our server-first design.