Choosing a customer data platform starts with the work you need to do. Bringing purchase records together, building advertising audiences and managing loyalty rewards involve different requirements, even when suppliers describe all three as customer engagement.

The guide to Customer Data Platforms Explained: Profiles, Audiences and Activation explains the foundations. This comparison looks at platform differences, current product names and questions to ask during an evaluation.

Which Customer Data Platform Fits Your Business?

Some products below focus on collecting and joining data. Others combine customer profiles with campaign delivery or specialise in loyalty and post-sales work. Choose a shortlist based on the tasks your business needs to complete and the systems already in place.

Twilio Segment

Twilio Segment collects customer events and routes data between systems. Its product range includes Connections for data collection and distribution, Unify for identity resolution and Engage for audience and journey activation.

Consider Segment when your website, app and business systems need a shared approach to collecting customer activity. A useful starting project is agreeing on consistent event names and properties before distributing those events to analytics and marketing tools.

What to Evaluate

Data collection: Ask the supplier to trace an event from your website or app through to each required destination. Include missing fields and duplicate events in the demonstration.
Customer identity: Segment’s identity resolution joins interactions using supplied identifiers. Test anonymous browsing, account creation and signed-in activity with your own matching requirements.
Data governance: Review how collection rules, access controls and consent choices fit your implementation. Governance features support your processes without guaranteeing compliant use.
Integrations: Verify the exact fields and actions supported by each connector. A listed integration is insufficient evidence of compatibility with your planned workflow.

Where Segment Fits

Segment belongs on a shortlist when data collection and distribution are central requirements and you have technical support for implementation. Marketing teams should also test the audience-building workflow rather than evaluating the event pipeline alone.

Separate the commercial scope of collection, identity resolution and activation. Request a written breakdown of the products required for your first use case, ongoing usage assumptions and responsibilities for maintaining the implementation.

Adobe Real-Time CDP on Adobe Experience Platform

Adobe Real-Time Customer Data Platform is the CDP application built on Adobe Experience Platform. The two names describe different layers of Adobe’s offering rather than a product before and after a rename.

Your website. Fully managed. €49/month. No setup fee. Hosting and updates included.

Profiles, Audiences and Activation

Adobe Real-Time CDP brings together known and anonymous data from enterprise sources. Its documented capabilities include identity management, customer profiles, segmentation, governance and audience activation through connected destinations.

Adobe offers B2C, B2B and B2P editions. The B2B edition addresses lead and account data, while B2P brings business and consumer contexts together. Choose the relevant edition before comparing functionality or requesting a quote.

A Useful Demonstration

Ask Adobe to demonstrate one audience built from your expected data sources. For example, a B2B evaluation might join account attributes with individual engagement and then pass the audience to an approved destination. Check which identifiers support the match and how exclusions are applied.

Include the receiving application in the demonstration. Audience creation, message delivery and measurement are separate steps, even when several products share a supplier.

Implementation Questions

Evaluate Adobe when you need governed profiles and audience activation across a substantial technology stack, particularly when existing Adobe applications form part of the project.

Ask who will design schemas, manage identity rules and maintain destination mappings. Confirm the required applications and licences individually rather than assuming every capability shown in an Adobe demonstration belongs to the CDP package.

SAP Engagement Cloud (fka. SAP Emarsys)

SAP renamed SAP Emarsys to SAP Engagement Cloud in February 2026. Existing Emarsys capabilities continue within the renamed solution.

The product focuses on customer engagement and personalised interactions. Compare this role separately from the underlying work of consolidating customer data across an enterprise.

Campaign Execution and Team Access

SAP Engagement Cloud builds on Emarsys’s personalisation and omnichannel engagement capabilities. SAP also introduced an enterprise edition with additional administration, governance and content and data controls for organisations operating across brands, regions and teams.

This makes the evaluation relevant to marketing teams seeking campaign execution alongside customer insight. Ask the supplier to show your actual campaign process, including approvals, regional variations and the information available to each team.

Questions for a SAP Evaluation

