Skip to content

Commit 9fe655d

Browse files
authored
cleanup
1 parent 97d356c commit 9fe655d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/engage/faqs.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,17 +8,17 @@ redirect_from:
88

99
## Do you have an Audiences API?
1010

11-
Yes, more information about the Audience API can be found by visiting the [Segment Public API documentation](https://docs.segmentapis.com/tag/Audiences).
11+
Yes. You can learn more about the Audience API by visiting the [Segment Public API documentation](https://docs.segmentapis.com/tag/Audiences){:target="_blank"}.
1212

1313
## Can I programmatically determine if a user belongs to a particular audience?
1414

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:
15+
Yes. Eecause Engage creates a trait with the same name as your audience, you can query the Profile API to determine if a user belongs to a particular 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:
1616

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

21-
The following response indicates that Bob is indeed a high-value user:
21+
The following response indicates that Bob is a high-value user:
2222

2323
```json
2424
{

0 commit comments

Comments
 (0)