# Klenty Source

## Source Info

* The Klenty Source is an **Event Cloud** 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.](/docs/segment/connections/sources#cloud-app-sources)
* This integration is **partner owned** . Please reach out to the partner's support for any issues.

> \[!WARNING]
>
> This 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](/docs/segment/guides/regional-segment/).

[Klenty](https://www.klenty.com/) 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](mailto:support@klenty.com).

> \[!IMPORTANT]
>
> This means the feature is actively being developed, and some functionality may change before it becomes generally available.

## Getting started

1. From your Segment UI's Sources page click on **Add Source**.
2. Search for *Klenty* within the Sources Catalog and confirm by clicking **Connect**.
3. Give the source a nickname and follow the set up flow to add your 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 (for example, Klenty\_Prod, Klenty\_Staging, Klenty\_Dev).
4. 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

The following table lists 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

The following table outlines the properties included in the events.

| 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 to destinations.

Log in to 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 relevant destination docs for troubleshooting.

If you experience any issues with how the events arrive in Segment, [contact the Klenty team](mailto:support@klenty.com).