Audience Collaboration
This guide describes the audience collaboration use case pattern, which uses Segment Match in Real-Time CDP and Adobe Experience Platform to share and match audience segments across sandboxes or organizations in a privacy-safe manner. It is designed for solution architects, marketing technologists, and implementation engineers who need to understand what this pattern does, the business objectives it supports, the tactical use cases it enables, and the Adobe applications involved.
Segment Match enables two or more Experience Platform organizations (or sandboxes within an organization) to collaborate on audience data by sharing segment membership information without exposing underlying PII. Participants can estimate overlap, share audiences, and activate matched profiles to downstream destinations.
Use case pattern
This use case follows the Audience Collaboration pattern.
Share and match audience segments across sandboxes or organizations using Segment Match.
Execution plan: Segment Selection > Match Configuration > Overlap Estimation > Audience Sharing > Activation
Use case overview
Organizations increasingly need to collaborate on audience data with partners, subsidiaries, or across business units while maintaining strict privacy controls. Audience collaboration addresses this need by enabling secure segment sharing through Segment Match – a feature within Real-Time CDP that allows two or more Experience Platform organizations (or sandboxes) to exchange audience membership information using hashed, privacy-safe identifiers.
The business scenario typically involves one organization (the sender) that has built a valuable audience segment and wants to share it with a partner organization (the receiver) for joint targeting, suppression, or enrichment. Before sharing, both parties can estimate audience overlap to assess value. Once shared, the receiving organization can activate the matched audience through their own destinations.
This pattern is distinct from standard audience activation because it operates between organizations or sandboxes rather than to external advertising or marketing destinations. It is also distinct from data clean rooms or third-party collaboration platforms because it operates natively within the Adobe ecosystem using Experience Platform identity infrastructure.
Key business objectives
The following business objectives are supported by this use case pattern.
Acquire new customers
Expand the customer base through targeted acquisition campaigns, lookalike audiences, and paid media optimization. Audience collaboration enables organizations to discover new prospect pools by matching their segments against partner audiences, identifying high-value overlap, and reaching net-new customers through joint activation.
- KPIs: New Customers, Customer Acquisition Cost, Prospect/Lead Conversion
- Acquire new customers
Reduce customer acquisition cost
Improve targeting efficiency, suppress existing customers from acquisition campaigns, and optimize media spend. By sharing suppression segments across organizations or business units, teams can avoid wasted spend on already-converted customers and focus budgets on genuinely new prospects.
- KPIs: Customer Acquisition Cost, Cost Per Lead, Efficiency
- Reduce customer acquisition cost
Optimize marketing spend and ROI
Improve return on marketing investment through better targeting, attribution, audience suppression, and budget allocation. Segment Match enables cross-organization audience suppression and joint targeting that reduces duplication and improves precision.
- KPIs: Cost Savings, Customer Acquisition Cost, Incremental Revenue
- Optimize marketing spend and ROI
Example tactical use cases
- Publisher-advertiser audience matching – A brand shares its high-value customer segment with a media publisher to estimate overlap and target matched users with personalized ads, improving campaign relevance without exposing PII.
- Cross-brand suppression within a holding company – Multiple brands under a parent organization share customer segments to suppress existing customers of sister brands from acquisition campaigns, reducing wasted ad spend.
- Retail media network audience enrichment – A retailer shares purchase-based segments with CPG brand partners, enabling the brands to target proven buyers on the retailer’s media network with higher conversion rates.
- Co-marketing partner audience discovery – Two non-competing brands evaluate audience overlap to assess partnership potential before launching a joint campaign, using overlap estimation to validate audience alignment.
- Data cooperative segment sharing – Organizations in a data cooperative share hashed audience segments to expand targeting reach while maintaining privacy compliance and data governance controls.
- Multi-sandbox audience federation – A global enterprise shares audience segments across regional sandboxes to enable consistent customer targeting across markets while respecting regional data residency requirements.
- Loyalty program cross-partner activation – A loyalty coalition shares loyalty tier segments with participating merchants so each partner can offer tier-appropriate promotions to the shared customer base.
- Measurement and attribution collaboration – An advertiser shares a conversion segment with a media partner so the partner can measure campaign effectiveness by matching exposed users against converters.
Key performance indicators
The following KPIs help measure the success of audience collaboration implementations.
Applications
The following applications are used in this use case pattern.
- Real-Time CDP – Provides the Segment Match capability for privacy-safe audience sharing, audience evaluation for segment creation, and destination activation for downstream use of matched audiences.
- Adobe Experience Platform – Provides the foundational data infrastructure including identity resolution, profile unification, data governance, and consent enforcement that Segment Match depends on.
Related documentation
The following resources provide additional detail on the capabilities used in this use case pattern.