Analyze cross-partner behavior
Match your dataset with your partner's to compute overlap, and read the resulting insights.
Your goal
Find out how your audience overlaps with a partner's, and get insights on the common users, without either of you exposing raw data.
Prerequisites
An active Clean Room with your partner.
At least one dataset shared by you and one shared by your partner into that Clean Room.
Datasets matching
A datasets matching is the operation that overlaps two datasets to identify their common records - for example, common identifiers or users.
Choose matching keys and freshness
Select one or multiple matching keys if both datasets are Segment type - a matching key is selected automatically when at least one File type dataset is involved. Matching keys are grouped into Standard identifier and Clean room identifier; an incomplete clean room identifier is listed but cannot be selected. Then specify the identifier freshness that controls how recent online identifiers must be to be matched (this only applies to identifiers such as cookie, mobile ID, or device ID attached to a Segment-type dataset).
Scheduled refresh
When a matching is refreshed - manually or on schedule - the platform recomputes overlap metrics (count and rate), matching stats (total identifiers in the owner's environment and common identifiers), and pushes any new records or deletions to the activation platforms already connected to the matching. Track refresh activity in the Matching History tab: timestamp, initiator (a user or the scheduled system), the size of both datasets, and the number of common records.
Reading the result
Once a matching completes, open it from the Matched datasets tab to see:
General information - name, description, creation date, the user who triggered it, and expiration date.
High-level metrics - number of matched records, match rate, and refresh schedule.
Overview - information about the datasets used.
Matching history - the audit trail described above.
Matching stats - per identifier: whether it was used as a matching key, how many common identifiers exist in both datasets, and how many are available for common users in your own environment.
Insights - dashboards on the match, described below.
Insights
Match rate
The first metric to review is the match rate. The view depends on the matching setup:
Unitary match rate - appears when matching one Segment dataset against another Segment dataset. It is the percentage of common users or records between the two, based on the chosen matching keys, together with the absolute matched count. You can switch the comparison to show the rate relative to your partner's dataset instead of yours.
Bulk match rate - appears when matching a Segment dataset against a Segment catalog, sourced from a datamart or from a file. Results are shown per segment in the catalog rather than for the catalog as a whole, including each segment's match rate and absolute matched-user count.
Dashboards
Dashboards reporting on shared properties of common users between you and your partner can be created by the mediarithmics team on request: ask your Account Manager.
Troubleshooting
Why can't I see an Insights or Activation tab? The tab is only available when the datasets used in the matching are Segment type and have been shared with the corresponding purpose (Insights or Activation).
How long does a matching take? Typically under a minute, though larger datasets take longer.
Related pages
Last updated
Was this helpful?