Establish where customer records originate and which system maintains the approved profile. Then ask how operational changes, such as an unavailable product or delayed order, enter a customer engagement workflow.

Check the difference between your current Emarsys entitlement and the proposed Engagement Cloud package. A renamed product does not establish which additional capabilities your contract includes.

For a business needing only a simple newsletter and a small contact database, first compare the work against existing marketing automation tools. A broader engagement platform needs a clear operational reason.

Salesforce Data 360 (fka. Salesforce Data Cloud)

Salesforce Data 360, previously called Data Cloud, is Salesforce’s data platform for connecting sources and creating unified profiles. Salesforce Customer 360 is the broader name for its connected customer applications.

Data 360 maps records into a common model and uses matching and reconciliation rules to create unified profiles. Those profiles support analysis, segmentation and activation across connected systems.

Marketing Cloud Personalization (fka. Evergage and Interaction Studio)

Evergage became Interaction Studio and then Marketing Cloud Personalization. Salesforce also offers Salesforce Personalization, a newer solution built natively on Data 360. These are separate products, so confirm which product and licence a proposal includes.

Ask which application stores profiles, which decides the experience and which delivers the message. Existing Marketing Cloud Personalization implementations need different evaluation questions from a new Salesforce Personalization project.

Where Salesforce Fits

Include Data 360 when sales, service and marketing records need to support shared customer workflows. An existing Salesforce estate provides a reason to evaluate the product, though the business case still depends on the data connections and actions required.

For an illustrative test, join a customer’s purchase record with an open service case and create an audience excluding unresolved cases from an upsell campaign. Inspect the matching rules and the delay between a case update and the audience change.

Check the Whole Cost

Request costs for data ingestion, processing, storage and activation where applicable, alongside implementation and related applications. Use your expected workload in the estimate. A demonstration using a small sample provides limited guidance about ongoing production costs.

Optimove

Optimove combines customer data with predictive analysis, campaign decisioning and multichannel execution. Its current positioning centres on helping marketing teams move from customer information to campaign action.

Evaluate Retention Workflows

Consider Optimove when your main requirement involves repeat purchases, customer retention or deciding which campaign a customer receives next. Its documented platform scope includes customer profiles, predictive capabilities, personalisation and campaign orchestration.

Start with a familiar business problem. An illustrative retail test might identify customers whose buying frequency has fallen and compare different follow-up approaches. Ask the supplier to demonstrate how the audience is defined, how customers leave the campaign and how overlapping campaigns are handled.

Measure the Decision

A predictive score needs an explanation your team understands. Ask what the score predicts, how often the underlying data changes and how performance is assessed against later outcomes.

Also define the comparison group before launching. A campaign reaching previous buyers should not receive credit for every subsequent purchase without examining what would have happened without the campaign.

Review how much channel execution you want inside Optimove and which existing tools should stay in place. Include data feeds, campaign ownership and reporting in the implementation plan. This provides a more useful comparison than a broad promise of improved return on investment.

FirstHive

FirstHive’s current documentation describes a CDP covering data ingestion, identity resolution, segmentation, analysis and activation. Its supported source categories include websites, mobile apps, CRM systems, enterprise systems and point-of-sale data.

Joining Online and Offline Records

FirstHive deserves evaluation when customer information sits across several operational systems. Its documentation describes configurable identity models and data cleansing alongside audience creation.

Prepare representative records before the demonstration. Include a customer using different contact details, an incomplete transaction and two people sharing an address. Ask the supplier to explain the resulting profiles and identify records requiring review.

For a retailer, a proposed test might combine online browsing with store purchases and use the resulting profile to avoid sending an irrelevant acquisition offer. Treat this as a test scenario rather than a promised result.

Analytics and Activation

FirstHive documents cohort analysis, dashboards and predictive models, including churn and customer lifetime value. Ask which features apply to your package and whether your historical data supports the intended analysis.

Request a complete example from source record to audience export or campaign action. Establish responsibility for data quality and confirm how a failed feed is detected. A complete feature list provides little help when nobody owns the daily checks or knows which data problems affect an active campaign.

