Mixpanel
Pull event data, user profiles, cohort membership, and engagement metrics from Mixpanel into Perly for behavioral churn signals.
Overview
Product usage is one of the strongest predictors of churn. The Mixpanel integration brings behavioral data into Perly -- event streams, engagement metrics, and cohort membership -- so health scores reflect how customers actually use your product, not just what your CRM says about them.
What Perly pulls
- Event data (feature usage, page views, key actions)
- User profiles and profile properties
- Cohort membership and segment data
- Engagement metrics (DAU, WAU, MAU per customer)
- Feature adoption rates
- Session frequency and duration trends
- Funnel completion rates
This is a read-only integration. Perly never writes data back to Mixpanel.
How Perly uses analytics data
Perly transforms raw Mixpanel events into actionable health signals:
- Usage frequency drop -- a customer who logged in daily but now logs in weekly is showing disengagement.
- Feature abandonment -- stopping use of a core feature often precedes churn.
- Cohort drift -- customers falling out of high-engagement cohorts are at elevated risk.
- DAU/WAU/MAU trends -- declining ratios indicate fading stickiness.
- Onboarding stalls -- users who stop progressing through key activation milestones need intervention.
These behavioral signals are weighted alongside billing (Stripe) and CRM (HubSpot/Salesforce) data to produce a holistic health score.
Connecting Mixpanel
Connection uses service account credentials -- no OAuth flow required.
- In Mixpanel, go to Project Settings and note your Project ID.
- Navigate to Service Accounts under your organization settings and create a new service account. Copy the Secret.
- In Perly, go to Settings > Integrations and click Connect Mixpanel.
- Enter your Project ID and Service Account Secret.
- Click Save. Perly begins syncing within minutes.
Tip: Create a dedicated service account for Perly with read-only permissions. This follows the principle of least privilege and makes it easy to revoke access if needed.
Sync frequency
Perly ingests Mixpanel event data every 4 hours via the Mixpanel Export API. User profiles and cohort membership are synced every 6 hours. Engagement metrics (DAU, WAU, MAU) are recalculated daily.
On first connection, Perly backfills up to 90 days of historical event data to establish behavioral baselines.
Event mapping
You can configure which Mixpanel events Perly treats as health-positive or health-negative signals. Common mappings:
| Mixpanel event | Perly signal type | Impact |
|---|---|---|
feature_used | Engagement | Positive |
export_created | Value realization | Positive |
invite_sent | Expansion signal | Positive |
error_encountered | Friction | Negative |
support_ticket_opened | Friction | Negative |
downgrade_page_viewed | Churn intent | Negative |
Configure event mappings in Settings > Mixpanel > Signal Mapping.