diff --git a/src/connections/destinations/catalog/actions-heap/index.md b/src/connections/destinations/catalog/actions-heap/index.md new file mode 100644 index 0000000000..2813364160 --- /dev/null +++ b/src/connections/destinations/catalog/actions-heap/index.md @@ -0,0 +1,38 @@ +--- +title: Heap (Actions) Destination +hide-boilerplate: true +hide-dossier: false + +versions: + - name: Heap (Classic) + link: /docs/connections/destinations/heap +--- + +{% include content/plan-grid.md name="actions" %} + +[Heap](https://heapanalytics.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) automatically captures every user interaction with no extra code. This includes clicks, taps, gestures, form submissions, page views, and more. + +> success "" +> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Segment destination. There's also a page about the [non-Actions destination](/docs/connections/destinations/catalog//). Both of these destinations receives data from Segment. + + +{% include content/ajs-upgrade.md %} + +## Benefits of Heap (Actions) vs Heap Classic + +Heap (Actions) provides the following benefits over the classic Heap destination: + +- **More control with clearer mapping**. Actions-based destinations enable you to define the mapping between the data Segment receives from your source, and the data Segment sends to the destination. + +- **Increased transparency**. All Segment ingested events will display the Segment icon in Heap to easily identify the source of the event, and foster greater data trust + +- **Improved setup**. Easier default settings make it easier to get set up faster + +## 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 Heap**. +4. Select an existing Source to connect to Heap (Actions). + +{% include components/actions-fields.html %}