--- "@context": https://schema.org "@type": TechArticle "@id": https://www.twilio.com/docs/segment/connections/destinations/catalog/actions-heap#article headline: Heap (Actions) Destination description: Connect Segment to the Heap (Actions) destination to send events to Heap's analytics platform with clearer data mapping and improved setup. url: https://www.twilio.com/docs/segment/connections/destinations/catalog/actions-heap inLanguage: en dateModified: 2026-06-10T17:19:57.000Z author: "@type": Organization name: Twilio Developer Education Team publisher: "@type": Organization name: Twilio --- # Heap (Actions) Destination > \[!NOTE] > > This page is about the Heap (Actions) Destination. See below for information about other versions of the Heap destination: > > * [Heap (Classic)](/docs/segment/connections/destinations/heap) [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. > \[!TIP] > > **Good to know**: This page is about the [Actions-framework](/docs/segment/connections/destinations/actions/) Heap destination. There's also a page about the [non-Actions Heap destination](/docs/segment/connections/destinations/catalog/heap/). Both of these destinations receive data from Segment. ## 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 display the Segment icon in Heap, so you can identify the source of the event, and foster greater data trust. * **Improved setup**. Clear default settings enable you to set up faster. ## Getting started 1. From the Segment web app, navigate to **Connections** and click **Add Destination**. 2. Search for **Heap (Actions)** and click it. 3. Click **Configure Heap**. 4. Select the Source to connect to Heap (Actions). ## Destination Settings | Field | Description | Required | Type | | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | | Heap app ID | The app ID of the environment to which you want to send data. You can find this ID on the \[Projects]\(https://heapanalytics.com/app/manage/projects) page. | Yes | string | | Browser Array Limit | This is an optional setting. When set, nested array items will be sent in as new Heap events. Defaults to 0. | No | number | | Global data redaction via Disabling Text Capture | Setting to true will redact all target text on your website. For more information visit the heap \[docs page]\(https://developers.heap.io/docs/web#global-data-redaction-via-disabling-text-capture). | No | boolean | | Hostname | This is an optional setting used to set the host that loads heap-js. This setting is used when heapJS is self-hosted. In most cased this should be left unset. The hostname should not contain https or app id it will be populated like so: https://$\{hostname}/js/heap-$\{appId}.js. For more information visit the heap \[docs page]\(https://developers.heap.io/docs/self-hosting-heapjs). | No | string | | Secure Cookie | This option is turned off by default to accommodate websites not served over HTTPS. If your application uses HTTPS, we recommend enabling secure cookies to prevent Heap cookies from being observed by unauthorized parties. For more information visit the heap \[docs page]\(https://developers.heap.io/docs/web#securecookie). | No | boolean | | Tracking Server | This is an optional setting. This is used to set up first-party data collection. For most cased this should not be set. For more information visit the heap \[docs page]\(https://developers.heap.io/docs/set-up-first-party-data-collection-in-heap). | No | string | ## Available Presets Heap Web (Actions) has the following presets | Preset Name | Trigger | Default Action | | ------------- | ----------------------- | -------------- | | Track Event | Event type = "track" | Track Event | | Identify User | Event type = "identify" | Identify User | ## Available Actions Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Heap Web-supported actions: > \[!NOTE] > > Individual destination instances support a maximum of 5 mappings. * [Identify User](#identify-user-9) * [Track Event](#track-event-12) ### Identify User Sets user identity Identify User is a **Web** action. The default Trigger is `type = "identify"` | Field | Description | Required | Type | | -------- | ------------------------------------------ | -------- | ------ | | Identity | The user's identity | No | STRING | | Traits | The Segment traits to be forwarded to Heap | No | OBJECT | ### Track Event Track events Track Event is a **Web** action. The default Trigger is `type = "track"` | Field | Description | Required | Type | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------ | | Name | The name of the event. | Yes | STRING | | Properties | A JSON object containing additional information about the event that will be indexed by Heap. | No | OBJECT | | Identity | a string that uniquely identifies a user, such as an email, handle, or username. This means no two users in one environment may share the same identity. More on identify: https://developers.heap.io/docs/using-identify | No | STRING | | Anonymous ID | The segment anonymous identifier for the user | No | STRING | | User Properties | An object with key-value properties you want associated with the user. Each property must either be a number or string with fewer than 1024 characters. | No | OBJECT |