Legal Obligation

GDPR processing basis A working definition from the RGM marketing glossary.

Schematic — Legal Obligation

GDPR processing basis

Term: Legal Obligation
Field: Audience & Privacy
Category: Audience & Privacy

Definition in plain terms

Here is the short version.Treat Legal Obligation as an audience or privacy concept with a clear scope. Two people using the term should mean the same thing.

GDPR processing basis

In Audience & Privacy, Legal Obligation names an audience or privacy concept. Pin the meaning down early and the strategy stays coherent.

The mechanics

Pick one definition.Legal Obligation is no fixed dial. How it behaves depends on your audience, your channel mix, and the strategy around it.

Legal Obligation behaves unlike a fixed rule. An early-stage brand and a mature one will apply Legal Obligation on different terms. The mechanics follow the inputs around it. Treat Legal Obligation as a buzzword and the reporting misleads; agree on it and the numbers hold.

The working rule is plain. Agree what Legal Obligation covers first, then act on it. Skip that order and Legal Obligation loses its shared meaning, and two teams end up measuring two different things. Start here.

When to reach for it

Here is the short version.Bring Legal Obligation in when a live call depends on it. With no decision on the table, it stays background.

Legal Obligation matters at the point of a decision. In audience & privacy, three moments come up again and again. Outside them, Legal Obligation is reference material.

Setting budget. Legal Obligation clarifies which budget line deserves more.
Choosing a metric. Legal Obligation checks that the figure is not just noise.
Comparing options. Legal Obligation evens out a comparison that would otherwise mislead.

A concrete walk-through

Start here.To make Legal Obligation concrete, the case below uses Sephora and figures from public reporting plus RGM analysis.

Take Sephora. During a consented-audience rebuild, the team made Legal Obligation the deciding input, not an afterthought. They set a baseline first, agreed one definition of Legal Obligation, and only then read the result: match rates held near 70% after ATT. The number matters less than the order.

Example walk-through for Legal Obligation -- figures illustrative, RGM analysis
Stage	The step taken	Why it mattered
Baseline	Read the starting point before any change to Legal Obligation.	A reference to judge against.
Define	Locked the scope of Legal Obligation so it stayed stable.	No room for scope drift.
Act	A consented-audience rebuild — one variable.	One change, a clean read.
Result	Match rates held near 70% after ATT	An outcome you can trust.

These Legal Obligation numbers are illustrative -- RGM analysis. The structure travels; the specific figures do not.

Pitfalls in practice

Start here.The errors with Legal Obligation are predictable: one blanket rule, no context, chasing the word, raw benchmarks. Each is avoidable.

No segments. Treating Legal Obligation as one number for all. Break it out before you trust it.
No anchor. Quoting Legal Obligation without a starting point. Always pair it with a baseline.
Wrong target. Treating Legal Obligation as the goal. The goal is the outcome it predicts.
Apples to oranges. Comparing Legal Obligation across firms raw. Adjust for pricing and cycle before you read it.

Questions teams ask

What does Legal Obligation mean?

GDPR processing basis Agree the scope of Legal Obligation before the planning starts.

Why does Legal Obligation matter?

Legal Obligation earns its place when it shapes a real decision. The leverage is in correct use, not in the word itself.

How is Legal Obligation used in practice?

Legal Obligation supports a real choice: where money goes, what gets measured, which option wins. The Sephora case traces it.

What goes wrong with Legal Obligation most often?

Chasing Legal Obligation as a goal and benchmarking it raw. Both bury the real trade-off underneath.

Where can I learn more about Legal Obligation?

The related terms below are a good next step; from there, see Apple's App Tracking Transparency, plus server-side tagging.

What does Legal Obligation mean?: GDPR processing basis Agree the scope of Legal Obligation before the planning starts.
Why does Legal Obligation matter?: Legal Obligation earns its place when it shapes a real decision. The leverage is in correct use, not in the word itself.
How is Legal Obligation used in practice?: Legal Obligation supports a real choice: where money goes, what gets measured, which option wins. The Sephora case traces it.