Salesforce retired Audience Studio, the data management platform formerly known as Krux, on February 1, 2024. The retirement did not end audience management, but it clarified how much the job had moved beyond the traditional DMP.
Brands still need to build audiences, manage media reach, control frequency, suppress existing customers, and measure outcomes. The durable foundation for those jobs now begins with governed first-party data and resolved identity, then connects to the identifiers, platforms, and measurement methods available for each channel.
Key Takeaways
Salesforce Audience Studio is no longer available, so its retirement should be treated as a completed platform transition rather than a prediction about the DMP category.
Traditional DMPs were designed primarily for pseudonymous advertising data and audience operations, while customer data platforms work with persistent first-party profiles across a broader set of business uses.
A first-party strategy should not depend on one browser's cookie roadmap; signal availability, consent, platform access, and measurement coverage vary across the advertising ecosystem.
A DMP migration should preserve audience logic, permissions, destination mappings, measurement baselines, and operating knowledge, not simply move records into a new tool.
What Audience Studio's retirement confirmed
Salesforce's retirement notice states that Audience Studio products were retired on February 1, 2024 and that associated customer data would be deleted according to its trust and compliance documentation. For former customers, the operational migration deadline has passed.
The broader lesson remains useful. A platform built around third-party advertising signals cannot serve as the only source of customer understanding when brands also need purchase history, loyalty, service activity, permissions, current behavior, and business outcomes.
The DMP really only serves to fuel a piece of media optimization for a fraction of media — and that fraction is based on third-party cookies, which are becoming obsolete.
DMPs and customer data platforms solve different jobs
A data management platform traditionally organizes pseudonymous audience and device data for advertising. It can support audience enrichment, prospecting, suppression, media buying, and frequency management within the partners and identifiers it supports.
A customer data platform focuses on a brand's customer data. It connects records from operational and engagement systems, resolves identities, builds governed profiles, creates audiences, and makes approved data available to marketing, analytics, service, advertising, and other workflows.
The categories can overlap, and neither label guarantees a specific architecture. Buyers should evaluate data ownership, identity methods, governance, latency, destination support, measurement, and portability instead of assuming that one category name supplies every capability.
The third-party cookie story changed, but the risk did not disappear
The original article assumed that Chrome would eliminate third-party cookies. Google later changed course and said it would maintain its current approach of giving people a choice in Chrome instead of introducing a new standalone prompt.
That change does not restore a universal identifier. Other browsers restrict third-party cookies, people can opt out, mobile environments use different controls, walled gardens limit data access, and privacy requirements vary by market and use case. A durable strategy therefore uses first-party identity as its base and treats every external identifier as conditional infrastructure.
What DMPs still get right
DMP-era workflows addressed real media problems. Brands still need audience reach, suppression, frequency controls, enrichment, prospecting, and connections to programmatic partners. Those requirements should not be discarded during migration.
The better question is where each job should live. A customer-data foundation can own customer identity, permissions, audience definitions, and outcome data, while advertising platforms, clean rooms, data partners, and alternative identifiers perform the functions they are designed to support.
A CDP powers measurement based around the customer, focusing on behavior and outcomes, so that brands can have a clear view of what’s working and what isn’t to power adaptation and innovation.
What to preserve when replacing a DMP
Inventory the current operating model before selecting technology. Preserve the business meaning and controls behind the following assets:
Audience definitions, exclusions, suppression rules, and refresh requirements.
Data sources, permitted uses, consent signals, retention rules, and regional restrictions.
Destination mappings, accepted identifiers, match expectations, delivery cadence, and failure handling.
Campaign, reach, conversion, and outcome data used for measurement.
Historical baselines, test designs, taxonomies, owners, approvals, and audit requirements.
Some assets may no longer be usable under current contracts or policies. The inventory should distinguish what can be migrated, what must be rebuilt, and what should be retired.
How to evaluate a customer-data foundation
Identity you can inspect and govern
Identity resolution should connect known and anonymous records only where the data and permissions support it. Test false merges, missed matches, shared identifiers, householding, persistence, explainability, and the ability to tune identity for different business purposes.
Profiles built from useful customer context
A profile should combine the history, attributes, permissions, derived measures, and current signals needed for a decision. Completeness should be defined by the use case, not by an impossible promise to capture every interaction.
Activation that matches each destination
Verify supported destinations, identifiers, payloads, refresh cadence, retries, logs, deletions, and opt-out enforcement. No platform can send every type of data to every destination under every contract and policy.
Measurement tied to business outcomes
Connect available exposure, campaign, conversion, transaction, and customer data so teams can compare activity with outcomes. Separate platform reporting, attribution, experiments, and modeled analysis because each method answers a different question.
Portability and operating control
Document where data resides, how it moves, who can use it, how definitions are versioned, and how the organization can retrieve its data and logic. Independence depends on contracts and architecture as much as vendor category.
Build beyond the DMP use case
Amperity's Customer Context Platform combines first-party identity, customer history, current signals, governance, intelligence, and activation. It can support paid-media workflows while giving analytics, marketing, service, and AI systems a shared customer-data foundation.
A successful transition should make customer context more dependable and usable, not simply replace one media tool with another. Start with the required decisions and workflows, then test the data, identity, permissions, destinations, and measurement path end to end.
See how Amperity can support your first-party data and paid-media strategy. Request a demo using your audience, identity, governance, activation, and measurement requirements.