Skip to content

Commit a336b3a

Browse files
authored
More edits
1 parent 9d003d4 commit a336b3a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/engage/audiences/account-audiences.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ Use-cases for account-level computed traits include:
7070

7171
To associate users to an account with SQL traits, you must return both the `group_id` and `user_id` in the account level SQL trait. This fires a Group call which Segment uses to add users to groups in destinations.
7272

73-
There is a limitation on Segment end when a group (account) contains more than one user, the query will return duplicate group_ids (mapped to unique user_ids). Segment won't allow us to return duplicate group_id's in the Group(account level) SQL trait., So we can't map the users to the accounts on many-to-many situation.
73+
When a group (account) contains more than one user, the query returns duplicate `group_id`s (mapped to unique `user_id`s). However, Segment doesn't return duplicate `group_id`s in the account-level SQL trait. As a result, you can't map users to accounts in a many-to-many situation.
7474

7575
### Use account-level computed and SQL traits as account-level audience conditions
7676

0 commit comments

Comments
 (0)