From 79001628abb7ef2e090b0b12325016576a695b7b Mon Sep 17 00:00:00 2001 From: Brandon Caudillo <52050659+bcaudillo@users.noreply.github.com> Date: Thu, 8 Feb 2024 20:07:36 -0700 Subject: [PATCH 1/6] Add details for support on this destination --- src/connections/destinations/catalog/actions-pendo-web/index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/connections/destinations/catalog/actions-pendo-web/index.md b/src/connections/destinations/catalog/actions-pendo-web/index.md index 283dd901c8..c0542a7144 100644 --- a/src/connections/destinations/catalog/actions-pendo-web/index.md +++ b/src/connections/destinations/catalog/actions-pendo-web/index.md @@ -11,6 +11,8 @@ hide-dossier: true [Pendo](http://www.pendo.io/){:target="_blank"} combines powerful software usage analytics with in-app guidance and user feedback capabilities, enabling even non-technical teams to deliver better product experiences to their customers or employees. +This destination is maintained by Pendo. For issues with the Pendo Web (Actions) destination please reach out to [Pendo's support team](https://support.pendo.io/hc/en-us/articles/360034163971-Get-help-with-Pendo-from-Technical-Support) + > success "" > **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Pendo Web (Actions) Segment destination. There's also a page about the [non-Actions Pendo destination](/docs/connections/destinations/catalog/pendo/). Both of these destinations receives data from Segment. From f9be96db172456ff4605fd7bf76d0576dbeeac06 Mon Sep 17 00:00:00 2001 From: Esteban Gonzalez Corti Date: Tue, 13 Feb 2024 10:51:55 +1100 Subject: [PATCH 2/6] Add Troubleshooting for invalid list ID.md Typical error that comes up when the client deleted the audience in the destinaton --- .../destinations/catalog/adwords-remarketing-lists/index.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/connections/destinations/catalog/adwords-remarketing-lists/index.md b/src/connections/destinations/catalog/adwords-remarketing-lists/index.md index 306bc29469..b374912831 100644 --- a/src/connections/destinations/catalog/adwords-remarketing-lists/index.md +++ b/src/connections/destinations/catalog/adwords-remarketing-lists/index.md @@ -127,6 +127,10 @@ If a user has more than one email address or IDFA on their account as `external_ Make sure that this destination was created in [Engage](/docs/engage/) as it requires additional event data not available in standard destinations. +### Invalid user list ID error in Event Delivery + +When you first connect the destination into an audience, a call to the destination will be triggered to create the audience downstream. Once that succeeds and the audience is created, the destination API returns an ID for that audience to Segment. Later on, for subsequent updates to the audience in the destination (adding/removing users), Segment uses this ID to send the request to it. This error usually means that the audience ID Engage is using no longer exist in the destination. To sort this issue, you will need to either recreate the audience or create a *new instance* of the destination and link it to the audience. Removing and re-adding the same instace of the destination will not work. + ## FAQs #### What Google Ads campaigns does Engage support? From 94f7967d519d3f8a068e6b7ebd702eb4e023eaec Mon Sep 17 00:00:00 2001 From: Esteban Gonzalez Corti Date: Wed, 14 Feb 2024 09:27:01 +1100 Subject: [PATCH 3/6] Update src/connections/destinations/catalog/adwords-remarketing-lists/index.md Co-authored-by: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> --- .../destinations/catalog/adwords-remarketing-lists/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/adwords-remarketing-lists/index.md b/src/connections/destinations/catalog/adwords-remarketing-lists/index.md index b374912831..6db73ba14f 100644 --- a/src/connections/destinations/catalog/adwords-remarketing-lists/index.md +++ b/src/connections/destinations/catalog/adwords-remarketing-lists/index.md @@ -129,7 +129,7 @@ Make sure that this destination was created in [Engage](/docs/engage/) as it req ### Invalid user list ID error in Event Delivery -When you first connect the destination into an audience, a call to the destination will be triggered to create the audience downstream. Once that succeeds and the audience is created, the destination API returns an ID for that audience to Segment. Later on, for subsequent updates to the audience in the destination (adding/removing users), Segment uses this ID to send the request to it. This error usually means that the audience ID Engage is using no longer exist in the destination. To sort this issue, you will need to either recreate the audience or create a *new instance* of the destination and link it to the audience. Removing and re-adding the same instace of the destination will not work. +When you first connect a destination to an audience, Segment triggers a call to the destination to create the audience downstream. Once Segment creates the audience, the destination API returns an audience ID. For subsequent updates to the audience in the destination (adding or removing users), Segment uses this ID to send requests to the destination. The invalid user list ID error usually means that the audience ID no longer exists in the destination. To resolve this, you'll need to either recreate the audience or create a *new instance* of the destination and link it to the audience. Removing and re-adding the same instance of the destination will not work. ## FAQs From 08c6b6cbb043d5a67b04a7ec7470b7ad5ea2ac2f Mon Sep 17 00:00:00 2001 From: rchinn-segment <93161299+rchinn-segment@users.noreply.github.com> Date: Tue, 13 Feb 2024 16:39:50 -0800 Subject: [PATCH 4/6] small fix --- src/connections/destinations/catalog/actions-pendo-web/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-pendo-web/index.md b/src/connections/destinations/catalog/actions-pendo-web/index.md index c0542a7144..65723b46ce 100644 --- a/src/connections/destinations/catalog/actions-pendo-web/index.md +++ b/src/connections/destinations/catalog/actions-pendo-web/index.md @@ -11,7 +11,7 @@ hide-dossier: true [Pendo](http://www.pendo.io/){:target="_blank"} combines powerful software usage analytics with in-app guidance and user feedback capabilities, enabling even non-technical teams to deliver better product experiences to their customers or employees. -This destination is maintained by Pendo. For issues with the Pendo Web (Actions) destination please reach out to [Pendo's support team](https://support.pendo.io/hc/en-us/articles/360034163971-Get-help-with-Pendo-from-Technical-Support) +Pendo maintains this destination. For issues with the Pendo Web (Actions) destination, please reach out to [Pendo's support team](https://support.pendo.io/hc/en-us/articles/360034163971-Get-help-with-Pendo-from-Technical-Support){:target="_blank"}. > success "" > **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Pendo Web (Actions) Segment destination. There's also a page about the [non-Actions Pendo destination](/docs/connections/destinations/catalog/pendo/). Both of these destinations receives data from Segment. From 7726d83c810216741678dcd40e85a21b999aebd5 Mon Sep 17 00:00:00 2001 From: Niall Brennan Date: Wed, 14 Feb 2024 10:54:24 +0000 Subject: [PATCH 5/6] fix support type param --- .../sources/catalog/libraries/mobile/android/index.md | 2 +- src/connections/sources/catalog/libraries/mobile/ios/index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/sources/catalog/libraries/mobile/android/index.md b/src/connections/sources/catalog/libraries/mobile/android/index.md index b94d416b66..9a4ee04008 100644 --- a/src/connections/sources/catalog/libraries/mobile/android/index.md +++ b/src/connections/sources/catalog/libraries/mobile/android/index.md @@ -2,7 +2,7 @@ title: 'Analytics for Android' strat: android repo: analytics-android -support_type: legacy +support_type: maintenance id: wXNairW5xX --- Analytics for Android makes it easier for you to send data to any tool without having to learn, test or implement a new API every time. diff --git a/src/connections/sources/catalog/libraries/mobile/ios/index.md b/src/connections/sources/catalog/libraries/mobile/ios/index.md index 795b3056f1..07090f9141 100644 --- a/src/connections/sources/catalog/libraries/mobile/ios/index.md +++ b/src/connections/sources/catalog/libraries/mobile/ios/index.md @@ -2,7 +2,7 @@ title: Analytics for iOS strat: ios repo: analytics-ios -support_type: legacy +support_type: maintenance id: UBrsG9RVzw --- With Analytics for iOS, you can send your data to analytics or marketing tool, without needing to learn, test, or implement a new API with each update or addition. From 9c4692c285420c8686466b7bd308769dec3e53d5 Mon Sep 17 00:00:00 2001 From: stayseesong Date: Wed, 14 Feb 2024 09:59:59 -0800 Subject: [PATCH 6/6] fixed link --- src/connections/oauth.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/oauth.md b/src/connections/oauth.md index 387c7cafaa..bbdf9ffcf1 100644 --- a/src/connections/oauth.md +++ b/src/connections/oauth.md @@ -122,7 +122,7 @@ To obtain the access token: JWT | The signed JWT token string from Step 1. SCOPE | Scopes for which token is requested. See [supported scopes](#supported-scopes). -To use the access token, see an example of how to use the access token in the [HTTP API source](). +To use the access token, see an example of how to use the access token in the [HTTP API source](/docs/connections/sources/catalog/libraries/server/http-api/#oauth). ## Edit an OAuth application To edit an existing OAuth application: