From 482cc1827849bb591e05c0e156ad8f65cc14bc0b Mon Sep 17 00:00:00 2001 From: dineshraj-arunmozhi <87521197+dineshraj-arunmozhi@users.noreply.github.com> Date: Thu, 22 Aug 2024 09:47:29 +0100 Subject: [PATCH 1/2] Update faqs.md public docs typo fix --- src/engage/faqs.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/engage/faqs.md b/src/engage/faqs.md index 0aa2cd7568..7f01e3df76 100644 --- a/src/engage/faqs.md +++ b/src/engage/faqs.md @@ -12,7 +12,7 @@ Yes. You can learn more about the Audience API by visiting the [Segment Public A ## Can I programmatically determine if a user belongs to a particular audience? -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: +Yes. Because 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 @@ -150,4 +150,4 @@ Based on Engage behavior, standard source events such as Page, Track and Identif ## Why can't I connect the audience/computed trait to an existing destination in my workspace? -Engage will not allow you to connect an audience/computed trait to a destination that is already linked to a [Connections-based source](https://segment.com/docs/connections/sources/). Instead, create a new instance of the destination with the correct Engage space selected as the data source. \ No newline at end of file +Engage will not allow you to connect an audience/computed trait to a destination that is already linked to a [Connections-based source](https://segment.com/docs/connections/sources/). Instead, create a new instance of the destination with the correct Engage space selected as the data source. From 51afaf3f60344e9626a1b78d8629344fe5e10da2 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 22 Aug 2024 12:31:02 -0400 Subject: [PATCH 2/2] relative link fix --- src/engage/faqs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/engage/faqs.md b/src/engage/faqs.md index 7f01e3df76..d8d2e8b842 100644 --- a/src/engage/faqs.md +++ b/src/engage/faqs.md @@ -150,4 +150,4 @@ Based on Engage behavior, standard source events such as Page, Track and Identif ## Why can't I connect the audience/computed trait to an existing destination in my workspace? -Engage will not allow you to connect an audience/computed trait to a destination that is already linked to a [Connections-based source](https://segment.com/docs/connections/sources/). Instead, create a new instance of the destination with the correct Engage space selected as the data source. +Engage will not allow you to connect an audience/computed trait to a destination that is already linked to a [Connections-based source](/docs/connections/sources/). Instead, create a new instance of the destination with the correct Engage space selected as the data source.