---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/segment/connections/destinations/catalog/churned#article
headline: Churned Destination
description: Connect the Segment Churned destination to send Page, Identify, and Track data to Churned, an AI-powered customer success platform that predicts churn.
url: https://www.twilio.com/docs/segment/connections/destinations/catalog/churned
inLanguage: en
dateModified: 2026-07-15T17:40:17.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# Churned Destination

## Destination Info

* Refer to it as **Churned** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.

[Churned](https://www.churned.io/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) is an artificial intelligence (AI)-powered customer success platform for subscription businesses, replacing rule-based decision making with live AI-driven actions. It uses machine learning to predict churn and drive customer retention.

This destination is maintained by Churned. For any issues with the destination, [contact the Churned Support team](mailto:info@churned.io).

## Getting started

To set up the Churned destination, follow these steps:

1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog) search for "Churned"
2. Select "Churned" and click **Add Destination**
3. Choose which Source should send data to the "Churned" destination.
4. Enter the **API Key** you've received from Churned in the "Churned" destination settings in Segment.

## Supported methods

Churned supports the following methods, as specified in the [Segment Spec](/docs/segment/connections/spec).

### Page

Send [Page](/docs/segment/connections/spec/page) calls. For example:

```js
analytics.page();
```

Segment sends Page calls to Churned as a `pageview`.

### Identify

Send [Identify](/docs/segment/connections/spec/identify) calls. For example:

```js
analytics.identify("userId123", {
  email: "john.doe@example.com",
});
```

Segment sends Identify calls to Churned as an `identify` event.

### Track

Send [Track](/docs/segment/connections/spec/track) calls. For example:

```js
analytics.track("Login Button Clicked");
```

Segment sends Track calls to Churned as a `track` event.

## Engage

You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo).

For user-property destinations, an [identify](/docs/segment/connections/spec/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.

| Field   | Description          | Required | Type   |
| ------- | -------------------- | -------- | ------ |
| API Key | Your Churned API key | Yes      | string |
