You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/actions.md
+19-7
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,5 @@
1
1
---
2
2
title: Destination Actions
3
-
hidden: true
4
3
---
5
4
6
5
{% 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
15
14
16
15
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.
17
16
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).
0 commit comments