Skip to content

Commit a78876f

Browse files
authored
Merge pull request #2046 from segmentio/action-dests-benefits
Expand on the benefits of Destination Actions
2 parents 1e2ad6d + 8ed7c55 commit a78876f

File tree

1 file changed

+19
-7
lines changed

1 file changed

+19
-7
lines changed

src/connections/destinations/actions.md

+19-7
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
---
22
title: Destination Actions
3-
hidden: true
43
---
54

65
{% include content/plan-grid.md name="dest-actions" %}
@@ -15,13 +14,26 @@ You can also choose which event types, event names, or event property values tri
1514

1615
Each Actions-framework Destination you see in the Segment catalog represents a feature or capability of the destination which can consume data from your Segment source. The Action clearly lists which data from the events it requires, and which data is optional. For example, Amplitude requires that you always send a `LogEvent` , or Slack always requires a `PostMessage`. Each Action also includes a default mapping which you can modify.
1716

17+
## Benefits of Destination Actions
18+
19+
- **Easier setup**: Users see fewer initial settings which can decrease the time spent configuring the destination.
20+
- **Increased transparency**: Users can see the exact data that is sent to the destination, and when Segment sends it. For example, users can see exactly when Segment sends an IP address to FullStory or an AnonymousId to Amplitude.
21+
- **Improved customization**: Users can determine how the events their sources trigger and map to actions supported by the destination. For example, define the exact events that are considered purchases by Braze.
22+
- **Partner ownership**: Partners can own and contribute to any Actions-based destination that use cloud and device mode (web).
23+
1824
## Available Actions-based Destinations
19-
- [Amplitude (Actions)](/docs/connections/destinations/catalog/actions-amplitude)
20-
- [Braze (Actions) Web](/docs/connections/destinations/catalog/actions-braze-web)
21-
- [Braze (Actions) Cloud](/docs/connections/destinations/catalog/actions-braze-cloud)
22-
- [Slack (Actions)](/docs/connections/destinations/catalog/actions-slack)
23-
- [FullStory (Actions)](/docs/connections/destinations/catalog/actions-fullstory)
24-
- [Customer.io (Actions)](/docs/connections/destinations/catalog/actions-customer-io)
25+
26+
The following destinations are available in public beta status:
27+
28+
| Destination | Benefits |
29+
| ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
30+
| [Amplitude (Actions)](/docs/connections/destinations/catalog/actions-amplitude) | - Supports Amplitude session reporting <br /> - Revenue is a top-level property <br /> - Session tracking in cloud-mode |
31+
| [Braze (Actions) Cloud](/docs/connections/destinations/catalog/actions-braze-cloud) | E-commerce mappings |
32+
| [Braze (Actions) Web](/docs/connections/destinations/catalog/actions-braze-web) | E-commerce mappings |
33+
| [Customer.io (Actions)](/docs/connections/destinations/catalog/actions-customer-io) | Track an anonymous event |
34+
| [FullStory (Actions)](/docs/connections/destinations/catalog/actions-fullstory) | Support for FullStory's tracking page variables feature. |
35+
| [Slack (Actions)](/docs/connections/destinations/catalog/actions-slack) | - Consolidated Message Sending <br /> - Configure connection details on a per-message basis |
36+
2537

2638
## Destination Actions compatibility
2739

0 commit comments

Comments
 (0)