Canny (Actions) Destination

Canny is a single place for all customer feedback. It saves you time managing all the feedback while keeping your customers in the loop. Let your customers post and vote on feedback from within your website or mobile app. You’ll get an organized list of feedback that you can use to inform your roadmap.

Canny maintains this destination. For any issues with the destination, contact the Canny Support team.

Benefits of Canny (Actions) vs Canny Classic

Canny (Actions) provides the following benefit over the classic Canny destination:

• Group Events. Canny (Actions) supports group events and updates or adds properties to companies.

Getting started

1. Go to your Canny Admin Segment Settings.
2. Install the integration to get your API key.
3. From the Segment web app, navigate to Connections > Catalog, then select the Destinations tab in the catalog.
4. Search for Canny (Actions) and select it.
5. Click Configure Canny (Actions).
6. Select an existing Source to connect to Canny (Actions).
7. Enter your configuration settings.
8. Enter the Canny API key in the Canny (Actions) destination settings.
9. Enable the destination and save changes.

Destination Settings

Available Presets

Canny (Actions) has the following presets:

Available Actions

Build your own Mappings. Combine supported triggers with the following Canny-supported actions:

• Group

• Identify

Group

Updates or adds properties to a company. Company is created if it does not exist.

Group is a Cloud action. The default Trigger is: type = "group"

Click to show / hide fields

Identify

Create or update a user profile in Canny.

Identify is a Cloud action.

Click to show / hide fields

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.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.