Kable Destination

Kable helps API companies launch and grow their business with easy-to-use billing infrastructure and analytics tools that work at any scale.

The fastest-growing API companies trust Kable to automate their revenue operations, improve their developer experience, and empower their product leaders to iterate on pricing and packaging without limitations or bottlenecks.

This Segment destination is maintained by Kable. For any questions or issues, please contact Kable Support.

Getting Started

1. From the Segment web app, click Catalog then Destinations.
2. Search for Kable in the Destinations Catalog, and select Kable.
3. Click Configure Kable.
4. Choose which Source(s) should send data to Kable, and add a name for your Kable Segment Destination.
5. Configure your Segment Connection Settings:
   • Add your Kable Client ID and Kable API Key. (You can find your Kable Client ID and API Keys in the Company tab of your Kable dashboard.)
   • Specify which Segment event field corresponds to your customer’s Client ID on Kable.
   • Map any other Segment event properties to Kable event fields.

Supported methods

Kable supports Segment Track calls to capture usage metrics from your API. Learn more about Segment Track calls in the Segment Spec.

Track

Send Track calls to Segment to record usage events in Kable. For example:

analytics.track({
  event: "your_event_type",
  userId: "yourcompanyuser_1234567890",
  properties: {
    segmentX: "important data point",
    messageId: "msg_ABC123XYZ456", 
    objectCount: 12, 
    bankAccountBalance: 399.99,
  }
});

The Segment Track event above would be transformed and transmitted to Kable as:

curl --request POST \
     --url https://live.kable.io/api/v1/events/create \
     --header 'Accept: application/json' \
     --header 'Content-Type: application/json' \
     --header 'Kable-Client-ID: <YOUR_KABLE_CLIENT_ID>' \
     --header 'Kable-Client-Secret: <YOUR_KABLE_CLIENT_SECRET>' \
     --data '
{
  "clientId": "messageId",
  "timestamp": "2022-01-09T09:32:01Z", # Segment timestamp
  "transactionId": "022bb90c-bbac-11e4-8dfc-aa07a5b093db", # Segment messageId
  "data": {
    "kableX": "important data point", # notice the property mapping here from the example above
    "messageId": "msg_ABC123XYZ456", 
    "objectCount": 12, 
    "bankAccountBalance": 399.99
  }
}

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.