Piano DMP

Overview

Audience combines anonymous profiles identified by browser or app ID with known profiles identified by email or another unique identifier. Teams can use that combined view to build segments for targeting, analysis, or export, rather than restricting audience work to signed-in customers.

Data can come from web and app activity, first-party systems, campaigns, and second- or third-party sources, collected through tags, server-to-server connections, or APIs. Piano Audience APIs also accept online and offline customer data and allow customers to change their data-field structure. That flexibility helps accommodate varied inputs, but it also calls for a considered implementation.

Key features

Segmentation and enrichment

The Segment Builder creates audiences from anonymous or known profiles, including look-alike segments. Piano's content crawler uses NLP and LLM processing to classify content by entity, sentiment, and subject without manual tagging. That can reduce the effort of organizing content for segmentation, though the platform's stated role is to support those workflows, not to replace the need for suitable source data.

Activation and integrations

Audience segments can be used for targeting in Piano Activation, and Piano Composer can use them in tests and personalized experiences. Audience can also share segments and selected profile attributes with Composer, and export profile attributes to Piano Analytics. The Composer connection requires Piano's Support Team to configure it first, so teams should account for that dependency before planning activation.

Documented direct connections include Facebook, LinkedIn, Google Ads, Google Ad Manager, Xandr, Equativ, Adform, Platform161, and Nativo. Integration Designer can select and transform fields before sending data to an endpoint, file, Amazon S3, sFTP, or Google Cloud Storage on a chosen schedule. This suits teams that need controlled data movement as well as advertising activation.

Mobile and security

The implementation guide covers mobile SDK integration alongside web tracking scripts, event tracking, and data imports. Piano maintains an Information Security Management System based on ISO/IEC 27001:2022, a relevant assurance for organizations evaluating data infrastructure.

Tracking boundary

Piano says Audience does not track users across the Web. It does support consistent first-party behavior across multiple domains managed by one organization without third-party cookies. That boundary makes the product better suited to organization-owned properties than strategies dependent on cross-Web identity.

Pricing

Audience is paid, with custom pricing available by request. The product page directs prospective customers to request a demo rather than publishing a price, so buyers should expect a sales-led evaluation rather than a self-serve purchase.

The Composer integration is capped at 100 profile attributes and 100 custom segments per site group, subject to per-type limits. Those ceilings may be adequate for focused implementations, but organizations with larger Composer setups should confirm that their needs fit before committing.

Platforms

Audience is listed for Android, iOS, web, and API use. Mobile SDK integration and web tracking scripts support collection across those app and browser environments.

Who it's for

Audience is aimed at digital businesses using customer information for personalization, analytics, and export to other systems. It is a strong candidate for teams combining anonymous and known profiles across their own web and app properties, especially where Piano Activation, Composer, or Analytics is part of the stack. Teams that need cross-Web tracking, or want a product they can configure without relying on Piano Support for Composer, should look elsewhere.

Pros and cons

Pros

• Works across anonymous and known profiles: browser or app IDs can be combined with email or another unique identifier for broader audience building.
• Flexible collection and export: tags, server-to-server integrations, APIs, imports, and scheduled field transformations serve varied data pipelines.
• Useful Piano activation paths: segments can feed Piano Activation and Composer, while profile attributes can go to Piano Analytics.
• Automated content classification: NLP and LLM processing supports segmentation by subject, sentiment, and entities without manual tagging.

Cons

• No cross-Web tracking: the product's identity scope is limited to first-party behavior across an organization's own domains.
• Composer setup depends on support: Piano's Support Team must configure the connection before it can be used.
• Composer caps constrain scale: 100 profile attributes and 100 custom segments per site group, subject to per-type limits, may not suit larger deployments.
• Custom pricing adds a sales step: buyers cannot compare a published price or start with a stated free plan.

Alternatives

For a wider category comparison, browse Data Management Platforms or Customer Data Platforms.

• Adform DMP is another paid, custom-priced DMP; its stated package includes one standard data import integration and one standard taxonomy setup per account unless otherwise agreed.
• Informatica Product 360 is a paid product-data management option with deployment and integration choices, with pricing dependent on data volume, modules, deployment, integrations, and add-ons.
• Permutive is a paid option for Android, iOS, and web when those platforms are the priority.
• ArcSpan AMS is another paid web-based option.
• Audigent is another paid web-based option.
• Kubico uses a custom commercial structure with activation-volume and operator-size platform tiers, performance pricing tied to qualified FTDs, and no per-seat licensing.
• BlueData offers a freemium plan capped at 1 web user, 1 mobile user, 1 GB storage, and 500 submissions per month, making it the clearest fit for buyers who want to begin within explicit limits.
• Mingdata DMP is a paid web-based alternative with pricing details available by contacting Miaozhen.

Verdict

Choose Piano Audience if your digital business needs flexible profile unification, segmentation, and activation across its own web and app properties, especially within a Piano stack. Its strongest case is the combination of broad data intake, content enrichment, and Piano-side activation; its main reasons to look elsewhere are the lack of cross-Web tracking, support-dependent Composer setup, and custom pricing.