Partner Management allows for ease of configuration of pipelines, where a customer can send data hosted in Salesforce Audience Studio to a supported activation partner. Audience Studio allows for the configuration of multiple pipelines between an organization to a particular partner. Each individual pipeline is called an integration partner account.
When requesting a new integration partner account, the customer should indicate if the partner seat is “owned” or “shared”. Seats that are owned are seats that are managed specifically by the customer or perhaps by an agency partner on behalf of the customer. Historically, Audience Studio treated all seats as “owned”. “Shared” seats on the other hand are used by business partners but not controlled by the data owner, the Audience Studio client making the segment available.
To enable customers to comply with GDPR, Audience Studio implemented a Consumer Rights Management framework where certain Audience Studio functionality is gated based on specific consumer consents. One of the consent flags is Data Sharing. The Data Sharing flag is used in two places: 1) sending data to a second party via Data Studio, and 2) sending data to another entity via a “shared” seat in Partner Management. If no Data Sharing consent is present, no data will be send to "shared seats".
It is entirely up to the customer to determine and indicate in the Audience Studio UI whether a new integration partner account will connect to a seat that is “owned” or “shared”. Therefore, when making new integration requests via the Audience Studio portal, please indicate if the seat is owned / managed on your behalf or if you would like that seat to be marked as a “shared” seat so that the Data Sharing flag is respected. For advice on which designation to give to a seat for a particular use case, customers should consult with their legal department.
Here are some typical examples:
- Publisher A sending segments a DSP seat owned and operated only by them
- Marketer B sending segments to a DSP seat managed by Agency C to run campaigns for Marketer B
- Publisher A sending segments to a DSP seat owned by Marketer B, for Marketer B to run campaigns.
- Marketer B sending segments to a DSP seat of Marketer D, for Marketer D to run campaigns
- Marketer B sending segments to a DSP seat managed by Agency C to run campaigns for Marketer D