# Gleap (Actions) Destination ## Destination Info * Accepts [Page](/docs/segment/connections/spec/page), [Alias](/docs/segment/connections/spec/alias), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls. * Refer to it as **Gleap (Action)** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object) * This integration is **partner owned.** Please reach out to the partner's support for any issues. * This destination is **Beta.** [Gleap](https://gleap.io/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) is a customer feedback platform designed for apps and websites. It offers a suite of tools including visual bug reporting, live chat, AI customer support, public roadmaps, marketing automation, and more, aimed at enhancing customer success and product improvement. This destination is maintained by Gleap. For any issues with the destination, [contact their Support team](mailto:hello@gleap.io). ## 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 Gleap**. 4. Select an existing Source to connect to Gleap (Actions). 5. To use the Gleap destination, obtain an API key by signing up at [app.gleap.io](https://app.gleap.io). 6. Once registered, navigate to **Project > Settings > Security** in the Gleap dashboard. 7. Copy the API key and paste it into the Segment Gleap destination settings. ## Destination Settings | Field | Description | Required | Type | | ---------------- | ------------------------------------------------------ | -------- | -------- | | Secret API token | Found in \`Project settings\` -> \`Secret API token\`. | Yes | password | ## Available Actions Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Gleap (Action)-supported actions: > \[!NOTE] > > Individual destination instances have support a maximum of 50 mappings. * [Track Event](#track-event-2) * [Identify Contact](#identify-contact) ### Track Event Submit an event to Gleap. Track Event is a **Cloud** action. The default Trigger is `type = "track" or type = "page" or type = "screen"` | Field | Description | Required | Type | | ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------- | | Event Name | The name of the event that occurred. Names are treated as case insensitive. Periods and dollar signs in event names are replaced with hyphens. | No | STRING | | Event Timestamp | The time the event took place in ISO 8601 format. Segment will convert to Unix before sending to Gleap. | Yes | DATETIME | | User ID | Your identifier for the user who performed the event. User ID is required. | Yes | STRING | | Event Metadata | Optional metadata describing the event. Each event can contain up to ten metadata key-value pairs. If you send more than ten keys, Gleap will ignore the rest. | No | OBJECT | | Enable Batching? | When enabled, Segment will send events in batches. | No | BOOLEAN | ### Identify Contact Create or update a contact in Gleap Identify Contact is a **Cloud** action. The default Trigger is `type = "identify"` | Field | Description | Required | Type | | ------------------- | ---------------------------------------------------- | -------- | -------- | | User ID | A unique identifier for the contact. | Yes | STRING | | First name | The contact's first name. | No | STRING | | Last name | The contact's last name. | No | STRING | | Email Address | The contact's email address. | No | STRING | | Phone Number | The contact's phone number. | No | STRING | | Company Name | The contact's company name. | No | STRING | | Company ID | The contact's compan ID | No | STRING | | Language | The user's language. | No | STRING | | Subscription Plan | The user's subscription plan. | No | STRING | | User Value | The user's value. | No | NUMBER | | Last Page View | The page where the contact was last seen. | No | STRING | | Signed Up Timestamp | The time specified for when a contact signed up. | No | DATETIME | | Last Seen Timestamp | The time when the contact was last seen. | No | DATETIME | | Custom Attributes | The custom attributes which are set for the contact. | No | OBJECT | ## Engage You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo). For user-property destinations, an [identify](/docs/segment/connections/spec/identify/) call is sent to the destination for each user being added and removed. The property name is the snake\_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property `order_completed_last_30days: true`. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to `false`. When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync. > \[!NOTE] > > Real-time audience syncs to Gleap (Actions) may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected. ## Settings Segment lets you change these destination settings from the Segment app without having to touch any code. | Field | Description | Required | Type | | ---------------- | ------------------------------------------------------ | -------- | -------- | | Secret API token | Found in \`Project settings\` -> \`Secret API token\`. | Yes | password |