Merge pull request #3332 from segmentio/develop

Release 22.31.2

Author: rchinn1

.github/styles/Vocab/Docs/accept.txt

@@ -25,6 +25,8 @@ async
 background(?:ed|ing)
 Blitzllama
 blocklist
+Bluedot
+bool
 boolean
 Breyta
 Chargebee
@@ -34,6 +36,7 @@ Cocoapods
 Contentful
 Criteo
 csv
+datetime
 deeplink
 Dev
 Doubleclick
@@ -44,8 +47,10 @@ eu
 Freshsales
 Friendbuy
 ga
+geofenc(?:e|ing)
 gmail
 Gradle
+gzip
 Heatmapping
 href
 html
@@ -87,6 +92,7 @@ Preact
 Rokt
 Selligent
 Shopify
+signup
 Skalin
 Smartly
 Snapchat
@@ -106,6 +112,4 @@ waitlist
 WebKit
 Wootric
 Xcode
-Zendesk
-geofenc(?:e|ing)
-Bluedot
+Zendesk

src/_data/actions/amplitude.yml

@@ -198,9 +198,9 @@ config:
     - name: Track Referrer to Amplitude
       connection_mode:
         - device-web
-      configurable: false
+      configurable: true
       location:
-      notes: Not supported with Actions
+      notes: Update the User Properties mapping to send `context.page.referrer`.
     - name: Track Revenue per Product
       connection_mode:
         - cloud
@@ -219,9 +219,9 @@ config:
       connection_mode:
         - cloud
         - device-web
-      configurable: false
+      configurable: true
       location:
-      notes: Not supported with Actions
+      notes: Supported by default. See the UTM Properties section to view the mappings.
     - name: Unset Params Referrer on New Session
       connection_mode:
         - device-web

src/connections/destinations/catalog/webhooks/index.md

@@ -226,4 +226,4 @@ Under 'Connection Settings', you can provide up to 5 webhooks.
 
 ### Retries
 
-Our webhooks destination will retry any request that returns 5xx errors, multiple times, for a maximum of 4 hours.
+Segment retries requests that fail due to temporary errors like timeouts and 5xx status codes for up to four hours.

src/connections/destinations/destination-filters.md

@@ -3,9 +3,9 @@ title: Destination Filters
 rewrite: true
 ---
 
-Destination Filters let you prevent certain data from flowing into a destination.
+Use Destination Filters to prevent certain data from flowing into a destination.
 
-Using Destination Filters, you can conditionally filter out event properties, traits, and fields, or even filter out the event itself.
+With Destination Filters, you can conditionally filter out event properties, traits, and fields, or even filter out the event itself.
 
 Common use cases for Destination Filters include the following:
 
@@ -17,10 +17,11 @@ Common use cases for Destination Filters include the following:
 > note ""
 > Destination Filters are available to Business Tier customers only.
 
-### Destination Filtering Limitations
+### Destination filtering limitations
 
 Keep the following limitations in mind when you use Destination Filters:
 
+- Segment applies Destination Filters one at a time in the order that they appear in your workspace.
 - Destination Filters can only be applied to cloud-mode (server-side) streaming destinations. Device-mode destinations aren't supported.
 - You can't apply Destination Filters to Warehouses or S3 destinations.
 - Each filter can only apply to one source-destination pair.
@@ -59,7 +60,7 @@ To learn more, read Segment's [Destination Filters API docs](https://reference.s
 
 The following examples illustrate common Destinations Filters use cases.
 
-### PII Management
+### PII management
 
 Example: Remove email addresses from `context` and `properties`:
 
@@ -68,19 +69,19 @@ Property-level allowlisting is available with Segment's API. Using Destination F
 
 ![PII management example](images/destination-filters/pii_example.png)
 
-### Control Event Volume
+### Control event volume
 
 This example shows a filter that controls event volume by only sending `User Signed Up` and `Demo Requested` events.
 
 ![Example of a filter that controls event volume](images/destination-filters/drop_example.png)
 
-### Cleaner Data
+### Cleaner data
 
 This example shows a rule that only sends track calls to Google Analytics.
 
 ![Example of a filter that only sends track calls to Google Analytics](images/destination-filters/clean_example.png)
 
-### Remove Internal and Test Events From Production Tools
+### Remove internal and test events from production tools
 
 This rule targets email addresses with internal domains to stop test events from reaching Destinations.
 