Oracle Unity Data Platform (fka. Oracle CX Unity)

Oracle’s current product page uses the name Oracle Unity Data Platform. Earlier material refers to Oracle CX Unity and Oracle Unity Customer Data Platform.

The current offering includes customer and account profiles, identity resolution, audience creation and customer data preparation. Oracle positions the platform as a data foundation for marketing and related customer workflows.

Check the Timing of Each Step

Oracle’s documentation describes both scheduled processing and near real-time ingestion capabilities. Ask which processing methods apply to the proposed deployment rather than treating every stage as instantaneous.

Measure how long your workflow takes from a source event to an updated profile and then to an action in the destination. Specify the required timing for each use case. A daily audience for a monthly campaign has different needs from an offer responding to a customer’s current visit.

Review the data model as well. The records needed for an individual consumer campaign differ from the relationships needed for account-based marketing.

Where Unity Fits

Unity belongs on a shortlist when enterprise customer records need to support marketing, sales or service workflows, particularly where Oracle applications already perform relevant work.

Ask for a demonstration using one of your existing data sources and the actual destination application. Include export failures, changed customer details and duplicate records in the acceptance criteria.

Confirm which Unity version, related applications and integrations the proposal covers. Older documentation and a current product demonstration do not necessarily describe the same deployment scope.

Lytics, Part of Contentstack

Contentstack acquired Lytics in January 2025. Current Contentstack documentation describes Lytics CDP as a connection between behavioural data collection and content delivery across Contentstack products.

Customer Data for Content Decisions

Lytics collects visitor events through its JavaScript SDK and uses profiles and audience membership to support personalisation. Contentstack’s documentation describes connections between CMS content, visitor behaviour and targeting in Personalize.

Evaluate this approach when a central requirement involves showing relevant content during a website or app visit. A proposed publisher test might distinguish returning subscribers from first-time visitors and compare appropriate content or subscription messages.

Test the Content Workflow

Ask the supplier to demonstrate audience creation alongside the editorial process. Your team needs to understand who creates content variants, who approves targeting and what a visitor receives when no relevant profile exists.

Measure the outcome of the content decision. More clicks on a promoted article provide different evidence from additional paid subscriptions or retained customers.

Confirm the current commercial package through Contentstack. Historical Lytics descriptions help explain the product’s background, though purchasing decisions need the current platform scope, integrations and support terms. Include any existing CMS in the discussion rather than assuming the project requires a replacement.

BlueConic

BlueConic combines customer profiles, audience activation and first-party data collection. Its current product material emphasises B2C marketing teams, including retail, consumer goods and ecommerce businesses.

Profiles and Declared Preferences

BlueConic describes profile unification, identity resolution, consent management and a no-code interface for marketing users. Its Experiences features collect information through quizzes, product finders and preference flows.

These features merit attention when useful customer information is missing from your existing records. A preference answer provides different context from a page view, so define how each should influence an audience or experience.

For an illustrative skincare retailer, a product finder might collect a shopper’s stated preferences and use those answers alongside purchase history. Evaluate the information collected and the resulting recommendation separately.

What to Check

Marketer access: Ask a campaign manager to build a real audience and send the result to an existing tool.
Profile quality: Review how new answers affect existing attributes and whether conflicting records are visible.
Consent handling: Test a changed preference or withdrawn permission through the complete data flow.

Also establish who maintains the collection experience. A quiz needing regular product updates creates ongoing work, even when the audience-building interface is straightforward. Include those responsibilities in the business case.

ActionIQ and Uniphore CDP Agent

Uniphore acquired ActionIQ and incorporated its composable CDP capabilities into its wider offering. Uniphore’s ActionIQ page directs buyers to its current CDP Agent product.

Working With Existing Data Infrastructure

Uniphore describes a composable architecture connecting existing data with identity resolution, audiences, journey orchestration and analytics. Its CDP Agent material includes support for combining streaming and historical data.

