Use cases
Collaborate supports three core use cases. A partnership can be used for one or all three, depending on what you and your partner agree to enable.Discover
Understand how your audience overlaps with your partner’s — and what those shared customers look like. Run an overlap analysis to see how many records match between the two datasets, broken down by shared demographic or behavioural attributes (such as gender, age group, or purchase category). This tells you the size and composition of your shared audience without either side exposing individual records.Example: A retailer (Contributor) and an FMCG brand (Subscriber) use overlap analysis to understand what share of the brand’s customer base shops at the retailer, and which product categories those shared customers buy.
Activate
Save matched segments as audiences and push them to advertising channels for targeting. Once you have run an overlap analysis, the Subscriber can save the matched population — or specific breakdowns of it — as an audience in Zeotap CDP. That audience can then be activated to any channel the Contributor has permitted, such as a DSP or paid social platform.Example: A media owner (Contributor) allows an advertiser (Subscriber) to save the overlap between the advertiser’s high-value customers and the media owner’s addressable inventory, and activate it directly to a campaign on a permitted ad platform.
Suppress
Identify customers in your dataset who were not reached by your partner — for exclusion targeting or incrementality measurement. The suppression view shows the non-overlapping portion of the Subscriber’s audience. This is useful for building exclusion lists (avoid showing ads to people already reached), measuring incremental reach (how much new audience did the partnership unlock?), and managing frequency across channels.Example: A brand (Subscriber) uses suppression to identify which of their CRM customers have not been exposed to a partner publisher’s campaign, then activates that segment separately to close the coverage gap.
What you can do in Collaborate
How it works
A Collaborate partnership always involves two roles.The Contributor is displayed as Publisher in some parts of the product.
- The Contributor creates the partnership — an invitation email is sent immediately to the CDP admins of the Subscriber organisation.
- The Contributor configures which attributes to share and sets privacy controls.
- The Subscriber accepts the invitation — the partnership status moves to In Setup.
- The Subscriber maps their identity keys to the Contributor’s, completing their configuration.
- Once both sides have submitted, the partnership becomes Active.
- The Subscriber runs analysis to view overlap/suppression results and activate relevant segments.
Partnership status lifecycle
Which role are you?
I own the data I want to share → Contributor Guide
Create the partnership, select attributes to share, set privacy and activation controls, and manage the partnership throughout its lifetime.
I want to analyse a partner's data → Subscriber Guide
Accept an invitation, map your identity keys, run overlap analysis, and save matched audiences for activation.
Prerequisites
Complete these before attempting to create or join a partnership. Admin tasks — completed once per organisation- Confirm your organisation is on the Zeotap composable CDP plan (a warehouse-native BigQuery setup is required for both sides). To be a Subscriber, your organisation must be composable.
- Request the Collaborate module to be enabled for your org, and enable collaboration consent — contact your Zeotap account team. Only consenting organisations appear in the partner selection dropdown.
- Confirm at least one composable data source is onboarded in your org.
- Confirm that source contains at least one ID-type attribute (for example, Email MD5 or Phone MD5) or a primary key column, to serve as the join key.
- Confirm you have onboarded a dataset as a customer parent model in your org. This is required for overlap analysis — the join key of the customer parent model lets the system resolve user profiles for matching.
- Ensure your org’s CDP admins are monitoring their inbox — they receive the invitation email when a Contributor creates a partnership with your org.