Merge remote-tracking branch 'upstream/develop' into develop

Author: lopenchi

src/_includes/content/functions/runtime.md

@@ -1,12 +1,12 @@
-On March 26, 2024, Segment upgraded the Functions runtime environment to Node.js v18, which is the current long-term support (LTS) release.
+Segment Functions run on the Node.js LTS runtime (currently v20). This keeps the runtime current with industry standards and security updates.  
 
-This upgrade keeps your runtime current with industry standards. Based on the [AWS Lambda](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html){:target="_blank"} and [Node.js](https://nodejs.org/en/about/previous-releases){:target="_blank"} support schedule, Node.js v16 is no longer in *Maintenance LTS*. Production applications should only use releases of Node.js that are in *Active LTS* or *Maintenance LTS*.
+Based on the [AWS Lambda](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html){:target="_blank"} and [Node.js](https://nodejs.org/en/about/previous-releases){:target="_blank"} support schedule, production applications should only use Node.js releases that are in Active LTS or Maintenance LTS.
 
-For existing functions, this change automatically occurs as you update and deploy an existing function. Segment recommends that you check your function post-deployment to ensure everything's working. Your function may face issues due to the change in syntax between different Node.js versions and dependency compatibility.
+When Segment upgrades the Functions runtime to a new LTS version, existing functions automatically use the new runtime after their next deployment. Segment recommends checking your function after deployment to ensure everything works as expected, since dependency or syntax changes between Node.js versions might affect your function’s behavior.
 
-Functions don't currently support importing dependencies, but you can [contact Segment Support](https://segment.com/help/contact/){:target="_blank"} to request that one be added.
+Functions don't support importing dependencies, but you can [contact Segment Support](https://segment.com/help/contact/){:target="_blank"} to request that one be added.
 
-The following dependencies are installed in the function environment by default.
+The following dependencies are installed in the function environment by default:
 
 - [`atob v2.1.2`](https://www.npmjs.com/package/atob){:target="_blank"} exposed as `atob`
 - [`aws-sdk v2.488.0`](https://www.npmjs.com/package/aws-sdk){:target="_blank"} exposed as `AWS`

src/connections/auto-instrumentation/configuration.md

@@ -3,49 +3,55 @@ title: Generate Events from Signals
 hidden: true
 ---
 
-This guide details how to use signals, and their associated data, generated in one of the Signals SDKs with the Auto-Instrumentation dashboard in your Segment workspace. On this page, you'll find details on:
+This guide details how to use signals and their associated data, generated in one of the Signals SDKs with the Auto-Instrumentation dashboard in your Segment workspace. On this page, find details on:
 
-- Creating custom rules to capture and translate signals into actionable analytics events
-- Example rules that you can use as a basis for further customization
+- Creating custom rules to capture and translate signals into actionable analytics events.
+- Example rules that you can use as a basis for further customization.
 
 This guide assumes that you've already added the Signals SDK to your application. If you haven't yet, see the [Auto-Instrumentation Setup](/docs/connections/auto-instrumentation/) guide for initial setup.
 
-> info "Auto-Instrumentation Private Beta"
-> Auto-Instrumentation is currently in Private Beta and is governed by Segment's [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}. Segment is actively iterating on and improving the Auto-Instrumentation user experience.
-
-> success "Enable Auto-Instrumentation"
-> To enable Auto-Instrumentation in your Segment workspace, reach out to your dedicated account manager.                     
-
+> info "Auto-Instrumentation in public beta"
+> Auto-Instrumentation is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.                  
 
 ## Converting signals to events
 
 After you set up the Signals SDK to capture the signals you want to target, you can create rules in your Segment workspace to translate the captured signals into traditional Segment analytics events. These rules are deployed in your application the next time a user launches your app.
 
 ### Getting started with rule creation
 
-1. In your Segment workspace, go to **Sources** and select a source.
-2. Open the **Event Builder**, then click **Create Rules**.
+1. Ensure you have the `Workspace Owner` or `Source Admin` role in Segment. If your source is connected to a tracking plan, you will also need, at a minimum, the `Tracking Plan Read-only` role. To view the content in the Event Builder tab, you will need, at a minimum, the `Source Read-only` role.
+2. In your Segment workspace, go to **Sources** and select a source.
+3. Open the **Event Builder**, then click **Create Rules**.
 
 > info "Where's the Event Builder tab?"
-> The Event Builder tab only appears after you've installed the Auto-Instrumentation snippet in your site or app. If you don’t see the tab, double check your implementation or reach out to your Segment CSM.
+> The Event Builder tab only appears after you've enabled Auto Instrumentation under the Analytics.js tab in the source's settings. If you don’t see the tab, reach out to your Segment CSM.
 
 ### Using the Rules Editor
 
 The Rules Editor is where you define rules that transform raw signal data into analytics events. Using the dropdown-based editor, you can:
 
-- Combine multiple signals into a single event (for example, a click followed by a navigation)
-- Set conditions to control when events should be triggered
-- Assign custom event names
+- Combine multiple signals into a single event (for example, a click followed by a navigation).
+- Set conditions to control when events should be triggered.
+- Assign custom event names.
+
+#### Tracking plan integration
+
+If your source is connected to a tracking plan, you can quickly confirm that a rule’s event and properties are planned. When creating or editing a rule, choose an event by typing its name or selecting from the tracking plan’s events in a dropdown. Similarly, add properties by typing their names or selecting from the event’s properties in a dropdown. The Planned column, shown next to each property mapping and in the Event Rules table, indicates whether the property or event is planned.
 
 #### Adding event properties
 
 You can enrich your events by adding properties based on signal metadata. For example:
 
-- Capture `product.price` in your **Add to Cart** event
-- Add a boolean field like `couponApplied` to your **Order Completed** event
+- Capture `product.price` in your **Add to Cart** event.
+- Add a boolean field like `couponApplied` to your **Order Completed** event.
 
 These properties are sent alongside your event, giving your team deeper insights without requiring any manual instrumentation.
 
+#### Preview your event rule
+
+To verify that a rule is working as expected, you don't need to enter a cycle of creating and updating the rule, generating signals, then checking the source debugger for the generated event. As you create, edit, or view a rule, you can preview it in real time against the current signal buffer to see which signals match and what the resulting event will look like. Event properties are mapped to the values found in the matched signals, and complete matches are grouped by anonymous ID.
+
+
 <!-- PW, 6 August 2025: Commenting this section out for now
 
 The Rules Editor also lets you test your rules with recent signals to verify that they produce the data you need before you deploy. 
@@ -89,7 +95,7 @@ interface RawSignal<T> {
 
 ### Signal Types
 
-The Signal Type enum defines the different types of signals the SDK can collect:
+The Signal Type `enum` defines the different types of signals the SDK can collect:
 
 ```java
 enum SignalType {
@@ -317,4 +323,4 @@ function ProcessSignals(signal) {
     trackAddToCart(signal); // Process the "Add To Cart" tracking based on incoming signals
 }
 ```
--->
+-->

src/connections/auto-instrumentation/index.md

@@ -26,11 +26,8 @@ redirect_from:
 
 Auto-Instrumentation simplifies tracking in your websites and apps by removing the need for a traditional Segment instrumentation.
 
-> info "Auto-Instrumentation Private Beta"
-> Auto-Instrumentation is currently in private beta and is governed by Segment's [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}. Segment is actively iterating on and improving the Auto-Instrumentation user experience.
-
-> success "Enable Auto-Instrumentation in your workspace"
-> To enable Auto-Instrumentation in your Segment workspace, reach out to your dedicated account manager or friends@segment.com.
+> info "Auto-Instrumentation in public beta"
+> Auto-Instrumentation is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
 
 ## Background
 
@@ -52,7 +49,7 @@ After you install the required SDKs and enable Auto-Instrumentation, Segment det
 
 You can group signals into complete analytics events, assign names, and map custom properties. You can then [use this data to create detailed analytics events](/docs/connections/auto-instrumentation/configuration/) based on those signals, enriching your insights into user behavior and application performance.
 
-## Setup Guides
+## Setup guides
 
 <div class="auto-instrumentation-catalog">
 <div class="auto-insturmentation__section markdown" id="{{ category | slugify }}">

src/connections/auto-instrumentation/kotlin-setup.md

@@ -7,22 +7,19 @@ Segment’s Signals library powers [Auto-Instrumentation](/docs/connections/auto
 
 This guide shows how to install and configure the library, as well as how to enable optional plugins for screen views, network activity, and more.
 
-> info "Auto-Instrumentation Private Beta"
-> Auto-Instrumentation is currently in Private Beta and is governed by Segment's [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}. Segment is actively iterating on and improving the Auto-Instrumentation user experience.
+> info "Auto-Instrumentation in public beta"
+> Auto-Instrumentation is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
 
-> success "Auto-Instrumentation access"
-> To turn Auto-Instrumentation on in your Segment workspace, reach out to your dedicated account manager.
-
-## Before you begin
+## Before you start
 
 To use Signals with Android, you need:
 
-- An active Segment workspace with Auto-Instrumentation enabled
-- A Kotlin-based Android project
-- Android Gradle Plugin version 7.0 or later
-- A minimum compile SDK version of 21
+- An active Segment workspace with Auto-Instrumentation enabled.
+- A Kotlin-based Android project.
+- Android Gradle Plugin version 7.0 or later.
+- A minimum compile SDK version of 21.
 
-Signals supports [Jetpack Compose](https://developer.android.com/compose){:target="_blank"} and traditional Android UI frameworks. It also includes optional plugins for network tracking using [OkHttp3](https://square.github.io/okhttp/){:target="_blank"}, [Retrofit](https://square.github.io/retrofit/){:target="_blank"}, or `HttpURLConnection`](https://developer.android.com/reference/java/net/HttpURLConnection){:target="_blank"}.
+Signals supports [Jetpack Compose](https://developer.android.com/compose){:target="_blank"} and traditional Android UI frameworks. It also includes optional plugins for network tracking using [OkHttp3](https://square.github.io/okhttp/){:target="_blank"}, [Retrofit](https://square.github.io/retrofit/){:target="_blank"}, or [HttpURLConnection](https://developer.android.com/reference/java/net/HttpURLConnection){:target="_blank"}.
 
 Segment recommends testing in a development environment before deploying Signals in production. For more information, see [Debug mode](#step-4-enable-debug-mode).
 
@@ -66,7 +63,7 @@ Only add the plugins you plan to use. You can add or remove them later without r
 
 ## Step 2: Initialize the SDK
 
-After you add dependencies, you'll need to initialize the Analytics client and configure the Signals plugin. 
+After you add dependencies, you need to initialize the Analytics client and configure the Signals plugin. 
 
 Start by creating the `Analytics` instance using your source's write key. Then add the Signals plugin and configure its settings separately.
 
@@ -98,7 +95,7 @@ navController.turnOnScreenTracking()
 
 When you run this code, keep the following in mind:
 
-- You'll need to replace `<WRITE_KEY>` with the key from your Android Source in Segment.
+- You need to replace `<WRITE_KEY>` with the key from your Android Source in Segment.
 - `debugMode` sends signals to Segment for use in the Event Builder. Only enable it in development environments.
 - If your app doesn't use Jetpack Compose or Navigation, you can skip those plugin lines.
 
@@ -233,7 +230,7 @@ If `debugMode` is enabled, Signals appear in real time as you interact with the
 5. After you add any event mappings, click **Publish event rules** to save them.
 
 > info "What if I don't see the Event Builder tab?"
-> If you don't see the Event Builder tab, confirm that the SDK is installed correctly and make sure `debugMode` is enabled. If you still don't see it, reach out to your CSM to verify that your workspace has Auto-Instrumentation enabled.
+> If you don't see the Event Builder tab, confirm that the SDK is installed correctly and make sure `debugMode` is enabled. Verify that Auto-Instrumentation is enabled in **Settings > Advanced**. If you still don't see it, reach out to your CSM.
 
 ## Configuration options
 

src/connections/auto-instrumentation/swift-setup.md

@@ -5,17 +5,14 @@ hidden: true
 
 This guide outlines the steps required to set up the Signals SDK in your Apple OS applications using Swift. 
 
-You'll learn how to connect an existing source, integrate dependencies, turn on Auto-Instrumentation, and verify that your setup captures and processes data as intended. 
+Learn how to connect an existing source, integrate dependencies, turn on Auto-Instrumentation, and verify that your setup captures and processes data as intended. 
 
-> info "Auto-Instrumentation Private Beta"
-> Auto-Instrumentation is currently in Private Beta and is governed by Segment's [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}. Segment is actively iterating on and improving the Auto-Instrumentation user experience.
-
-> success "Auto-Instrumentation access"
-> To turn Auto-Instrumentation on in your Segment workspace, reach out to your dedicated account manager.
+> info "Auto-Instrumentation in public beta"
+> Auto-Instrumentation is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
 
 ## Step 1: Get your source write key
 
-You need the `writeKey` from an existing Segment source:
+You need the `writeKey` from an existing Segment source. To find it:
 
 1. In your Segment workspace, go to **Connections > Sources**.
 2. Select your source.
@@ -24,7 +21,7 @@ You need the `writeKey` from an existing Segment source:
 
 ## Step 2: Add dependencies and initialization code
 
-Next, you'll need to add the Signals SDKs to your Swift applicatiion.
+Next, add the Signals SDKs to your Swift applicatiion.
 
 1. Use Swift Package Manager to add the Signals SDK from the following repository:
 
@@ -35,7 +32,7 @@ Next, you'll need to add the Signals SDKs to your Swift applicatiion.
 2. Add the initialization code and configuration options:
 
 > success ""
-> see [configuration options](#configuration-options) for a complete list.
+> See [configuration options](#configuration-options) for a complete list.
 
     ```swift
     // Configure Analytics with your settings
@@ -58,11 +55,11 @@ Next, you'll need to add the Signals SDKs to your Swift applicatiion.
     Analytics.main.add(plugin: Signals.shared)
     ```
 
-Verify that you replaced `<WRITE_KEY>` with the actual write key you copied in Step 1.
+Verify that you replaced `<WRITE_KEY>` with the actual write key you copied in [Step 1](#step-1-get-your-source-write-key).
 
 #### SwiftUI projects
 
-If your app is written in SwiftUI, you'll need to add a `TypeAlias.swift` file to your project that captures interaction and navigation Signals, like in this example:
+If your app is written in SwiftUI, you need to add a `TypeAlias.swift` file to your project that captures interaction and navigation Signals, like in this example:
 
 ```swift
 import Foundation
@@ -96,7 +93,7 @@ After integrating the SDK and running your app, verify that Segment is collectin
 4. Use the app as a user would: navigate between screens, tap buttons, trigger network requests. Signals appear in real time as you interact with the app.
 5. In the Event Builder, find a signal and click **Configure event** to define a new event. After configuring the event, click **Publish event rules**.
 
-## Configuration Options
+## Configuration options
 
 Using the Signals Configuration object, you can control the destination, frequency, and types of signals that Segment automatically tracks within your application. The following table details the configuration options for Signals-Swift.