This article is part of our guide to product usage data and renewals.
Amplitude and HubSpot have a real partnership and published connectors in both directions, but neither is built to hand a renewal owner a ready-made usage-health signal. Amplitude’s data model is built around cohorts and events; HubSpot’s is built around contacts, companies, and deals. This guide covers how the two connect, why cohorts are the practical bridge between them, and how to turn Amplitude’s product analytics into a signal a renewal team can actually use.
What the Amplitude-HubSpot Connectors Actually Do
Amplitude ships two connectors relevant here:
- HubSpot as a source: pulls HubSpot CRM data (deal stage, lifecycle stage, company properties) into Amplitude, so you can analyze product usage segmented by CRM attributes, for example, comparing usage patterns between enterprise and self-serve accounts.
- HubSpot as a destination (Event Stream): pushes Amplitude events and user properties out to HubSpot, updating contact records with product usage data.
Amplitude and HubSpot also announced a partnership around product-led growth, but that’s a go-to-market alignment, not a specific renewal-health feature. In practice, both connectors are built around marketing and lifecycle use cases (lead scoring, PQL identification), not the account-level renewal rollups this guide is about. You’ll still need to build the renewal-specific layer yourself.
Cohorts Are the Practical Bridge, Not Raw Events
Amplitude’s core unit for “a group of users who share a behavior” is the cohort, for example, “accounts with zero logins in the last 30 days” or “accounts that have used fewer than two core features.” Cohorts matter here because they’re the right grain to sync to HubSpot: a cohort membership flag (yes/no, or a count) maps cleanly onto a HubSpot property. A raw Amplitude event stream does not; nobody scans a deal record for individual event rows.
The practical build:
- Define the account-level cohorts you actually care about in Amplitude first: low-usage accounts, accounts with declining feature adoption, accounts that haven’t touched a specific high-value feature.
- Sync cohort membership, not raw events, to a HubSpot property using the Event Stream destination connector or a reverse-ETL tool if you need more control over the mapping.
- Aggregate to the account level before syncing, if your B2B accounts have multiple users. Amplitude’s cohorts are usually user-level by default; a company-level rollup (percentage of the account’s users in the “low usage” cohort) is more useful on a deal than a single user’s status.
Copy This: The Exact Cohort Definition for “At-Risk Account”
Rather than a vague “define your cohorts” instruction, here’s a specific one to build first, in Amplitude’s Cohort Builder (Data → Cohorts → New Cohort):
Cohort name: Renewal Risk - Low Engagement 30d
Definition (behavioral cohort, “did” logic):
Users who
have NOT performed [Core Action Event]
in the last 30 days
AND
have performed [Login Event]
at least 1 time in the last 90 daysThe second condition matters as much as the first: it excludes brand-new trial users or accounts that never onboarded (a different problem, not a renewal risk signal) and isolates accounts that were active and have since gone quiet, the pattern that actually correlates with a nervous renewal conversation. Replace [Core Action Event] with whichever event in your Amplitude taxonomy represents real product value delivered, not a login or page view.
Then, for the account-level rollup: create a second saved computation, ”% of account users in this cohort,” grouped by your account/company ID property. That percentage, not the raw cohort membership, is what should sync to the usage_seat_utilization_pct-style property on the HubSpot deal, see the scoring model in our pillar guide for how to turn this into a full health score.
This one cohort, built correctly, is more useful than a dozen loosely defined ones. Start here before building out a larger cohort library.
What to Put on the Deal Record
Keep it to what a renewal owner would glance at before a call, the same short list regardless of which analytics tool feeds it:
- Last active date across the account, not per user
- Percentage of the account’s users in a low-usage or declining-usage cohort
- Count of core features adopted, defined by your own product’s retention-correlated features, not a generic benchmark
- Usage trend direction over the last 30 to 90 days
Everything more granular than that belongs in Amplitude, where it’s built to live, not on the HubSpot record.
Turning the Sync Into a Renewal Action
Once cohort data is landing on HubSpot properties, it needs to do something:
- Build a HubSpot workflow that flags the deal and creates a task when an account enters a risk cohort (for example, moves into “zero logins, 30 days”).
- Route the flag to the renewal owner as a task, not a passive notification.
- Keep the signal visible on the deal record itself, not in a separate Amplitude dashboard the renewal owner has to remember to check.
The full workflow build, thresholds, escalation, churn-reason taxonomy, is covered in building a churn prevention workflow in HubSpot.
What This Data Can (and Can’t) Tell You
Resist treating a cohort shift as proof an account will churn. The most detailed available research on this exact question found that no single usage metric, tested in isolation, reliably predicted renewal once relationship-strength was factored into the model. Use synced Amplitude data to prompt a conversation and feed a broader health score, not to auto-flag an account as lost. Full findings in which product usage metric actually predicts renewal.
Related Reading
- Product Usage Data and Renewals: How to Connect Pendo, Mixpanel, or Amplitude to HubSpot
- Mixpanel to HubSpot: Turning Product Events Into Renewal Signals
- Pendo HubSpot Integration: Complete Setup Guide, Costs, and Limits
- Best Product Analytics Tools to Connect to HubSpot for Renewal Health (2026)
- Building a Churn Prevention Workflow in HubSpot
Frequently Asked Questions
Does Amplitude integrate with HubSpot? Yes, Amplitude publishes both a HubSpot source connector (pulling HubSpot CRM data into Amplitude for analysis) and a destination connector (sending Amplitude event data to HubSpot). Amplitude and HubSpot also announced a formal partnership around product-led growth. The connectors are built for marketing and event data, not turnkey renewal-health scoring, so getting an account-level usage signal onto a deal still takes setup.
What is an Amplitude cohort and why does it matter for HubSpot syncing? A cohort is a saved group of users defined by shared behavior, for example, accounts with zero logins in 30 days, or accounts that haven’t used a core feature. Cohorts are the practical unit for syncing to HubSpot: build the account segment you care about as a cohort in Amplitude, then sync cohort membership to a HubSpot property or list, rather than trying to sync raw events.
Can this integration support real-time data updates? Amplitude’s HubSpot destination connector can push events close to real time, but for renewal use cases this is rarely worth the added complexity. A daily or weekly cohort sync is sufficient, since renewal decisions run on a weeks-to-months cycle.
How does the Amplitude-HubSpot integration handle data privacy and consent? Data flowing between Amplitude and HubSpot inherits whatever consent and privacy settings govern the underlying user data in each system; the integration itself doesn’t add a separate compliance layer. Under GDPR or similar regimes, treat synced usage data the same as any other personal data crossing between systems, and confirm your data processing agreements cover the sync.
How do I create HubSpot contacts automatically from new Amplitude users? Amplitude’s HubSpot destination connector can be configured to push new or updated user profiles to HubSpot as contacts, mapped through your account’s user-identification field. For B2B accounts, pair this with a company-level rollup so a burst of new individual users maps to one account record, not forty disconnected contacts.
Can Amplitude data predict which accounts will renew? Not reliably on its own. Treat cohort and event data as one input into a broader health score alongside relationship and commercial signals, not a standalone renewal predictor. See our research on which usage metric actually predicts renewal for the full evidence.
SWOTBee builds HubSpot-native renewal operations for mid-market teams: usage data synced onto the deal, health-score workflows, and alert cadences that actually get worked, all inside your portal, and you own everything we build.
Get your 1-page renewal leakage estimate →
No call needed. Prefer to talk it through first? Book a free 30-minute discovery call →
