Usage integrations allow you to bring product usage and event data directly into ChurnZero from supported product analytics and engagement platforms. For example, teams can track feature adoption, spot disengaged accounts early, and trigger proactive outreach when usage drops.
By connecting your usage data sources to ChurnZero, you can enrich account and contact records with real product activity and use that data to power segmentation, health scoring, and other automated engagement. These integrations reduce the need for custom data pipelines or manual imports and help teams understand how customers are actually using your product.
This article provides a high-level overview of how ChurnZero usage integrations work, what types of usage data they support, and where to find setup instructions for each platform.
What Usage Integrations Do in ChurnZero
Usage integrations securely connect your product analytics or engagement platform to your ChurnZero tenant using an authorized connection or configured destination. Once connected, ChurnZero syncs supported usage events as structured usage data. Depending on the integration, usage data may include feature events, page views, custom product events, login activity, or other tracked actions performed by users within your application.
Most usage integrations are designed as one-way syncs from the source platform into ChurnZero. Usage data flows one-way into ChurnZero to support visibility and customer success workflows.
How Usage Data Syncing Works
Usage integrations rely on Account External IDs and Contact External IDs to correctly associate incoming events to the right accounts and users in ChurnZero. The source platform must provide the necessary account and user information for accurate mapping.
Sync behavior varies by platform. Some integrations send usage data to ChurnZero in real time, while others run on scheduled intervals. Certain platforms provide individual event instances, while others send summarized event counts that ChurnZero expands into individual usage events for reporting consistency.
Because each usage platform handles events and timestamps differently, integration-specific behavior (such as historical data limits, sync frequency, and metadata availability)is documented in the individual setup articles.
Supported Usage Platforms
ChurnZero supports Usage Native Integrations with the following platforms:
Each platform has its own setup guide that outlines authorization steps, required identifiers, supported event types, and integration-specific rules.
What You Configure During Usage Integration Setup
While setup steps vary by platform, most usage integrations require you to:
Authorize the connection or configure ChurnZero as a destination within the source platform
Provide or confirm the Account External ID and Contact External ID fields used for mapping
Define the list of usage events that should sync to ChurnZero
Optionally provide friendly or “pretty” names for events to make them easier for Customer Success teams to interpret
Most customers intentionally limit the number of usage events sent to ChurnZero to only those that are meaningful for customer health, adoption tracking, and engagement workflows.
Who Should Use Usage Native Integrations
Usage integrations are recommended for teams that want deeper visibility into how customers interact with their product. They are especially useful for:
- Tracking feature adoption and engagement trends
- Building health scores based on real product usage
- Triggering alerts, tasks, or journeys based on usage behavior
- Identifying at-risk or expanding accounts through changes in activity
Usage integrations are often implemented after a CRM integration is in place, once the account and contact records are already established in ChurnZero.
Next Steps
To get started, review the setup guide for your specific usage platform to understand authorization requirements and data mapping rules. If you have questions about which usage integration is right for your use case, or need help defining which events to sync, contact ChurnZero Support or your CSM for guidance.
Comments
0 comments
Article is closed for comments.