Note: This is different from Canny's built-in user segmentation function.
Overview
Canny's integration with Segment.com lets you easily capture users from your Segment sources and makes them available in Canny. Rich customer data will help inform your product decisions. Your users will also be instantly available for voting-on-behalf.
Benefits
Pass user data into Canny to add context around feedback
Build user segments easily
Automatically sync updates to user and company data
How to Install
Before you begin
Owner-level admin permissions in Canny are required to connect the integration.
You will also need to be an admin in Segment.
Installation steps
1. Go to your Segment settings page and copy the API key to use with Segment's app catalog.
2. Once copied, head to Canny in the Segment Catalog and click "Add destination"
3. Once you arrive at the setup screen, set up your destination.
(This lets Segment know where to send data. Select your data source and set up your destination).
From there, you can enter your API key into the API key field. Make sure to enable the "Enable Destination" toggle, then save the changes.
The Segment integration currently supports two actions:
"Identify" and "Group"
Identify Action
The "Identify" action updates a user profile in Canny. If the user does not exist in Canny, they will be created.
The fields traits.email and traits.name are required, without them, the "Identify" call will return an error. If you'd like to pass additional custom fields, the title of the field needs to be preceded by traits for the field to be recognized by Canny.
Custom fields must:
Have names that are less than 30 characters long
Have values that are of types: boolean, number, string, null or undefined
Sending custom fields that do not meet the above requirements may result in an error or fields not being saved.
If a user needs to be associated with a company, the traits.company field should be provided. The company object can contain any fields that are accepted through the Canny API. If a company is sent through a user's "Identify" request and does not exist, it will be created.
Group Action
The "Group" action updates or adds properties to a company. If the company does not exist in Canny, it will be created.
The field traits.name is required if the trait object is being sent, without it the "Group" call will return an error. If you'd like to also pass custom fields, the title of the field needs to be preceded by traits for the field to be recognized by Canny.
Custom fields must:
Have names that are less than 30 characters long
Have values that are of types: boolean, number, string, null or undefined
Sending custom fields that do not meet the above requirements may result in an error or fields not being saved.
Mapping Custom Fields
To sync custom fields to Canny, simply click on the "Mappings" heading on the page. Once there, click on the 3 dots of the trigger, and edit the mapping. From there, you can adjust your data mapping.
Note: when testing through the Segment UI that your mapped data is sent to Canny correctly, please make sure you have PII enabled for your Segment user. Otherwise, Segment will not be able to map your email field as expected and this will result in an error from Canny.
If you'd like to import more than the default user traits (e.g. name, email), you can import Segment's other user traits into Canny as Custom Fields.
Once you've added your custom fields, click the "Save" button, and you're done! 😄
Things to note:
Groups in Segment cannot be passed to Canny. Only the attributes in Segment can be sent
User segments can be built using the attributes passed over to group customers
Segment is available on all paid plans, excluding the legacy Starter plan.
As always, feel free to message us using the Intercom chat or reach out to support@canny.io if you need help!