Gleap (Actions) Destination

On this page

Destination Info
Partner Owned
  • This integration is partner owned. Please reach out to the partner's support for any issues.

Gleap 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.

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.
  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

Setting Description
Secret API token Required.

Found in Project settings -> Secret API token.

Available Actions

Build your own Mappings. Combine supported triggers with the following Gleap (Action)-supported actions:

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

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"

Click to show / hide fields

Field Description
Event Name Type: STRING

The name of the event that occurred. Names are treated as case insensitive. Periods and dollar signs in event names are replaced with hyphens.
Event Timestamp* Type: DATETIME

The time the event took place in ISO 8601 format. Segment will convert to Unix before sending to Gleap.
User ID* Type: STRING

Your identifier for the user who performed the event. User ID is required.
Event Metadata Type: OBJECT

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.
Enable Batching? Type: BOOLEAN

When enabled, Segment will send events in batches.

Identify Contact

Create or update a contact in Gleap

Identify Contact is a Cloud action. The default Trigger is: type = "identify"

Click to show / hide fields

Field Description
User ID* Type: STRING

A unique identifier for the contact.
First name Type: STRING

The contact’s first name.
Last name Type: STRING

The contact’s last name.
Email Address Type: STRING

The contact’s email address.
Phone Number Type: STRING

The contact’s phone number.
Company Name Type: STRING

The contact’s company name.
Company ID Type: STRING

The contact’s compan ID
Language Type: STRING

The user’s language.
Subscription Plan Type: STRING

The user’s subscription plan.
User Value Type: NUMBER

The user’s value.
Last Page View Type: STRING

The page where the contact was last seen.
Signed Up Timestamp Type: DATETIME

The time specified for when a contact signed up.
Last Seen Timestamp Type: DATETIME

The time when the contact was last seen.
Custom Attributes Type: OBJECT

The custom attributes which are set for the contact.

Engage

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an 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.

Real-time to batch destination sync frequency

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.

Setting Description
Secret API token
(required)		 string. Found in Project settings -> Secret API token.

This page was last modified: 07 Aug 2024

Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
or
Create free account

Was this page helpful?