Definition
PDEI measures the percentage of current data processing activities that fall outside the scope of consent as originally granted, quantifying the accumulated gap between what users agreed to and what the organization actually does with their data.
The Measurement Gap
Marketing technology stacks evolve continuously. New tools are added, new data integrations are built, new AI models are trained, new use cases are deployed. Each addition potentially creates a new data processing purpose. But the consent collected from users reflects the processing purposes that existed when consent was granted, not the purposes that have accumulated since. This creates a drift between the consent basis and actual processing that only grows over time. Legacy privacy metrics like consent rate and DSAR response time measure the mechanics of consent collection and data rights fulfillment, but they have no mechanism to detect whether the processing activities that consent was supposed to authorize have expanded beyond what was originally described. A martech team that adds a new personalization engine, integrates a new analytics provider, or deploys an AI recommendation model has created new processing purposes that may not be covered by existing consent categories. Each addition is individually small, but the cumulative drift can be substantial. An organization may be technically collecting consent while materially processing data in ways that consent does not cover. Regulatory frameworks (GDPR's purpose limitation principle, CCPA's right to know, and the principle of data minimization) all require that processing be limited to the purposes disclosed at the time of consent. Purpose drift is not a hypothetical compliance risk: it is a structural inevitability in any martech environment that evolves faster than its consent framework refreshes. Without measuring the gap between consented purposes and actual purposes, organizations cannot assess their true compliance exposure.
Decision Supported:
What percentage of our current data processing activities are not covered by consent as originally granted, and where is purpose drift creating compliance exposure that requires consent refresh or processing restriction?
Formula
Plain language: Count all active data processing purposes across the martech stack. Identify which purposes are covered by current consent categories and which are not. Divide the uncovered purposes by total purposes and multiply by 100.
Notation:
PDEI = (Processing_purposes_uncovered / Processing_purposes_total) × 100
Variables:
| Variable | Definition | Unit |
|---|---|---|
| Processing_purposes_total | Count of all distinct data processing purposes currently active across the marketing technology stack, including analytics, personalization, targeting, measurement, and third-party data sharing | Count |
| Processing_purposes_uncovered | Count of active processing purposes not explicitly covered by current consent categories as defined in the consent management platform | Count |
Proposed formula, pending validation pilots.