Kevel Destination

1. From the Segment web app, click Catalog.
2. Search for "Kevel" in the Catalog, select it, and choose which of your sources to connect the destination to.
3. In the Kevel App, click the Information icon in the top-right navigation to find your Network ID.
4. Still in the Kevel app, go to Settings -> API Keys in the top navigation. Either copy an existing key, or generate a new one.
5. Back in the Kevel destination settings in the Segment app, enter the values for the Network ID and the API Key.

If you aren't familiar with the Segment Spec, take a look at the Identify method documentation to learn about what it does. An example call would look like:

1
analytics.identify('userId123', {
2
  email: 'john.doe@example.com'
3
});

Segment sends Identify calls to Kevel as UserDB updates. Traits with boolean values are stored as interests on the UserDB Record. Other traits are stored in the custom property.

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.

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