Skip to content

Commit 6b6ca17

Browse files
authored
Note about array of objects in the builder.md
Engage does support nested traits, however, accessing objects nested in arrays is not currently supported by the Audience builder. To go a bit more into how arrays work with Engage, when arrays are sent, they get flattened into strings and stored in our backend. For building audiences based on array traits, all the same conditions that would work on strings will work on the array (since the array is now being treated as a string). Said in other words, when you try to access a trait within an object in an array in the Audience builder, you won't be able to access any of the nested objects. Instead, you can only use string operations like 'contains' and 'does not contain' to look for individual characters or a set of characters in the string.
1 parent 51bfae7 commit 6b6ca17

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

src/engage/audiences/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,8 @@ You can also build Audiences based on custom traits. These traits can be collect
3434

3535
You can also use computed traits in an Audience definition. For example, you can create a `total_revenue` computed trait and use it to generate an audience of `big_spender` customers that exceed a certain threshold.
3636

37+
> info ""
38+
> Engage does support nested traits, however, accessing objects nested in arrays is not currently supported by the Audience builder. When arrays of objects are sent, they will be flattened into strings. For building audiences based on array traits, all the same conditions that would work on strings will work on the array. Within the builder, you can only use string operations like 'contains' and 'does not contain' to look for individual characters or a set of characters in the flattened array.
3739
3840
### Funnel Audiences
3941

0 commit comments

Comments
 (0)