@@ -90,15 +91,15 @@ This rule prevents an event from sending if `Order Completed` and `properties.em
 
 ![Internal domain filter example](images/destination-filters/internal_example2.png)
 
-### Sample a Percentage of Events
+### Sample a percentage of events
 
 Using the [Destination Filters API](https://reference.segmentapis.com/#6c12fbe8-9f84-4a6c-848e-76a2325cb3c5){:target="_blank"}, you can create a rule to randomly sample video heartbeat events.
 
-### Drop Events
+### Drop events
 
 [Watch this Destination Filters walkthrough](https://www.youtube.com/watch?v=47dhAF1Hoco){:target="_blank"} to learn how to use event names to filter events sent to destinations.
 
-## Important Notes
+## Important notes
 
 **Conflicting settings**
 

src/connections/functions/destination-functions.md

@@ -452,7 +452,7 @@ Yes, Functions access is logged in the [Audit Trail](/docs/segment-app/iam/audit
 
 ##### Does Segment retry failed function invocations?
 
-Segment retries 9 times over the course of 4 hours. This increases the number of attempts for messages, so Segment tries to re-deliver them another 4 times after some backoff. Segment doesn't retry if your function throws a [non-recoverable error](#errors-and-error-handling).
+Segment retries invocations that throw RetryError or Timeout errors for up to four hours. Segment does not retry if your function throws a [non-recoverable error](#errors-and-error-handling).
 
 ##### Are events guaranteed to send data in order?
 

src/connections/functions/source-functions.md

@@ -385,7 +385,7 @@ Copy and paste this URL into the upstream tool or service to send data to this s
 
 ##### What is the retry policy for a webhook payload?
 
-The webhook payload retries up to six times with an exponential backoff for the function in the event of a failure with the function. After six attempts, the message is dropped.
+Segment retries invocations that throw RetryError or Timeout errors up to six times. After six attempts, the request is dropped.
 
 ##### What is the maximum payload size for the incoming webhook?
 

src/connections/sources/catalog/cloud-apps/braze/index.md

@@ -23,7 +23,7 @@ Braze maintains this source. For any issues with the source, you can [contact th
    The nickname is used as a label for the source in your Segment interface, and Segment creates a related schema name. The schema name is the namespace you'll query against in a warehouse. The nickname can be anything, but Segment recommends sticking to something that reflects the source itself and distinguishes amongst your environments (for example, `Braze_Prod`, `Braze_Staging`, `Braze_Dev`).
 4. Copy the **Write Key** on the Overview page.
 5. To finish the setup, contact Braze Support or your Customer Support Manager to activate Currents in Braze.
-   Braze Currents is only available in select Braze packages and can't be configured within Braze without assistance from your Braze Customer Success representative.
+   - **Note:** Braze Currents is only available in select Braze packages and can't be configured within Braze without assistance from your Braze Customer Success representative. Select the appropriate **Supported Region** in the Braze Currents configuration if you are using a non U.S. Segment Region.
 6. Go back to Segment and click **Add Destinations** in your Braze source to add the destinations where you want to receive your Braze data.
 
 Events are now sent to these destinations and automatically loaded into any warehouses you enabled.

src/connections/sources/catalog/libraries/mobile/kotlin-android/index.md

@@ -16,7 +16,7 @@ With Analytics-Kotlin, you can send data using Kotlin applications to any analyt
 If you're migrating to Analytics-Kotlin from a different mobile library, you can skip to the [migration guide](/docs/connections/sources/catalog/libraries/mobile/kotlin-android/migration/).
 
 
-## Getting Started
+## Getting started
 
 To get started with the Analytics-Kotlin mobile library:
 
@@ -92,7 +92,9 @@ To get started with the Analytics-Kotlin mobile library:
 
     The SDK internally uses a number of Java 8 language APIs through desugaring. Make sure your project either [enables desugaring](https://developer.android.com/studio/write/java8-support#library-desugaring)) or requires a minimum API level of 26.
 
-## Tracking Methods
+    You'll find configuration options such as IDFA collection and automatic screen tracking in Segment’s [Plugin Examples repository](https://github.com/segmentio/analytics-kotlin/tree/main/samples/kotlin-android-app/src/main/java/com/segment/analytics/next/plugins){:target="_blank"}.
+
+## Tracking methods
 
 Once you've installed the mobile or server Analytics-Kotlin library, you can start collecting data through Segment's tracking methods:
 - [Identify](#identify)
@@ -153,7 +155,7 @@ analytics.track("View Product", buildJsonObject {
 ### Screen
 The [Screen](/docs/connections/spec/screen/) method lets you record whenever a user sees a screen in your mobile app, along with optional extra information about the page being viewed.
 
-You'll want to record a screen event whenever the user opens a screen in your app. This could be a view, fragment, dialog or activity depending on your app.
+You'll want to record a screen event whenever the user opens a screen in your app. This could be a view, fragment, dialog, or activity depending on your app.
 
 Not all integrations support screen, so when it's not supported explicitly, the screen method tracks as an event with the same parameters.
 
@@ -203,10 +205,10 @@ analytics.group("user-123", buildJsonObject {
 {% endcodeexampletab %}
 {% endcodeexample %}
 
-## Plugin Architecture
+## Plugin architecture
 Segment's plugin architecture enables you to modify and augment how the analytics client works. From modifying event payloads to changing analytics functionality, plugins help to speed up the process of getting things done.
 
-Plugins are run through a timeline, which executes in order of insertion based on their entry types. Segment has these 5 entry types:
+Plugins are run through a timeline, which executes in order of insertion based on their entry types. Segment has these five entry types:
 
 | Type          | Details                                                                                        |
 | ------------- | ---------------------------------------------------------------------------------------------- |
@@ -217,7 +219,7 @@ Plugins are run through a timeline, which executes in order of insertion based o
 | `utility`     | Executes only with manual calls such as Logging.                                               |
 
 ### Fundamentals
-There are 3 basic types of plugins that you can use as a foundation for modifying functionality. They are: [`Plugin`](#plugin), [`EventPlugin`](#eventplugin), and [`DestinationPlugin`](#destinationplugin).
+There are three basic types of plugins that you can use as a foundation for modifying functionality. They are: [`Plugin`](#plugin), [`EventPlugin`](#eventplugin), and [`DestinationPlugin`](#destinationplugin).
 
 #### Plugin
 `Plugin` acts on any event payload going through the timeline.
@@ -341,7 +343,7 @@ analytics.add(yourPlugin)
 See how different platforms and languages use Analytics-Kotlin in different [example projects](https://github.com/segmentio/analytics-kotlin/tree/main/samples).
 The example projects contain sample [plugins](https://github.com/segmentio/analytics-kotlin/tree/main/samples/kotlin-android-app/src/main/java/com/segment/analytics/next/plugins) and [destination plugins](https://github.com/segmentio/analytics-kotlin/tree/main/samples/kotlin-android-app-destinations/src/main/java/com/segment/analytics/destinations/plugins) you can utilize.
 
-## Utility Methods
+## Utility methods
 The Analytics-Kotlin utility methods help you work with plugins from the analytics timeline. They include:
 - [Add](#add)
 - [Find](#find)
@@ -440,7 +442,7 @@ analytics.reset()
 {% endcodeexampletab %}
 {% endcodeexample %}
 
-## Build Your Own Destination
+## Build Your own destination
 
 If Segment doesn't support your Kotlin destination, you can build your own with the template Segment provides.
 

src/connections/sources/catalog/libraries/mobile/swift-ios/index.md

@@ -34,7 +34,7 @@ To get started with the Analytics-Swift mobile library:
 
     ```swift
     var analytics: Analytics? = nil
