Connect Reverse ETL Source to Gainsight PX Audience

Private Beta

Configure a Reverse ETL source with your Gainsight PX Audience destination.

4 minute read

The Gainsight PX Audience destination is in Private Beta.
Reach out to Customer Success to enable it for your workspace.

This guide takes you through the steps to connect a Reverse ETL source to your Gainsight PX Audience destination.

Before you start, make sure to complete the prerequisites — create the Boolean custom user attribute in Gainsight PX, and get a REST API key and your data center.

Setup

Set up and configure your Reverse ETL source.
In the Overview tab of the source page, click Add destination > Create new destination. You can also select an already-configured destination here.
From the list of destinations, select Gainsight PX Audience and click Continue.
Specify a unique name to identify this destination in RudderStack.
In the Gainsight PX account section, click Select to choose an existing account. To add a new account, click Add account, and specify the following settings:

Setting	Description
Account name	Specify a unique account name.
REST API key	Enter your Gainsight PX REST API key. Create it in Gainsight PX under Administration > REST API with Read and Write permission.
Data center	Select the data center of your Gainsight PX subscription: `US`, `EU`, or `US2`. Match the host of your Gainsight PX URL — `app` for `US`, `app-eu` for `EU`, `app-us2` for `US2`.

Proceed to configure the mapping settings.

Mapping settings

This section lists the settings to correctly map data from your Reverse ETL source to the Gainsight PX Audience destination.

Members who are not yet Gainsight PX users are reported as failed rows until they exist in Gainsight PX; no users are created.

Attribute API name

Enter the API name of the Boolean custom user attribute in Gainsight PX that stores membership for this sync (for example, rs_trial_power_users).

The attribute must already exist in Gainsight PX as an enabled Boolean custom user attribute.
API names are case-sensitive. Use the API name, not the display name.
Allowed characters: letters, numbers, and underscores, maximum length 200.
You can’t change the attribute once the connection exists. To use a different attribute, create a new sync.

Sync mode

Only Mirror mode is supported for this integration. There is no sync mode selector in the UI.

Map user identifier

Map exactly one warehouse column to the Gainsight PX user ID, identifyId. The values must match the user IDs in Gainsight PX exactly, including case.

Setup validation

When you create the connection, RudderStack checks the account and the attribute against Gainsight PX. The connection is saved only if:

The API key is valid for the selected data center and has Read permission.
An attribute with that exact API name exists, is a custom attribute (not built in), is of type Boolean, and is enabled.
Exactly one column is mapped to identifyId.

Editing an existing connection in the RudderStack dashboard or through the API doesn’t re-run this check.

If a check fails, the form shows the reason. See Troubleshooting for each message and how to fix it.

Sync settings

RudderStack determines how and when to run a sync based on the sync schedule you set for your Reverse ETL connection.

Schedule type	Description
Basic	Run syncs at a set interval, optionally starting from a specified time (UTC). If a start time is set, syncs run from that time until the end of that day.
CRON	Run syncs based on a specified CRON expression (in UTC).
Manual	Run syncs manually.

Sync observability settings

Setting

Description

Retain sync logs

This setting is toggled on by default and instructs RudderStack to store the sync logs in your warehouse. You can also configure the below settings:

Setting	Description
Sync log retention	Specify the retention period of the sync logs in your warehouse. If you set it to 1, then RudderStack deletes any sync log older than a day (in UTC time).
Snapshot table retention	Specify the number of snapshot tables to retain.

Retry failed records

This setting is toggled on by default and causes RudderStack to continually retry sending the failed records.

Retain and show failures

This setting is toggled off by default. Turn it on to have RudderStack write the error recorded for every failed record to a failed records table in your warehouse and show it in the sync’s failed records view. It applies from the next sync and can take up to a minute to reach your data plane.

Setting	Description
Failure retention	Number of days RudderStack keeps each sync’s failed records in your warehouse. The default is 30 and the minimum is 7.

Storing sync logs, snapshot tables, and failed records may incur additional warehouse costs.

Avoid Reset History and Full Sync for this destination. A full sync sets the attribute to true for everyone currently in the source but never sets it to false for anyone who left before that run, so those users keep true until they re-enter and leave again. See Limitations.