Merge pull request #4959 from segmentio/develop

forstisabella · web-flow · commit b4979def1abe · 2023-06-29T13:36:13.000-04:00
Release 23.26.2
diff --git a/src/_data/catalog/destination_categories.yml b/src/_data/catalog/destination_categories.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2023-06-27 
+# destination categories last updated 2023-06-29 
 items:
 - display_name: A/B Testing
   slug: a-b-testing
diff --git a/src/_data/catalog/destinations.yml b/src/_data/catalog/destinations.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2023-06-27 
+# destination data last updated 2023-06-29 
 items:
 - id: 637e8d185e2dec264895ea89
   display_name: 1Flow
@@ -59248,12 +59248,12 @@ items:
   mark:
     url: https://cdn.filepicker.io/api/file/ID6Qu6cBSmivatPUnoMY
   methods:
-    track: true
+    track: false
     identify: true
     group: true
-    alias: true
+    alias: false
     screen: false
-    page: true
+    page: false
   platforms:
     browser: true
     mobile: false
diff --git a/src/_data/catalog/destinations_private.yml b/src/_data/catalog/destinations_private.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2023-06-27 
+# destination data last updated 2023-06-29 
 items:
   - id: 54521fd725e721e32a72eec6
     display_name: Intercom
diff --git a/src/_data/catalog/regional-supported.yml b/src/_data/catalog/regional-supported.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED LIST OF CONNECTIONS THAT SUPPORT REGIONAL
-# Last updated 2023-06-27 
+# Last updated 2023-06-29 
 warehouses:
   - id: WcjBCzUGff
     display_name: Azure SQL Data Warehouse
diff --git a/src/_data/catalog/source_categories.yml b/src/_data/catalog/source_categories.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source cateogries last updated 2023-06-27 
+# source cateogries last updated 2023-06-29 
 items:
   - display_name: A/B Testing
     slug: a-b-testing
diff --git a/src/_data/catalog/sources.yml b/src/_data/catalog/sources.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# sources last updated 2023-06-27 
+# sources last updated 2023-06-29 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET
diff --git a/src/connections/destinations/catalog/adwords-remarketing-lists/index.md b/src/connections/destinations/catalog/adwords-remarketing-lists/index.md
@@ -123,6 +123,10 @@ You can set an email on the user profile by including `email` as a trait, as a p
 
 If a user has more than one email address or IDFA on their account as `external_ids`, Engage sends the most recent id on the user profile to Adwords for matching. The match rate will be low if Google can't identify users based on the data that you provide.
 
+### Invalid Settings error in Event Delivery
+
+Make sure that this destination was created in [Engage](/docs/engage/) as it requires additional event data not available in standard destinations.
+
 ## FAQs
 
 #### What Google Ads campaigns does Engage support?