-    
+
     func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
             // Override point for customization after application launch.
             let configuration = Configuration(writeKey: "WRITE_KEY")
@@ -68,6 +68,7 @@ Once you've installed the Analytics-Swift library, you can start collecting data
 - [Track](#track)
 - [Screen](#screen)
 - [Group](#group)
+- [Alias](#alias)
 
 ### Identify
 The [Identify](/docs/connections/spec/identify/) method lets you tie a user to their actions and record traits about them. This includes a unique user ID and any optional traits you know about them like their email, name, address. The traits option can include any information you want to tie to the user. When using any of the reserved traits, be sure the information reflects the name of the trait. For example, `email`  should always be a string of the user's email address.
@@ -186,6 +187,23 @@ analytics.group(groupId: "user-123", traits: MyTraits(
 {% endcodeexampletab %}
 {% endcodeexample %}
 
+### Alias
+The [Alias](/docs/connections/spec/alias/) method is used to merge two user identities, effectively connecting two sets of user data as one. When this method is called, the `newId` value overwrites the old `userId`. If no `userId` is currently set, the `newId` associates with future events as the `userId`. This is an advanced method and may not be supported across the entire destination catalog.
+
+{% codeexample %}
+{% codeexampletab Method signature %}
+```swift
+func alias(newId: String)
+```
+{% endcodeexampletab %}
+
+{% codeexampletab Example use %}
+```swift
+analytics.alias(newId: "user-123")
+```
+{% endcodeexampletab %}
+{% endcodeexample %}
+
 ## Plugin Architecture
 Segment's plugin architecture enables you to modify and augment how the analytics client works. From modifying event payloads to changing analytics functionality, plugins help to speed up the process of getting things done.