Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Canny (Actions) Destination


Destination Info
  • Accepts Page, Alias, Group, Identify and Track calls.
  • Refer to it as Canny (Actions) in the Integrations object
  • This integration is partner owned. Please reach out to the partner's support for any issues.

Canny(link takes you to an external page) 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.

(success)

Success!

Good to know: This page is about the Actions-framework Canny Segment destination. There's also a page about the non-Actions Canny destination. Both of these destinations receive data from Segment.


Benefits of Canny (Actions) vs Canny Classic

benefits-of-canny-actions-vs-canny-classic page anchor

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.

  1. Go to your Canny Admin Segment Settings(link takes you to an external page).
  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.

Property nameTypeRequiredDescription
API Keystring
required

You can find your API Key in the Segment Integration page in your admin settings.


Canny (Actions) has the following presets

Preset NameTriggerDefault Action
Create or update a CompanyEvent type = "group"Group
Create or update a UserEvent type = "identify"Identify

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

(information)

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Group

group page anchor

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"

Property nameTypeRequiredDescription
Group IDSTRING
required

The unique identifier of the group.


Group PropertiesOBJECT

Optional

Properties to set on the group profile


TypeSTRING
required

The type of the event


User IDSTRING

Optional

The unique identifier of the user.

Create or update a user profile in Canny.

Identify is a Cloud action.

Property nameTypeRequiredDescription
User IDSTRING
required

A distinct ID of an identified (logged in) user.


User PropertiesOBJECT

Optional

Properties to set on the user profile


TypeSTRING
required

The type of the event


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(link takes you to an external page).

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.

(information)

Real-time to batch destination sync frequency

Real-time audience syncs to Canny (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.


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

Property nameTypeRequiredDescription
API Keystring
required

You can find your API Key in the Segment Integration page in your admin settings.