diff --git a/src/connections/sources/catalog/libraries/mobile/react-native/index.md b/src/connections/sources/catalog/libraries/mobile/react-native/index.md
@@ -692,5 +692,34 @@ import {
     }
   }
 ```
+### How do I add to the context Object?
+Like with the integrations object above, you'll need to use a plugin to access and modify the context object. For example, if you'd like to add `context.groupId` to every Track call, you should create a plugin like this:
+```js
+//in AddToContextPlugin.js
+import {
+  Plugin,
+  PluginType,
+  SegmentEvent,
+} from '@segment/analytics-react-native';
+
+export class AddToContextPlugin extends Plugin {
+  // Note that `type` is set as a class property
+  // If you do not set a type your plugin will be a `utility` plugin (see Plugin Types above)
+  type = PluginType.enrichment;
+
+ async execute(event: SegmentEvent) {
+    if (event.type == EventType.TrackEvent) {
+      event.context['groupId'] = 'test - 6/8'
+      }
+      return event;
+    }
+}
+ // in App.js
+
+import { AddToContextPlugin } from './AddToContextPlugin'
+
+segmentClient.add({ plugin: new AddToContextPlugin() });  
+```
+
 ## Changelog
 [View the Analytics React Native changelog on GitHub](https://github.com/segmentio/analytics-react-native/releases){:target="_blank"}.
diff --git a/src/connections/sources/catalog/libraries/server/node/classic.md b/src/connections/sources/catalog/libraries/server/node/classic.md
@@ -6,7 +6,7 @@ hidden: false
 ---
 
 > info "Upgrade to the latest Analytics Node.js package"
-> This is the docs for the legacy npm package (`analytics-node`). [Upgrade to the latest package](/docs/connections/sources/catalog/libraries/server/node/migration/) (`@segment/analytics-node`). See the updated [Analytics Node.js docs](/docs/connections/sources/catalog/libraries/server/node) to learn more.
+> This is the doc for the legacy npm package (`analytics-node`). Segment will deprecate this version of Node on December 31, 2023.[Upgrade to the latest package](/docs/connections/sources/catalog/libraries/server/node/migration/) (`@segment/analytics-node`). See the updated [Analytics Node.js docs](/docs/connections/sources/catalog/libraries/server/node) to learn more.
 
 Segment's Node.js library lets you record analytics data from your node code. The requests hit Segment's servers, and then Segment routes your data to any destinations you have enabled.
 
diff --git a/src/connections/sources/catalog/libraries/server/node/quickstart.md b/src/connections/sources/catalog/libraries/server/node/quickstart.md
@@ -4,10 +4,6 @@ redirect_from: '/connections/sources/catalog/libraries/server/node-js/quickstart
 strat: node-js
 ---
 
-> info ""
-> This version of Analytics for Node.js is in beta and Segment is actively working on this feature. Segment's [First-Access and Beta terms](https://segment.com/legal/first-access-beta-preview/) govern this feature. 
-> <br><br> If you’re using the [classic version of Analytics for Node.js](/docs/connections/sources/catalog/libraries/server/node/classic/), consider upgrading to the [latest Analytics for Node.js library](/docs/connections/sources/catalog/libraries/server/node). 
-
 This tutorial will help you start sending data from your Node servers to Segment and any destination, using Segment's Node library. Check out the full documentation for [Analytics Node.js](/docs/connections/sources/catalog/libraries/server/node) to learn more.  
 
 To get started with Analytics Node.js:
diff --git a/src/connections/spec/group.md b/src/connections/spec/group.md
@@ -2,11 +2,15 @@
 title: 'Spec: Group'
 ---
 
-The `group` API call is how you associate an individual user with a group—be it a company, organization, account, project, team or whatever other crazy name you came up with for the same concept!
+The `group` API call is how you associate an individual user with a group, such as a company, organization, account, project, or team.
+
+The `group` call enables you to identify what account or organization your users are part of. There are two IDs that are relevant in a `group` call: the `userId`, which belongs and refers to the user, and the `groupId`, which belongs and refers to the specific group. A user can be in more than one group which would mean different `groupId`s, but the user will only have one `userId` that is associated to each of the different groups. Keep in mind that not all platforms support multiple groups for a single user. 
 
 {% include components/reference-button.html href="https://university.segment.com/introduction-to-segment/324252?reg=1&referrer=docs" icon="media/academy.svg" title="Segment University: The Segment Methods" description="Check out our high-level overview of these APIs in Segment University. (Must be logged in to access.)" %}
 
-A user can be in more than one group; however, not all platforms support multiple groups. It also lets you record custom traits about the group, like industry or number of employees.  Calling `group` is a slightly more advanced feature, but it's helpful if you have accounts with multiple users.
+In addition to the `groupId`, which is how you'd identify the specific group or company, the group method receives traits that are specific to the group, like industry or number of employees for example, that belong to that specific account. Like the traits of an identify call, you can update these when you call the same trait with a different value.
+
+When using the `group` call, it's helpful if you have accounts with multiple users.
 
 Here's the payload of a typical `group` call, with most [common fields](/docs/connections/spec/common/) removed:
 
diff --git a/src/engage/audiences/organization.md b/src/engage/audiences/organization.md
@@ -83,3 +83,14 @@ To clone an Audience between Spaces, follow the steps below:
 
 
 If your target Space doesn't include the cloned Audience's events and traits, Engage prompts you to resolve the Space incompatibilities during Step 5.  As a best practice, verify that the target Space includes the Audience's traits and events before cloning.
+
+
+## Delete an Audience
+
+To delete an Audience, follow the steps below:
+
+1. Navigate to the **Audiences** tab within your Space.
+2. Select the Audience you want to delete, then click **Settings**.
+3. Click **Enabled** to toggle to **Disabled**, then click **Delete Audience...**.
+4. On the Delete Audience prompt, click **Delete Audience** to confirm.
+
diff --git a/src/help/index.md b/src/help/index.md
@@ -31,3 +31,8 @@ Wondering what you can do with Segment? Check out [Segment Recipes](https://segm
 ## Other Resources
 
 Head over to [Segment Resources](https://segment.com/resources/?utm=docs){:target="_blank"} for Segment case studies, webinars, courses, and more.
+
+## Status Page
+
+The [Segment Status Page](https://status.segment.com/){:target="_blank"} offers details about system metrics and reports on uptime for each part of the Segment product. You can subscribe to receive updates about ongoing incidents and view [information about past incidents](https://status.segment.com/#past-incidents){:target="_blank"}. 
+
