# Gainsight PX Cloud (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 **Gainsight Px Cloud (Actions)** 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.

[Gainsight PX](https://www.gainsight.com/product-experience/analytics/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) provides a personalized product experience platform to help companies acquire, retain, and grow customers by creating real-time, personalized engagements driven by product usage data. With Gainsight PX, companies can implement an effective product-led go-to-market strategy that will increase product adoption and customer lifetime value.

This destination is maintained by Gainsight PX. For any issues with the destination, [contact the Gainsight PX Support team](mailto:pxsupport@gainsight.com).

> **Good to know**: This page is about the [Actions-framework](/docs/segment/connections/destinations/actions/actions-gainsight-px-cloud) Gainsight PX Cloud Segment destination. There's also a page about the [non-Actions Gainsight PX Cloud destination](/docs/segment/connections/destinations/catalog/gainsight-px-cloud-server). Both of these destinations receive data from Segment.

## Benefits of Gainsight PX Cloud (Actions) vs Gainsight PX Cloud Classic

Gainsight PX Cloud (Actions) provides the following benefits over the classic Gainsight PX Cloud destination:

* **Data Center Support**. The new Actions-based integration allows for the selection of the PX datacenter. This is required for any PX customers based in any data center other than the main US datacenter (accessed via app.aptrinsic.com).

## Getting started

1. From the Segment web app, navigate to **Connections > Catalog** and select the **Destinations** tab.
2. Search for *Gainsight PX Cloud (Actions)* and select it.
3. Click **Add destination**.
4. Select an existing Source to connect to Gainsight PX Cloud (Actions).
5. Find your Gainsight PX key.
   * Log in to Gainsight PX and navigate to **Settings > Products > Web App**. Enter the URL for your web application and click the **Generate** button. The Tag Key is the value that begins with "AP-" to the right of the URL value. Copy the value to your clipboard.
6. Paste the Gainsight PX Tag Key into the Segment connection settings API Key field.
7. Choose the appropriate data center value in the "Other Settings" Data Center dropdown. If you access the PX instance with app.aptrinsic.com, select 'United States', otherwise, choose the appropriate selection based on the suffix after "app-" in the application's URL.

## Destination Settings

| Field       | Description                                                                          | Required | Type     |
| ----------- | ------------------------------------------------------------------------------------ | -------- | -------- |
| API Key     | Gainsight PX API key. You can find this key in the "Administration/Products" screen. | Yes      | password |
| Data center | The PX data center where your PX subscription is hosted.                             | Yes      | select   |

## Available Presets

Gainsight Px Cloud (Actions) has the following presets

| Preset Name     | Trigger                 | Default Action |
| --------------- | ----------------------- | -------------- |
| Identify User   | Event type = "identify" | Send Event     |
| Track Page View | Event type = "page"     | Send Event     |
| Track Event     | Event type = "track"    | Send Event     |
| Group User      | Event type = "group"    | Send Event     |

## Available Actions

Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Gainsight Px Cloud-supported actions:

> \[!NOTE]
>
> Individual destination instances have support a maximum of 50 mappings.

* [Identify User](#identify-user-18)
* [Group Identify User](#group-identify-user-1)
* [Track Event](#track-event-30)
* [Track Page View](#track-page-view-3)
* [Send Event](#send-event-3)

### Identify User

Set the user ID for a particular device ID or update user properties

Identify User is a **Cloud** action. The default Trigger is `type = "identify"`

This action does not have any fields.

### Group Identify User

Updates or adds properties to an account. The account is created if it does not exist.

Group Identify User is a **Cloud** action. The default Trigger is `type = "group"`

This action does not have any fields.

### Track Event

Send an event to Gainsight PX

Track Event is a **Cloud** action. The default Trigger is `type = "track"`

This action does not have any fields.

### Track Page View

Send a page view event to Gainsight PX

Track Page View is a **Cloud** action. The default Trigger is `type = "page"`

This action does not have any fields.

### Send Event

Send entire event payload to Gainsight PX

Send Event is a **Cloud** action.

| Field         | Description           | Required | Type   |
| ------------- | --------------------- | -------- | ------ |
| Segment Event | The raw Segment event | 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 Gainsight PX Cloud (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     |
| ----------- | ------------------------------------------------------------------------------------ | -------- | -------- |
| API Key     | Gainsight PX API key. You can find this key in the "Administration/Products" screen. | Yes      | password |
| Data center | The PX data center where your PX subscription is hosted.                             | Yes      | select   |