Comment on page
Audiences specified by a boolean query matching data in your identity graph
Once data is loaded into your DCN, you can build audiences using query expressions to select identity clusters based on advanced criteria, such as data source association and trait values. These audiences can be used in clean rooms, exports to your DSPs, DMPs or storage buckets and real time targeting via the Optable SDKs.
For example, one could define a query audience that semantically represents identity clusters that are members of audience #8 and include data from source #2.
Expressions can reference the following entities, also known as literals:
Expressions combine literals (and sub-expressions) with the following boolean operators:
- and: combines sub-expressions with the boolean "and", also known as logical conjunction.
- or: combines sub-expressions with the boolean "or", also known as logical disjunction.
- not: negates an expression with the boolean "not", also known as logical negation.
Note that query audiences have the following limitations:
- The expression can reference a maximum of 32 literals. This limits the depth and number of nodes in the query and ensures reasonable execution time.
$ optable-cli audience create "My Query Audience" \
'(or (audience 52) (source 2) (trait-eq "gender" "male"))'
orspecifies a logical OR between sub-expressions
andspecifies a logical AND between sub-expressions
audienceis followed by one argument, the integer ID of a matched audience, and specifies membership to a matched audience
Note that only a subset of expressions can be rendered in the DCN's query audience editor UI. If the expression of a query audience created with the CLI does not match what the audience editor UI expects, the a read-only JSON representation of the expression will be shown in the UI.
Last modified 1mo ago