Kana Destination

Kana provides pricing infrastructure for internet businesses. This destination allows for a low-code integration of Kana, using Segment events to record the usage of your features in order to measure entitlement, gain insights and ensure customers are charged correctly.

This destination is maintained by Kana. For any issues with the destination, contact the Kana team.

Getting Started

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for “Kana” in the Destinations Catalog, and select the “Kana” destination.
3. Choose which Source should send data to the “Kana” destination.
4. Go to the API Key page within the Kana dashboard.
5. Copy the API Key from ‘Admin API (Backend) Key’.
6. Enter the API Key in the Kana destination settings in Segment.

Supported methods

Kana supports the following methods, as specified in the Segment Spec.

Identify

Send Identify calls to create, update, merge and identify users in Kana.

analytics.identify('userId123', {
  name: "John Doe",
  email: 'john.doe@example.com',
  billingId: 'cus_Lp1bSKob4laHDD'
});

Kana looks for the following traits in Identify events which map to user fields in Kana:

Creating, updating or merging

Kana looks at the userId and email to determine when to create, update or merge a user. The userId takes precedence as the canonical identifier. Kana allows for multiple users to have the same email.

See more on how creating, updating and merging works.

Track

Send Track calls to Kana in order to record when a customer has used a particular feature. For example:

analytics.track('Message Sent', {
  featureId: 'messages',
  delta: 1
});

Kana looks at all properties in Track events for mapping rules. However, Kana considers the following properties to be special:

Mapping Rules

There are two ways to map Segment events to Kana features:

• Providing a properties.featureId field within a Segment event
• Setting rules to map events to features within the Kana dashboard

The latter can be used as a no-code solution (which also won’t muddy data to other destinations), whereby Kana will look at incoming events and process them alongside rules you have defined to attribute them to features.

These rules can be created on the Segment Integration page within the Kana dashboard. They can be set based on the name and properties of a track event with multiple AND conditions if required.

See more on how to setup rules in the Kana dashboard.

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.