diff --git a/src/connections/destinations/catalog/actions-appcues-web/index.md b/src/connections/destinations/catalog/actions-appcues-web/index.md
new file mode 100644
index 0000000000..4cdf62cf55
--- /dev/null
+++ b/src/connections/destinations/catalog/actions-appcues-web/index.md
@@ -0,0 +1,46 @@
+---
+title: Appcues Web (Actions) Destination
+id: 698aff47f133996889ade37e
+---
+
+{% include content/plan-grid.md name="actions" %}
+
+[Appcues](https://www.appcues.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} adds an experience layer to your product so you can build user onboarding, NPS surveys, or feature announcements in minutes instead of weeks.
+
+When you use the Appcues Web (Actions) destination, Segment loads the Appcues JavaScript library for you. The Appcues library enables you to track your user's events on your website and deliver personalized experiences based on user behavior and properties.
+
+## Benefits of Appcues Web (Actions) vs Appcues Classic
+
+Appcues Web (Actions) provides the following benefits over the classic Appcues destination:
+
+- **Clearer mapping of data.** Actions-based destinations enable you to define the mapping between the data Segment receives from your source, and the data Segment sends to Appcues.
+- **Granular control over data sent.** You can customize the conditions under which the events are sent to Appcues.
+- **Full region support.** Setup allows the destination to be configured for US or EU regions.
+- **URL detection control.** Configure whether Appcues should automatically detect URL changes or rely solely on Segment page events.
+
+## Getting started
+
+1. From the Segment web app, click **Catalog**, then click **Destinations**.
+2. Find the Destinations Actions item in the left navigation, and click it.
+3. Click **Appcues Web (Actions)**.
+4. Click **Add destination**.
+5. Select an existing Source to connect to Appcues Web (Actions). The source must use [Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/).
+6. In the destination settings, enter your **Account ID** from the [Appcues account page](https://my.appcues.com/account){:target="_blank"}.
+7. Select the correct **Region** for your Appcues subscription (US or EU).
+
+{% include components/actions-fields.html settings="true" %}
+
+## Additional Information
+
+### Regional Data Hosting
+
+Appcues supports regional data hosting in both US and EU regions. Make sure to select the correct region in your destination settings to match your Appcues subscription.
+
+### URL Detection
+
+The **Enable URL Detection** setting controls how Appcues tracks page changes:
+
+- When disabled (default), Appcues relies on Segment page events to trigger experience checks.
+- When enabled, Appcues automatically detects URL changes without requiring explicit page calls.
+
+For most implementations, keep this setting disabled and use Segment's page calls for better control over when experiences are triggered.
\ No newline at end of file
diff --git a/src/connections/destinations/catalog/actions-appcues/index.md b/src/connections/destinations/catalog/actions-appcues/index.md
new file mode 100644
index 0000000000..c63ef7cf9b
--- /dev/null
+++ b/src/connections/destinations/catalog/actions-appcues/index.md
@@ -0,0 +1,48 @@
+---
+title: Appcues (Actions) Destination
+id: 699409fe37dec8f849615779
+---
+
+{% include content/plan-grid.md name="actions" %}
+
+[Appcues](https://www.appcues.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} adds an experience layer to your product so you can build user onboarding, NPS surveys, or feature announcements in minutes instead of weeks.
+
+This destination is maintained by Appcues. For any issues with the destination, [contact their Support team](mailto:support@appcues.com).
+
+## Getting started
+
+1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank"} search for "Appcues".
+2. Select **Appcues (Actions)** and click **Add Destination**.
+3. Select an existing Source to connect to Appcues (Actions).
+4. Go to the [Appcues Settings page](https://studio.appcues.com/settings/account){:target="_blank"} to obtain your credentials:
+   - Copy your **Account ID**
+   - Generate or copy your **API Key**
+   - Generate or copy your **API Secret**
+   - Note your **Region** (US or EU)
+5. Enter your **Account ID**, **API Key**, **API Secret**, and **Region** in the Appcues (Actions) destination settings in Segment.
+
+{% include components/actions-fields.html %}
+
+## Migration from the classic Appcues destination
+
+If you're currently using the classic Appcues destination to send events server side to Appcues, you can migrate to the Appcues (Actions) destination to take advantage of improved functionality and easier configuration. The Actions destination provides:
+
+- Server-side event delivery with improved reliability
+- Support for track, identify, page, screen, and group events through a unified action
+- Better control over which events are sent to Appcues
+- Consistent behavior across all event types
+
+To migrate:
+1. Set up the Appcues (Actions) destination following the steps above
+2. Configure the Send action with your desired event mappings
+3. Test the integration to ensure events are flowing correctly
+4. Once validated, you can disable the classic Appcues destination
+
+## Regional data residency
+
+Appcues supports regional data residency for customers who need to store their data in specific geographic locations. When configuring the destination, select the appropriate region:
+
+- **US**: Data is stored in US-based infrastructure
+- **EU**: Data is stored in EU-based infrastructure
+
+Ensure you select the region that matches your Appcues account configuration.