Klenty Source
Good to know: Event Cloud source
The Klenty Source is an event source. This means that it sends data as events, which are behaviors or occurrences tied to a user and a point in time. Data from these sources can be loaded into your Segment warehouses, and also sent to Segment streaming destinations. Learn more about cloud sources.
This source is supported in US data processing regions.
The Klenty source is only supported in workspaces configured to process data in the US region. Workspaces configured with data processing regions outside of the US cannot connect to this source. For more information, see Regional Segment.
Klenty helps sales teams to send personalized emails and automated follow-ups at scale. With Klenty, your sales team can completely automate their email outreach and focus on closing more deals.
This source is maintained by Klenty. For any issues with the destination, contact the Klenty Support team.
This document is about a source which is in beta
This means that the Klenty Source is in active development, and some functionality may change before it becomes generally available.
Getting Started
- From your Segment UI’s Sources page click on “Add Source”.
- Search for “Klenty” within the Sources Catalog and confirm by clicking “Connect”.
- Give the Source a nickname and follow the set up flow to “Add Source”. The nickname is a label used in the Segment interface, and Segment creates a related schema name which you query against in your warehouse. The nickname can be whatever you like, but we recommend sticking to something that reflects the source itself and distinguishes amongst your environments (Eg. SourceName_Prod, SourceName_Staging, SourceName_Dev).
- Copy the Write key from the Segment UI and log in to your Klenty account - navigate to Settings > Integrations > Segment Integration and paste the key to connect.
Events
Below is a table of events that Klenty sends to Segment. These events will show up as tables in your warehouse, and as regular events in your other Destinations. Klenty will send through the userId if available.
| Event Name | Description |
| Email Sent | Email has been sent successfully |
| Email Opened | Prospect has opened the email |
| Link Clicked | Prospect has clicked the tracking link |
| Email Replied | Prospect has replied to the email sent |
| Email Bounced | Email was rejected by the email servers |
| Email Unsubscribed | Prospect has clicked the unsubscribe link |
Event Properties
Below are tables outlining the properties included in the events listed above.
| Property Name | Description |
event |
Email event type |
userId |
Prospect email ID |
email_id |
ID of the email |
fromId |
Sender email ID |
email_subject |
Subject line of the email |
link |
URL of the link clicked |
Adding Destinations
Now that your Source is set up, you can connect it with Destinations.
Log into your downstream tools and check to see that your events are populating and they contains all the properties you expect. If all your events and properties are not showing up, refer to the Destination docs for troubleshooting.
If you experience any issues with how the events arrive in Segment, contact the Klenty team.
This page was last modified: 27 Oct 2023
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!