{% else %}
{% endif %}
- {% unless page.hide-breadcrumb %}
- {% include components/breadcrumbs.html %}
- {% endunless %}
-
- {%- endif -%} - - {%- unless page.hide_toc -%} - {% include sidebar/mobile-menu-side.html %} - {%- endunless -%} - -
- {% include components/feedback.html %} - {% endunless %} -
-
-
-
- {%- if page.mark -%}
-
- {%- if page.url contains "destinations/catalog" -%}
- {%- elsif page.landing -%}
- {%- else -%}
-
- 
-
- {%- endif -%}
-
- {%- if page.title -%}
-
- - {{ page.title }} -
- {%- endif -%} - - {%- if page.excerpt -%} -
- {{ page.excerpt | markdownify }}
-
- {%- endif -%}
- - {%- endif -%} - - {%- unless page.hide_toc -%} - {% include sidebar/mobile-menu-side.html %} - {%- endunless -%} - -
- {% if page.beta %}
- {% unless page.integration_type == 'source' or page.integration_type == 'destination' %}
- {% include content/beta-note.md %}
- {% endunless %}
- {% endif %}
-
- {% if content.size < 2 %}
-
-
-
-
-
- {% endif %}
- {{ content }}
-
-
-
- Content coming soon.
-Content for this topic is on its way! Please check back soon.
- - -This page was last modified: {{ page.last_modified_at | date: '%d %b %Y' }}
- - {% if page.contributors %} - {% include components/recent-contributor.html contributors=page.contributors %} - {% endif %} - - - {% unless page.hide-feedback %} -- {% include components/feedback.html %} - {% endunless %} -
+
+To create a source volume alert:
+1. In your workspace, navigate to Connections, select Sources, and select the Event streams tab.
+2. Select the [event streams source](/docs/connections/sources/#event-streams-sources) you'd like to configure alerts for.
+2. Select the Alerts tab and click **Create alert**.
+3. On the Create alert sidesheet, enter a percentage of source volume change that you'd like to be notified for.
+4. Select one or more of the following alert channels:
+ - **Email**: Select this to receive notifications at the provided email address.
+ - **Slack**: Select this to send alerts to one or more channels in your workspace. You can post messages to your channel with either a [webhook](https://api.slack.com/messaging/webhooks){:target="_blank”} or a [workflow](https://slack.com/help/articles/360041352714-Build-a-workflow--Create-a-workflow-that-starts-outside-of-Slack){:target="_blank”}.
+ - **In-app**: Select this to receive notifications in the Segment app. To view your notifications, select the bell next to your user icon in the Segment app.
+5. Click **Save**.
+
+To make changes to a source volume alert, select the icon in the Actions column for the alert and click **Edit**.
+
+To delete a source volume alert, select the icon in the Actions column for the alert and click **Delete**.
+
+> info "Deleting alerts created by other users requires Workspace Owner permissions"
+> All users can delete source volume alerts that they created, but only those with Workspace Owner permissions can delete alerts created by other users.
+## Successful delivery rate alerts
+
+You can create an alert that notifies you when the volume of events successfully received by your destination in the last 24 hours falls below a percentage you set. For example, if you set a percentage of 99%, Segment notifies you if your destination had a successful delivery rate of 98% or below.
+
+To receive a successful delivery rate alert in a Slack channel, you must first create a Slack webhook. For more information about Slack webhooks, see the [Sending messages using incoming webhooks](https://api.slack.com/messaging/webhooks){:target="_blank”} documentation.
+
+To create a successful delivery rate alert:
+1. Navigate to the [cloud-mode destinations](/docs/connections/destinations/#:~:text=Cloud%2Dmode%3A%20The%20sources%20send%20data%20directly%20to%20the%20Segment%20servers%2C%20which%20then%20translate%20it%20for%20each%20connected%20downstream%20destination%2C%20and%20send%20it%20on.) you'd like to configure alerts for.
+2. Select the Alerts tab and click **Create alert**.
+3. On the Create alert sidesheet, enter a percentage. You will receive events if your successful delivery rate falls below this percentage.
+4. Select one of the following alert channels:
+ - **Email**: Select this to receive notifications at either the email address associated with your account or another email address that you enter into this field.
+ - **Slack**: Select this to send alerts to one or more channels in your workspace. You can post messages to your channel with either a [webhook](https://api.slack.com/messaging/webhooks){:target="_blank”} or a [workflow](https://slack.com/help/articles/360041352714-Build-a-workflow--Create-a-workflow-that-starts-outside-of-Slack){:target="_blank”}.
+ - **In-app**: Select this to receive notifications in the Segment app. To view your notifications, select the bell next to your user icon in the Segment app.
+5. Click **Save**.
+
+To make changes to a successful delivery rate alert, select the icon in the Actions column for the alert and click **Edit**.
+
+To delete a successful delivery rate alert, select the icon in the Actions column for the alert and click **Delete**.
+
+> info "Deleting alerts created by other users requires Workspace Owner permissions"
+> All users can delete successful delivery alerts that they created, but only those with Workspace Owner permissions can delete alerts created by other users.
+Segment generates delivery alerts for failed deliveries and successful deliveries, which are the last two stages of the delivery pipeline. As a result, alerts are based on Segment's attempts to send qualified events to your destination, excluding those filtered out by business rules (like protocols, destination filters, or mappings).
\ No newline at end of file
diff --git a/src/connections/auto-instrumentation/configuration.md b/src/connections/auto-instrumentation/configuration.md
new file mode 100644
index 0000000000..1f5af89c19
--- /dev/null
+++ b/src/connections/auto-instrumentation/configuration.md
@@ -0,0 +1,286 @@
+---
+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:
+
+- 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.
+
+
+## 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 to **Connections > Auto-Instrumentation** and click on a source.
+2. 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.
+
+### Using the Rules Editor
+
+The Rules Editor is where you define rules that transform raw signal data into analytics events. In the editor, you write functions that convert signals into events and then call them in the `processSignal()` function.
+
+The Rules Editor also lets you test your rules with recent signals to verify that they produce the data you need before you deploy.
+
+The following example tracks all Screen events:
+
+```javascript
+function screenCall(currentSignal) {
+ if (currentSignal.type == SignalType.Navigation && currentSignal.data.action == NavigationAction.Entering) {
+ analytics.screen(currentSignal.data.screen, null, null)
+ }
+}
+
+function processSignal(signal) {
+ screenCall(signal)
+}
+```
+
+## Signal definitions
+
+Signals come in various types, each associated with specific data that you can use to create analytics events. This section contains code samples that detail each signal type. Because Segment has standardized these definitions across both the Signals-Swift and Signals-Kotlin libraries, they're useful when you create rules in your Segment workspace.
+
+### Base signal
+
+The Base Signal serves as the foundation for all other signal types. It's defined by the `RawSignal