Evaluate this approach when your organisation already has substantial customer data infrastructure and needs marketing access to those records. Ask the supplier to show which data stays in your environment and which information moves elsewhere during each operation.

Treat architectural claims as requirements to demonstrate. Confirm how the proposed setup handles your warehouse, access controls and production workload.

A Useful Evaluation Task

Give the supplier a business audience definition and ask a marketing user to build the audience without a new custom extract. Include a purchase exclusion and a consent condition, then inspect the resulting records.

Check query costs, refresh timing and destination delivery. Also identify which tasks still require a data engineer. A composable approach divides responsibilities across systems, so the proposal should name who owns failures at each boundary.

For an existing ActionIQ customer, request a clear account of product naming, support commitments and any proposed migration before comparing additional capabilities.

Bloomreach Marketing (fka. Bloomreach Engagement and Exponea)

Bloomreach acquired Exponea in 2021 and developed the offering under the Bloomreach Engagement name. In September 2026, Bloomreach renamed Engagement to Marketing across the product interface.

Bloomreach Marketing combines customer profiles, campaign automation and analytics. Consider the platform when the requirement includes running marketing programmes alongside customer data, especially when product information plays an important part in the message.

Connect Customer and Product Decisions

Bloomreach’s current documentation describes unified profiles built from behavioural and transactional data. The platform supports campaigns across email, mobile messaging, push notifications, web and paid media.

For an illustrative ecommerce test, use purchase history and current product information to build a follow-up campaign. Include unavailable products and recent returns so the demonstration covers reasons to withhold a recommendation.

Ask the supplier to distinguish the customer data layer from campaign delivery and other Bloomreach products. A search recommendation, an email recommendation and an automated journey need separate checks.

Campaign Operations

Have the team responsible for campaigns create a segment, prepare a message and apply an exclusion. Review approvals and reporting with the same care as the initial setup.

For AI-assisted features, inspect the generated audience or workflow before activation. Confirm which decisions are visible and editable. Judge the platform against the campaigns your team needs to run rather than a supplier’s headline claims about speed or revenue.

For Existing Exponea or Engagement Users

Older documentation and integrations still contain Exponea and Engagement references. Identify the contracted services and working integrations before discussing an upgrade.

Bloomreach’s September 2026 announcement describes the Engagement-to-Marketing change as a rename without changes to functionality or agreement terms. Keep working identifiers and tracking references unless specific migration guidance requires a change.

Odie (fka. Totango): Post-Sales Customer Intelligence

Totango now operates under the Odie name. Its current offering describes a Customer Knowledge Engine for B2B post-sales teams, combining customer data with the knowledge held by customer-facing employees.

The rebrand accompanies a revised product offering. Evaluate the current Odie platform against your requirements rather than assuming every historical Totango feature carries over unchanged.

Start With the Post-Sales Requirement

Evaluate Odie when the main problem involves understanding existing customer accounts and supporting post-sales work. Its current material describes analysis of sources such as CRM records, product usage, emails, calls and meetings.

A relevant test would focus on a customer account needing attention. Ask the supplier to explain which evidence supports the assessment and what action a customer success manager should take next.

Historical Totango descriptions emphasise account health, onboarding, retention and expansion. Existing customers should confirm which current product and support arrangements apply to their deployment.

Avoid Comparing Different Jobs

A post-sales team reviewing renewal risk has different requirements from a marketing team building an anonymous website audience. Assess the relevant product against the work assigned to the buying team.

If both requirements exist, document the exchange between systems. Establish which source owns account information and which owns campaign audiences. Do not assume one customer-facing application replaces every other use of customer data.

Tealium AudienceStream

Tealium AudienceStream builds persistent customer profiles and audiences from event and customer data. Its documented capabilities include identity resolution, configurable profile attributes and actions in connected marketing systems.

From Event to Action

AudienceStream merits evaluation when data arrives from several sources and needs to trigger consistent actions across existing tools.

Ask Tealium to demonstrate a complete event-based workflow. For example, a completed purchase should update the relevant profile and affect an acquisition audience in the receiving system. Measure the elapsed time across the entire route rather than reviewing a profile update alone.

