Skip to main content

​
Setup

After selecting Appcues from our destinations catalog, you will be required to enter your Appcues Account ID (found in Appcues > Settings > Account) and API Key / API Secret (found in Appcues > Settings > API Keys). Hightouch supports syncing both Objects and Events to Appcues.

​
Syncing objects

Hightouch supports syncing to the following Appcues objects:
  • Users

​
Sync modes

Hightouch supports the following sync modes:
  • Upsert - pushes new User objects to Appcues and updates properties that change in your warehouse.

​
Record matching

User records can be matched from your source to your Appcues workspace by User ID (user_id), which is a unique identifier in Appcues for each User.

​
Field mapping

You may also sync columns from your source to Appcues’s User properties. Appcues doesn’t provide information on properties set for User objects, so you will need to type the exact name of the property you would like to map to in Appcues. These property names must be spelled correctly and are case-sensitive.

​
Sending events to Appcues

The Appcues integration also allows you to send events to Appcues with custom attributes.
To ensure syncs send each event, your event model must use a truly unique primary key. See the events syncs documentation for more information.
The three required elements of any Appcues event are the Event Name (which can be a single string used to name all events, or pulled from your warehouse per event), a Timestamp (in ISO 1806 format, or a Unix timestamp in milliseconds), and a User ID (the unique ID of the user corresponding to the event). You can also map properties that will become event attributes in Appcues.

​
Tips and troubleshooting

To see the exact API requests and responses from each sync run, use the live debugger. To get notified by Slack, PagerDuty, SMS, or email when a sync fails, set up sync alerts. If you run into an issue this page doesn’t cover, .
Last modified on January 4, 2023