Appcues (Actions) Destination
Appcues adds an in-app experience layer to your product, enabling you to deliver user onboarding flows, NPS surveys, and feature announcements with reduced engineering effort.
This destination is maintained by Appcues. For any issues with the destination, contact the Appcues support team.
- From your workspace's destination catalog, search for Appcues.
- Select Appcues (Actions) and click Add destination.
- Select an existing source to connect to Appcues (Actions).
- In the Appcues settings page, get the following credentials:
- Copy your Account ID.
- Generate or copy your API Key.
- Generate or copy your API Secret.
- Note your Region (US or EU).
- Enter the Account ID, API Key, API Secret, and Region in the Appcues (Actions) destination settings in Segment.
If you're currently using the classic Appcues destination to send events server side to Appcues, you can migrate to the Appcues (Actions) destination to take advantage of improved functionality and easier configuration. The Appcues (Actions) destination provides:
- Server-side event delivery with improved reliability.
- Support for Track, Identify, Page, Screen, and Group events through a unified action.
- Better control over which events are sent to Appcues.
- Consistent behavior across all event types.
To migrate:
- Set up the Appcues (Actions) destination following the steps in Getting started.
- Configure the Send action with your desired event mappings.
- Test the integration to ensure events are flowing as expected.
- Once validated, disable the classic Appcues destination.
Appcues supports regional data residency. When you configure the destination, choose the region that matches your Appcues account:
- US: Data is stored in infrastructure located in the United States.
- EU: Data is stored in infrastructure located in the European Union.