From 97d356c4f73d4120e877b4f83cb0d3a85d597dbb Mon Sep 17 00:00:00 2001 From: maleman842 <79479130+maleman842@users.noreply.github.com> Date: Thu, 9 May 2024 12:12:46 -0700 Subject: [PATCH 1/2] Update Engage faqs.md Updating Engage FAQs to correct that an audience api exists --- src/engage/faqs.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/engage/faqs.md b/src/engage/faqs.md index c5202d0d9b..e4585d743e 100644 --- a/src/engage/faqs.md +++ b/src/engage/faqs.md @@ -8,9 +8,11 @@ redirect_from: ## Do you have an Audiences API? -You can add, remove, and modify audiences only by using the Engage in-app audience builder. +Yes, more information about the Audience API can be found by visiting the [Segment Public API documentation](https://docs.segmentapis.com/tag/Audiences). -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 `bob@example.com` is a member of your `high_value_users` audience, you could query the following profile API URL: +## Can I programmatically determine if a user belongs to a particular audience? + +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 `bob@example.com` is a member of your `high_value_users` audience, you could query the following profile API URL: ``` https://profiles.segment.com/v1/namespaces//collections/users/profiles/email:bob@segment.com/traits?include=high_value_users From 9fe655d9d7cf57b64779195c3040ab586c110217 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Tue, 14 May 2024 13:09:46 -0500 Subject: [PATCH 2/2] cleanup --- src/engage/faqs.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/engage/faqs.md b/src/engage/faqs.md index e4585d743e..6c43e17c70 100644 --- a/src/engage/faqs.md +++ b/src/engage/faqs.md @@ -8,17 +8,17 @@ redirect_from: ## Do you have an Audiences API? -Yes, more information about the Audience API can be found by visiting the [Segment Public API documentation](https://docs.segmentapis.com/tag/Audiences). +Yes. You can learn more about the Audience API by visiting the [Segment Public API documentation](https://docs.segmentapis.com/tag/Audiences){:target="_blank"}. ## Can I programmatically determine if a user belongs to a particular audience? -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 `bob@example.com` is a member of your `high_value_users` audience, you could query the following profile API URL: +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 `bob@example.com` is a member of your `high_value_users` audience, you could query the following Profile API URL: ``` https://profiles.segment.com/v1/namespaces//collections/users/profiles/email:bob@segment.com/traits?include=high_value_users ``` -The following response indicates that Bob is indeed a high-value user: +The following response indicates that Bob is a high-value user: ```json {