Skip to content

Commit 97d356c

Browse files
authored
Update Engage faqs.md
Updating Engage FAQs to correct that an audience api exists
1 parent 9ab735d commit 97d356c

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

src/engage/faqs.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,11 @@ redirect_from:
88

99
## Do you have an Audiences API?
1010

11-
You can add, remove, and modify audiences only by using the Engage in-app audience builder.
11+
Yes, more information about the Audience API can be found by visiting the [Segment Public API documentation](https://docs.segmentapis.com/tag/Audiences).
1212

13-
However, you can programmatically query the Profile API to determine if a user belongs to a particular audience because Engage creates a trait with the same name as your audience. For example, to determine if the user with an email address of `[email protected]` is a member of your `high_value_users` audience, you could query the following profile API URL:
13+
## Can I programmatically determine if a user belongs to a particular audience?
14+
15+
Yes, you can programmatically query the Profile API to determine if a user belongs to a particular audience because Engage creates a trait with the same name as your audience. For example, to determine if the user with an email address of `[email protected]` is a member of your `high_value_users` audience, you could query the following profile API URL:
1416

1517
```
1618
https://profiles.segment.com/v1/namespaces/<namespace_id>/collections/users/profiles/email:[email protected]/traits?include=high_value_users

0 commit comments

Comments
 (0)