Merge pull request #7137 from segmentio/develop

stayseesong · web-flow · commit 73a9a3f5b5e0 · 2024-10-10T11:16:39.000-07:00
Release 24.41.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 2024-10-08 
+# destination categories last updated 2024-10-10 
 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 2024-10-08 
+# destination data last updated 2024-10-10 
 items:
 - id: 637e8d185e2dec264895ea89
   display_name: 1Flow
@@ -84839,11 +84839,9 @@ items:
   status: PUBLIC
   categories:
   - A/B Testing
-  - Analytics
-  - Marketing Automation
   - Personalization
   logo:
-    url: https://cdn-devcenter.segment.com/40210039-b8fc-4a7f-a04b-657153890b17.svg
+    url: https://cdn-devcenter.segment.com/23df1e94-d633-41e6-b43d-1210c2a59238.svg
   mark:
     url: https://cdn-devcenter.segment.com/cbed56fc-e143-49ae-96eb-e4847cde8f5f.svg
   methods:
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 2024-10-08 
+# destination data last updated 2024-10-10 
 items:
   - id: 54521fd925e721e32a72eee1
     display_name: Pardot
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 categories last updated 2024-10-08 
+# source categories last updated 2024-10-10 
 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 2024-10-08 
+# sources last updated 2024-10-10 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET
diff --git a/src/_includes/content/warehouse-ip.html b/src/_includes/content/warehouse-ip.html
@@ -1,14 +1,14 @@
 <div class="premonition warning">
   <div class="fa fa-exclamation-circle"></div>
   <div class="content">
-    <p class="header">Update your warehouse allowlist for with new IP addresses</p>
-    <p>Starting on November 14, 2023, all Segment customers with workspaces hosted in the US who use allowlists in their warehouses must update those allowlists to include the following ranges:</p>
+    <p class="header">Update your warehouse allowlist with new IP addresses</p>
+    <p>As of November 14, 2023, all Segment users with workspaces hosted in the US who use allowlists in their warehouses must update those allowlists to include the following ranges:</p>
     <ul>
       <li><code class="language-plaintext highlighter-rouge">52.25.130.38/32</code></li>
       <li><code class="language-plaintext highlighter-rouge">34.223.203.0/28</code></li>
     </ul>
 
-    <p>Customers with workspaces in the EU must allowlist <code class="language-plaintext highlighter-rouge">3.251.148.96/29</code>.</p>
+    <p>Users with workspaces in the EU must allowlist <code class="language-plaintext highlighter-rouge">3.251.148.96/29</code>.</p>
 
     <p>These updates coincide with reliability improvements to Segment's underlying warehouse architecture.</p>
 
diff --git a/src/connections/auto-instrumentation/web-setup.md b/src/connections/auto-instrumentation/web-setup.md
@@ -92,6 +92,18 @@ https://my-website.com?segment_signals_debug=false
 
 ### Advanced
 
+#### Emitting custom signals 
+If you need to listen for data that is unavailable to the Signals plugin by default, you can create and emit a custom signal:
+
+```ts
+import { signalsPlugin } from './analytics' // assuming you exported your plugin instance.
+
+signalsPlugin.addSignal({
+  type: 'userDefined',
+  data: { foo: 'bar' }
+})
+```
+
 #### Listening to signals
 ```ts
 const signalsPlugin = new SignalsPlugin()
diff --git a/src/connections/destinations/catalog/actions-accoil-analytics/index.md b/src/connections/destinations/catalog/actions-accoil-analytics/index.md
@@ -33,7 +33,7 @@ Accoil is most effective when used with Segment. Here’s how it functions:
 
 To start using the Accoil destination:
 
-1. In your Segment workspace, navigate to the Catalog page and search for "Accoil Analytics".
+1. In your Segment workspace, navigate to the [Catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog/){:target="_blank"} and search for "Accoil Analytics".
 2. Select Accoil Analytics from the results and click **Add Destination**.
 3. Choose the Segment source you want to connect to Accoil.
 4. Navigate to your Accoil dashboard and find your API Key under **General Account Settings**. Copy this API Key.
@@ -65,13 +65,14 @@ Example Call:
 Group calls link users to accounts and records account-level attributes.
 
 Example Call:
-   ````javascript
+   ```javascript
    analytics.group('accountId123', {
      name: 'Example Company',
      createdAt: '2021-03-15T09:00:00Z',  // ISO 8601 or Unix timestamp format
      mrr: 3000,
      status: 'active'
    });
+   ```
 
 ### Track
 
@@ -85,6 +86,7 @@ Example Call:
      item: 'Book',
      price: 25.00
    });
+   ```
 
 ### Page and Screen
 
@@ -94,6 +96,7 @@ Example Calls:
    ```javascript
    analytics.page('Home Page');
    analytics.screen('Dashboard');
+   ```
 
 ## Key Notes
 
