Churned Destination
Destination Info
- Refer to it as Churned in the Integrations object
Partner Owned
- This integration is partner owned. Please reach out to the partner's support for any issues.
Churned is an AI-powered customer success platform for subscription businesses, eliminating the need for 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.
Getting started
- From your workspace’s Destination catalog page search for “Churned”
- Select “Churned” and click Add Destination
- Choose which Source should send data to the “Churned” destination.
- 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.
Page
Send Page calls. For example:
analytics.page();
Segment sends Page calls to Churned as a pageview
.
Identify
Send Identify calls. For example:
analytics.identify("userId123", {
email: "john.doe@example.com",
});
Segment sends Identify calls to Churned as an identify
event.
Track
Send Track calls. For example:
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 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.
Real-time to batch destination sync frequency
Real-time audience syncs to Churned may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.
Settings
Segment lets you change these destination settings from the Segment app without having to touch any code.
Setting | Description |
---|---|
API Key (required) |
string . Your Churned API key |
This page was last modified: 04 Jun 2024
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!