Skip to main content
Adrià García
Menu
← Back to the glossary

Identity and governance

DULE and data usage governance

Data Usage Labelling and Enforcement in Adobe Experience Platform

DULE is AEP’s framework for governing data use. Labels express restrictions; policies connect them to marketing actions. An enforcement point evaluates the operation and can block it.

When it applies
When a contract or governance decision limits data use. For example, allowing internal analysis but prohibiting third-party export. The organisation defines the restriction; technical configuration enforces it.
What it is confused with
A label does not block anything on its own. Usage policies are disabled by default, including predefined policies. DULE does not replace access controls or individual consent.
Architecture consequence
Check the whole chain: restriction, label, enabled policy, marketing action and enforcement point. A test that should be blocked and a permitted one help reveal incomplete configuration.

Related concepts

Related patterns

Coverage depends on the integration

Adobe provides automatic enforcement and evaluation through Policy Service API. In a custom integration, querying the API does not prevent the operation: the application must act on the result. It is not automatic protection for every data output.

AJO: profile and event context are not equivalent

AJO documentation limits this DULE enforcement to profile attributes. It does not cover journey event context fields. Labelling them in the interface does not remove that limitation; additional controls are needed.

CJA: analysis and export also matter

Enabled policies can restrict Data View components and exports. C12 restricts field export or download when the corresponding policy is enabled. Labels do not automatically propagate to stitched datasets; review them explicitly.

Can I send this? →

Adobe documentation

Explore this decision