diff --git a/src/connections/destinations/catalog/actions-braze-cloud/index.md b/src/connections/destinations/catalog/actions-braze-cloud/index.md
@@ -34,8 +34,31 @@ Braze Cloud Mode (Actions) provides the following benefit over Braze Classic:
 > info ""
 > Braze now supports sending `email` as an identifier. Braze requires that you include `userId`, `braze_id`, or `email` for all calls made in cloud-mode. Segment sends a `braze_id` if the `userId` is missing. When you use a device-mode connection, Braze automatically tracks anonymous activity using the `braze_id` if a `userId` is missing.
 
-> info "V2 Actions"
-> The V2 versions of each action include improved sync mode support. Only valid sync modes for each action are available. As a result, the `_update_existing_only` parameter is tied to the sync mode you select for the mapping. If you select the `update` sync mode, Segment passes `_update_existing_only: true` to Braze, and if you choose the `add` sync mode, Segment passes `_update_existing_only: false` to Braze.
+
+## Actions v2
+
+Segment’s introduced the following v2 Actions to add additional functionality to the Braze Cloud Mode (Actions) destination: 
+- [Update User Profile v2](#update-user-profile-v2)
+- [Track Event v2](#track-event-v2)
+- [Identify User v2](#identify-user-v2)
+- [Create Alias v2](#create-alias-v2)
+- [Track Purchase v2](#track-purchase-v2)
+
+These Actions support the following features:
+- **Sync modes**: Control how Segment updates your downstream destination by selecting a sync mode, or a strategy for updating your downstream data. 
+- **Dynamic dropdowns**: When creating or updating a mapping in the Segment app, the dropdown auto-populates all of the available properties directly from Braze.
+- **Create and modify data**: Use Sync modes to create objects in your downstream destination without having to leave the Segment app.
+
+> warning ""
+> You might need to reauthorize your Braze account to use all of the features associated with v2 Actions.
+
+### Sync modes
+
+Sync modes allow users to define how Segment should update the data in your destination.
+
+Sync modes available for v2 Actions include:
+- **Upsert**: Update existing records and add new ones, if necessary.
+- **Add**: Add records to a list, segment, or journey.
 
 {% include components/actions-fields.html settings="true"%}
 
@@ -50,4 +73,4 @@ Keep the following in mind if you plan to move to Braze (Actions) from the class
 Braze requires one of either `external_id`, `user_alias`, or `braze_id` to be present in all events sent. If events are failing to send, please check your event mappings to make sure these fields are resolving to valid values.
 
 ### Missing events
-When an event is sent under an alias, the event may seem to be missing when the alias cannot be found in Braze. This may be due to incorrect search for the alias in Braze. To search for an alias in Braze, use the format "Alias Label:Alias Name". For example, if the "Alias Label" field is set as email and "Alias Name" field is set as email address (for example: "test@email.com"), use "email:test@email.com" to search for the alias in Braze.
+When an event is sent under an alias, the event may seem to be missing when the alias cannot be found in Braze. This may be due to incorrect search for the alias in Braze. To search for an alias in Braze, use the format "Alias Label:Alias Name". For example, if the "Alias Label" field is set as email and "Alias Name" field is set as email address (for example: "test@email.com"), use "email:test@email.com" to search for the alias in Braze.
diff --git a/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md b/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md
@@ -113,6 +113,24 @@ Segment automatically hashes any of the following fields that are not already ha
  * First name
  * Last name
 
+## Actions v2
+
+Segment’s v2 Actions, [Call Conversion v2](#call-conversion-v2), [Conversion Adjustment v2](#conversion-adjustment-v2), and [Click Conversion v2](#click-conversion-v2), support the following features:
+
+- **Sync modes**: Control how Segment updates your downstream destination by selecting a sync mode, or a strategy for updating your downstream data. 
+- **Dynamic dropdowns**: When creating or updating a mapping in the Segment app, the dropdown auto-populates all of the available properties directly from Google Ads.
+- **Create and modify data**: Use Sync modes to create objects in your downstream destination without having to leave the Segment app.
+
+> warning ""
+> You might need to reauthorize your Google Ads account to use all of the features associated with v2 Actions.
+
+### Sync modes
+
+Sync modes allow users to define how Segment should update the data in your destination.
+
+Sync modes available for v2 Actions include:
+- **Add**: Add records to a list, segment, or journey.
+
 {% include components/actions-fields.html settings="true"%}
 
 ## Consent mode
@@ -181,3 +199,4 @@ To resolve this, ensure that the ConversionActionType value in Google Ads is cor
 ### `The required field was not present., at conversions[0].gclid` Error
 
 Events going to Google for this integration require a `GCLID` field, an `email`, or a `phone_number`. If one of those identifiers isn't being sent properly, then you may see the `The required field was not present., at conversions[0].gclid` error. To fix this, double check that at least one of those fields is being passed to Google on each payload.
+
diff --git a/src/connections/sources/custom-domain.md b/src/connections/sources/custom-domain.md
@@ -59,6 +59,9 @@ To configure Custom Domain:
 
 ## FAQ
 
+### Can I set up multiple Custom Domains?
+Segment recommends creating a different subdomain (for example, `mysubdomain.mydomain.com`) for each source. You cannot connect multiple custom domains to the same source.
+
 ### What sources can I use with Custom Domain?
 Custom Domain was largely developed to support JavaScript sources. It helps with comprehensive collection of first-party data from your website when accessed over any platform (desktop, mobile, and more). You can use the subdomain for all other non-JavaScript sources as well, for consistency, but it will have no impact on data collection for those sources.  
 
diff --git a/src/engage/audiences/linked-audiences.md b/src/engage/audiences/linked-audiences.md
@@ -96,7 +96,7 @@ at most: supports 0 or greater.
 
 *When filtering by 0, you can’t filter on by entity properties or on additional nested entities.
 
-#### Operator Selection
+#### Operator selection
 
 You can create audience definitions using either `AND` or `OR` operators across all condition levels. You can switch between these operators when filtering on multiple entity or event properties, between conditions within a condition group, and between condition groups.
 
@@ -112,18 +112,24 @@ This information appears when you click the user profile generated from the audi
 
 ![A screenshot of the Entity Explorer.](/docs/engage/images/entity_explorer.png)
 
-#### Dynamic References
+#### Dynamic references
 
-**Event Conditions**
+**Event conditions**
 
 When filtering on event properties, you can dynamically reference the value of another profile trait, or enter a constant value. These operators support dynamic references: equals, not equals, less than, greater than, less than or equal, greater than or equal, contains, does not contain, starts with, ends with.
 
-**Entity Conditions**
+**Entity conditions**
+
+When filtering on entity properties, you can dynamically reference the value of another entity column (from the same entity branch at the same level or above it), profile trait, or enter a constant value. You can only dynamically reference properties of the same data type. Dynamic references are supported for specific operators depending on the data type, as in the following table:
+
+| Data Type | Supported Operators                                                                    |
+| --------- | -------------------------------------------------------------------------------------- |
+| NUMBER    | equals, not equals, less than, greater than, less than or equal, greater than or equal |
+| STRING    | equals, not equals, contains, does not contain, starts with, ends with                 |
+| DATE      | equals, not equals, less than, greater than, less than or equal, greater than or equal |
+| TIME      | equals, not equals, less than, greater than, less than or equal, greater than or equal |
+| TIMESTAMP | equals, not equals, less than, greater than, less than or equal, greater than or equal |
 
-When filtering on entity properties, you can dynamically reference the value of another entity column (from the same entity branch at the same level or above it), profile trait, or enter a constant value.You can only dynamically reference properties of the same data type. Dynamic references are only supported for certain operators depending on the data type:
-NUMBER data type: equals, not equals, less than, greater than, less than or equal, greater than or equal
-STRING data type: equals, not equals, contains, does not contain, starts with, ends with
-TIMESTAMP data type: equals, not equals, less than, greater than, less than or equal, greater than or equal
 
 ## Step 2: Activate your Linked Audience
 
@@ -179,7 +185,7 @@ After you select an action, Segment attempts to automatically configure the data
 
 Select additional traits and properties to include when the event is sent.
 
-#### Show/Hide preview 
+#### Show/hide preview 
 
 As you're enriching your events in Linked Audiences, you should view a preview of the event payload schema based on the properties you select. It might look like the following:
 
@@ -238,4 +244,4 @@ Delivery Overview shows you four steps in your data activation pipeline:
 - **Events from Audience**: Events that Segment created for your activation. The number of events for each compute depends on the changes detected in your audience membership. 
 - **Filtered at Destination**: The activation pipeline is rich with features that let you control which events make it to the destination. If any events aren't eligible to be sent (for example, due to destination filters, insert function logic, and so on), Segment will show them in Filtered at Destination.
 - **Failed Delivery**: Events that Segment attempted but failed to deliver to your destination. Failed Delivery indicates an issue with the destination, like invalid credentials, rate limits, or other error statuses received during delivery.
-- **Successful Delivery**: Events that Segment successfully delivered to your destination. You'll see these events in your downstream integration.
+- **Successful Delivery**: Events that Segment successfully delivered to your destination. You'll see these events in your downstream integration.
diff --git a/src/unified-profiles/unified-profiles-workspace.md b/src/unified-profiles/unified-profiles-workspace.md
@@ -34,7 +34,7 @@ You can set up 1 of the following options:
 ### CSV
 
 > warning "You cannot remove test profiles in your Unified Profiles workspace"
-> Contact Flex support to remove test profiles you uploaded to your Unified Profiles workspace.
+> Contact [Segment support](mailto:friends@segment.com){:target="_blank"} to remove test profiles you uploaded to your Unified Profiles workspace.
 
 1. On the Getting started page, click **Upload CSV**. 
 2. Review the information on the Upload profiles and custom traits page. 
