Skip to content

Heap (Actions) documentation #3184

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Heap (Actions) documentation #3184

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 38 additions & 0 deletions src/connections/destinations/catalog/actions-heap/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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/) <destination_name> Segment destination. There's also a page about the [non-Actions <destination_name> destination](/docs/connections/destinations/catalog/<destination_name>/). 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 %}