What is the dpm cookie?
"dpm" is an HTTP cookie associated with Adobe Audience Manager (AAM), Adobe's data management platform (DMP) used for audience segmentation and targeted advertising. It is set on the .dpm.demdex.net domain — "demdex" being the technical identity Adobe uses for its visitor identity management services (Adobe Experience Cloud ID / Device Co-op).
The cookie typically appears when a website integrates Adobe Audience Manager or other Adobe Experience Cloud services that use the "device co-op" feature to sync identifiers (cookie matching/syncing) with other third-party advertising and data platforms.
What data it stores
The "dpm" cookie is used in the identifier sync process (cookie syncing) between Adobe Audience Manager and partner advertising platforms. It essentially helps map a unique Adobe identifier to identifiers used by other ad networks, so data about the same visitor can be recognized across multiple systems.
The exact value format may vary and is not publicly documented in detail by Adobe. Data associated with this process is sent to Adobe's servers (demdex.net) and, through the sync mechanism, may be shared with third-party advertising partners connected via Audience Manager.
What it is used for
For Adobe, this cookie supports the functioning of its data-sync network (device co-op), allowing audience profiles built in Audience Manager to be usable across other programmatic advertising platforms.
For the website operator, this cookie supports targeted advertising campaigns, remarketing, and audience segmentation based on browsing behavior, typically as part of a broader digital marketing strategy built on Adobe Experience Cloud.
Does it require consent?
Since it is used exclusively for advertising and third-party data-syncing purposes, the "dpm" cookie falls under the marketing category. Under the ePrivacy Directive (as transposed in Romania via Law 506/2004) and the GDPR, this type of cookie requires the visitor's prior, explicit consent before being set.
- The site operator must declare this cookie in the cookie policy under the "marketing" category.
- The script that sets it (Adobe Audience Manager) must not load before the visitor gives consent.
- Consent must be as easy to withdraw as it was to give, per regulatory guidance (including from Romania's ANSPDCP).
How to block or delete dpm
A visitor can manually delete or block this cookie from browser settings (Chrome, Firefox, Edge, Safari) under the per-site cookie management section, by searching for demdex.net. Ad-tracker blocking extensions can also prevent it from being set.
For site operators, blocking it automatically before consent is essential for compliance: a consent management platform such as CookieFix can hold back execution of the Adobe Audience Manager script until the visitor accepts the marketing category, preventing the cookie from being placed without valid consent.
Frequently asked questions
It's not technically harmful, but it's used for advertising tracking and sharing identifiers with third parties, which is why it requires explicit consent under GDPR.
It's set by Adobe Audience Manager, via the demdex.net domain, when a website uses this Adobe solution for advertising and audience segmentation.
Its typical duration is about 6 months, after which it expires automatically, though it can be renewed on a new visit if the visitor consents again.
Yes, any marketing cookie like this one must be explicitly listed in the cookie policy, including its purpose, provider, and duration, to meet regulatory requirements.