| Audience | Platform admins |
| Prerequisites | Set up for platform admins and data teams |
Subsets restrict which rows of customer data each user can access in Customer Studio. Admins define subset filters based on attributes like region, brand, or consent, then grant access per teammate. Every audience those teammates build is automatically scoped to the rows they're permitted to see.
Overview
Customer Studio has several governance controls, each scoped to a different question. Subsets are the row-level control.
| To control… | Use |
|---|---|
| Which rows a user can work with | Subsets (this page) |
| Which columns or values are visible or syncable | Privacy levels and data masking |
| What can leave to a specific destination | Destination rules |
| Consent enforcement from OneTrust | OneTrust Snowflake Native App |
| Who can change schema, traits, or governance | Workspace roles |
Use subsets when different teammates should only work with part of your customer data. For example, a company with a global customer table can create a subset per region and assign each marketer to their region. Every audience they build is then scoped to those rows, so they can't sync customers outside it.
Common uses:
- Region — Scope each marketer to the geography they work in, so an EMEA marketer never builds against North American records.
- Brand or business unit — Give each team access only to the customers of the brand or product line they own.
- Consent — Scope access by opt-in type, so lifecycle marketers only see email opt-ins and performance marketers only see ad-targetable customers.
Subset categories vs. subsets
A parent model is segmented with subset categories and subsets. The category is the dimension (for example, Region); each subset is a value within it (North America, EMEA, APAC).
When a marketer builds an audience, they can pick more than one category and more than one subset within a category. A customer must match any subset selected within a category, and satisfy every category, to qualify for the audience.
Set up subsets
Subsets are configured under Customer Studio > Governance, on the Subset categories tab.
1. Select a parent model
Select the parent model you want to scope at the top of the page. Subsets apply to audiences built on that model.
2. Create a subset category
Click Add subset category, name the dimension (for example, Region or Consent), and add an optional description. Click Create subset category.
3. Decide whether the category is required
Open the category and turn on Required when a marketer must select a subset from it to build an audience on this parent model. Leave it off when the scoping is optional.
A required category with no accessible subset blocks a user entirely: if a marketer has access to no subset in a required category, they can't build audiences on that parent model.
4. Add subsets to the category
Click Add subset, name it (for example, Canada, Email opt-in), then click Add filter to define which customers it includes.
You define subset membership in the same visual builder used for audiences, with nested AND / OR logic. For how to build and combine conditions, see Audience filters.
5. Grant access and save
Select which users should have access to the subset, then click Create subset.
How subsets apply to audiences
When a marketer creates or edits an audience, they see any required categories and can choose the subsets they have access to. Their selections apply as base filters on top of the audience definition, so results never include rows outside the subset.
Because subsets scope what a user can see and build, they're the first place to look when a marketer's audience count is lower than expected. Membership can also be trimmed later by destination rules and consent filters.
Next steps
- Data masking to hide or block sensitive columns and values, even for users who can see the rows.
- Destination rules to control which records can reach a given destination.
- Build an audience to see how subset selections apply as base filters.