Include the absence of an identifier in the test. Your team needs to understand which activity stays separate and what changes when a known identifier appears.

Implementation and Maintenance

Do not assume deployment involves little technical work. Define the event specification, collection method, identity rules and destination mappings before estimating the effort.

Review the relationship between AudienceStream and any other Tealium products required by the proposal. Confirm whether collection, transformation and predictive functions sit inside the quoted scope.

Assign responsibility for connector failures and unexpected audience changes. Ask how your team investigates a customer receiving the wrong message and whether the relevant profile and event history provide enough evidence to trace the cause.

Treasure AI (fka. Treasure Data): Treasure Data CDP

Treasure Data adopted the Treasure AI business brand in April 2026. Its customer data platform continues to appear under the Treasure Data name within the broader Treasure AI offering.

Older material also uses Arm Treasure Data. These names belong to the same supplier’s history rather than separate CDP alternatives.

Unification, Audiences and Activation

Treasure Data CDP provides the customer data foundation for unified profiles, audience creation and activation. Treasure AI Studio adds a conversational workspace for marketing and data teams, including reviewable outputs before activation.

A suitable evaluation starts with the records you need to join. Ask for a demonstration combining historical transactions with more recent interactions, then inspect the audience produced from those records.

Include your data team in the assessment. Establish who maintains source connections, identity logic and the definitions used in reports. Marketing access to a finished profile does not remove those responsibilities.

Review AI-Assisted Work

Give an AI-assisted workflow a specific brief and compare the proposed audience with a manually checked definition. Review exclusions, timing and the underlying records before approving an action.

Ask which features are included, which require additional products and how usage is measured. Also request a clear distinction between the capabilities available in your proposed deployment and future plans.

For Existing Treasure Data Users

Confirm the products covered by your agreement before evaluating additional Treasure AI capabilities. The business rebrand does not establish which new features belong to an existing package.

Keep earlier names in your internal documentation where they help identify contracts or integrations. Use the current supplier and product names when requesting proposals so the commercial scope is clear.

Redpoint Customer Data Platform

Redpoint focuses on customer data preparation and use across enterprise customer experiences. Its documentation describes a central platform for joining data from several sources and supporting audiences and customer journeys.

Prioritise Data Quality

Include Redpoint when inconsistent or fragmented customer records form a substantial part of the problem. Evaluate the quality of the resulting profile before judging campaign features.

Use difficult sample records in the demonstration. Include duplicate customers, changed addresses, inconsistent formatting and an incorrect match. Ask how the proposed implementation identifies problems and how authorised users correct them.

For an illustrative retail workflow, define the record needed to recognise a returning customer across store and online transactions. Then specify which information the campaign should use and which information should stay restricted.

Activation and Support

Trace a segment into the intended destination. Establish the refresh schedule, supported attributes and response when delivery fails.

Ask the supplier to explain the proposed architecture and operational responsibilities. Include APIs, access permissions, staff training and support arrangements in the proposal rather than assuming every service belongs to a standard package.

A useful pilot should leave your team with documented matching rules and a repeatable activation process. Evaluate the time needed to maintain those assets alongside the platform’s functional capabilities.

Optimizely Data Platform (fka. Zaius)

Optimizely Data Platform, often shortened to ODP, was previously known as Zaius. The platform connects customer data with audience segmentation and activation across Optimizely’s wider products and connected tools.

Data for Experimentation and Personalisation

Optimizely’s current product material describes identity-resolved profiles, predictive segments and activation across content, commerce and experimentation.

Consider ODP when a central requirement involves using customer data to decide who sees an experience or enters an experiment. Ask the supplier to demonstrate a segment built from relevant customer attributes and activated in the exact product you intend to use.

For an illustrative test, compare a relevant returning-customer message with the existing page experience. Define the outcome before the test and include an appropriate comparison group.

Separate Product Capabilities

Confirm where experimentation, content delivery and messaging occur. Do not assume every capability in the Optimizely portfolio belongs to the data platform licence.

