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
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ Each Actions-framework Destination you see in the Segment catalog represents a f
16
16
17
17
##Benefits of Destination Actions
18
18
19
-
-**Easier setup**:Fewerinitial settingsdecreases time spent configuring the destination.
19
+
-**Easier setup**:Users see fewerinitial settingswhich can decrease the time spent configuring the destination.
20
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
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
22
-**Partner ownership**: Partners can own and contribute to any Actions-based destination that use cloud and device mode (web).
@@ -28,11 +28,11 @@ The following destinations are available in public beta status:
