Skip to content

Latest commit

 

History

History
57 lines (35 loc) · 3.11 KB

doc-template-update.md

File metadata and controls

57 lines (35 loc) · 3.11 KB
title hide-boilerplate hide-dossier
<destination_name>
true
true

{% include content/plan-grid.md name="actions" %}

success "" Good to know: This page is about the Actions-framework <destination_name> Segment destination. There's also a page about the non-Actions <destination_name> destination. Both of these destinations receives data from Segment.

{% include content/ajs-upgrade.md %}

Benefits of <destination_name> (Actions) vs <destination_name> Classic

<destination_name> (Actions) provides the following benefits over the classic <destination_name> destination:

  • Main point 1. One or two sentences that back up the main point.
  • Main point 2. One or two sentences that back up the main point.

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 Configure <desintation_name>.
  4. Select an existing Source to connect to <destination_name> (Actions).

{% include components/actions-fields.html %}

Migration from the classic <destination_name> destination