Review customer identifiers and integration requirements with your technical team. Older implementations and documentation still use Zaius terminology, so product history helps explain names appearing in tracking code or records.

Include data collection, segment refresh timing and ongoing administration in the project estimate. A successful demonstration should show the complete route from source event to the experience received by the customer.

SessionM: Loyalty and Customer Engagement

SessionM is now part of Capillary Technologies following its acquisition from Mastercard. The platform retains the SessionM name within Capillary’s loyalty and customer engagement portfolio.

Evaluate the Loyalty Programme

SessionM deserves consideration when the requirement centres on membership, rewards and loyalty operations. Its documentation includes customer profiles, audiences, campaigns, points, offers, reward stores and loyalty rules.

Begin with programme mechanics rather than a generic customer profile demonstration. Define how members earn rewards, how returns affect balances and which transactions qualify. Then ask the supplier to run those rules using representative transactions.

Include a failed or repeated transaction in the test. Your team needs a clear process for investigating a disputed reward and correcting the relevant record.

Connect Loyalty With Marketing

Map the information needed by your messaging and analytics tools. A member’s reward balance and a marketing permission serve different purposes, so specify how each enters an audience or campaign.

Confirm the current commercial and support arrangements through Capillary. Existing SessionM customers should review any proposed changes against their current deployment.

For a business seeking only website event collection or general audience distribution, assess those requirements separately. Loyalty programme operations provide the clearest reason to include SessionM in this comparison.

BlueVenn: Check Current Availability

Upland acquired BlueVenn in 2021. The acquisition announcement described a CDP combining customer data unification, analysis and marketing automation.

Treat those descriptions as historical background when reviewing an existing deployment or an older supplier shortlist.

Questions for an Existing Deployment

Ask Upland to confirm the product’s current sales availability, supported version and development roadmap. Request written details of support terms, security maintenance and any recommended migration route.

Review the integrations your business uses today. Document source systems, customer identifiers, scheduled processes and campaign destinations. This inventory provides a basis for evaluating either continued use or a replacement.

If your organisation has no existing BlueVenn deployment, establish current availability before investing time in a detailed feature comparison. Historical acquisition material does not establish a current purchasing option.

Selecting the Right CDP for Your Business

Start with a small set of measurable tasks. A platform evaluation becomes easier when every supplier receives the same source records, audience definition and acceptance criteria.

Define the First Business Requirement

Choose a concrete problem such as combining online and store purchases, removing recent buyers from acquisition campaigns or reducing manual audience exports.

Record the source systems, required identifiers and destination. Then define the timing. Specify whether a daily update meets the need or whether an action must happen during a current customer interaction.

For a smaller business, first test whether existing CRM and marketing automation tools address the requirement. Add a CDP when the missing capability and expected value are clear.

Test the Work Your Team Will Perform

Ask a prospective user to build an audience, inspect an individual record and investigate an unexpected result. Include the staff who will maintain integrations as well as the marketers using finished profiles.

Measure routine work during the pilot. Record the time needed to create an audience, resolve a data problem and send an approved segment to the destination. These observations support a practical comparison of usability.

Use the same difficult records with each supplier. A polished demonstration using clean sample data provides limited evidence about your implementation.

Estimate Cost and Growth Together

Request a written estimate using current volumes and a realistic growth scenario. Include profiles, events, storage, processing, destinations, messaging and warehouse charges where relevant.

Add implementation, training and ongoing support. Identify the work your own staff must perform and the assumptions behind any supplier timeline.

Also review exit requirements. Ask how customer data, audience definitions and operational records are exported, which formats are supplied and what assistance costs.

Review Privacy and Security in the Proposed Setup

Examine access controls, data location, retention settings and deletion workflows against your organisation’s requirements. Request current supporting documentation and involve the people responsible for approving data use.

Test a changed permission and a deletion request through every connected system. Verify how the proposed setup records the request and how downstream destinations receive the change.

Complete the pilot with a documented owner for each data source, identity rule and live audience. Specify monitoring, incident handling and the evidence required before the first production campaign goes live.