Page Summary
-
Audience members are operated on and can optionally include destination references and consent settings.
-
Audience member data can be identified by user-provided data, PAIR IDs, or mobile device IDs.
-
PairData requires at least one PAIR ID, which are hashed and encrypted PII data.
-
MobileData requires at least one mobile ID, which are advertising ID/IDFA.
The audience member to be operated on.
| JSON representation |
|---|
{ "destinationReferences" : [ string ] , "consent" : { object ( |
destinationReferences[]
string
Optional. Defines which Destination
to send the audience member to.
data
. The type of identifying data to be operated on. data
can be only one of the following:userData
object (
UserData
)
User-provided data that identifies the user.
pairData
mobileData
object (
MobileData
)
Data identifying the user's mobile devices.
PairData
PAIR IDs for the audience. At least one PAIR ID is required.
| JSON representation |
|---|
{ "pairIds" : [ string ] } |
| Fields | |
|---|---|
pairIds[]
|
Required. Cleanroom-provided PII data, hashed with SHA256, and encrypted with an EC commutative cipher using publisher key for the PAIR
user list. At most 10 |
MobileData
Mobile IDs for the audience. At least one mobile ID is required.
| JSON representation |
|---|
{ "mobileIds" : [ string ] } |
| Fields | |
|---|---|
mobileIds[]
|
Required. The list of mobile device IDs (advertising ID/IDFA). At most 10 |
