HubSpot Data Enrichment: Add Product Usage Data to Your CRM

Quick answer: HubSpot's native enrichment adds firmographics and company data, but it doesn't include product usage signals. To enrich HubSpot with behavioral data like feature adoption, login frequency, and engagement depth, you need to sync product usage directly from your database to HubSpot contact and company records.

• Native HubSpot enrichment - Covers company size, industry, social profiles. Doesn't include what users actually do in your product.
• Reverse ETL from a warehouse - Syncs product data but requires a data warehouse, engineering setup, and ongoing maintenance ($350-$800/mo plus warehouse costs).
• Direct product sync (Zoody) - Connects your product database to HubSpot, syncs usage data in real time. No warehouse, no code, $149/mo.
• Custom API integration - Full control, but requires engineering time to build and maintain.

What Is HubSpot Data Enrichment?

Data enrichment is the process of adding external data to your CRM contact and company records to fill in gaps. Instead of manually researching company size, industry, or job titles, enrichment tools pull that information from third-party datasets and write it back to your CRM automatically.

HubSpot's native enrichment runs in the background after you create a contact or company record. It pulls firmographic data (employee count, revenue range, industry classification), social profiles (LinkedIn, Twitter), and basic company information from commercial datasets like Clearbit, ZoomInfo, and others. This happens automatically when you add a new contact with an email domain HubSpot recognizes.

For sales and marketing teams focused on outbound or account-based campaigns, this enrichment is genuinely useful. It saves time on manual research and lets you segment by company size or industry without scraping LinkedIn profiles yourself.

HubSpot's Native Enrichment: What's Included

HubSpot enrichment populates fields like:

• Company name, domain, industry, and employee count
• Annual revenue estimates
• Headquarters location and geographic data
• Social media profile URLs
• Technologies used (for some records)

These fields live on the company record in HubSpot and auto-populate when you create a new contact with a valid business email domain. HubSpot pulls this data from its enrichment partners and writes it to the standard company properties.

You can view enrichment data in the company sidebar and use it in workflows, lists, and reports. The data updates periodically as the third-party providers refresh their datasets.

The Missing Piece: Product Usage and Behavioral Data

HubSpot's enrichment tells you who your contacts are (company size, industry, role), but it doesn't tell you what they're doing in your product. It can't tell you if a user logged in yesterday, which features they've adopted, whether they hit a usage limit, or if engagement is dropping off.

For RevOps teams at product-led growth (PLG) companies, this is the gap that kills conversion and expansion campaigns. You can segment by company size all day, but a 50-person company that hasn't logged in for two weeks is not a qualified lead. A solo founder who just activated three core features in the last 24 hours is.

Product usage data lives in your application database, your product analytics tool, or your event stream. HubSpot's native enrichment doesn't connect to any of those sources. To get behavioral signals into HubSpot, you need a separate sync mechanism.

Why Product Usage Data Is Critical for Modern RevOps

The shift to product-led growth changed what RevOps teams need from their CRM. When your go-to-market motion starts with a free trial or freemium product, firmographic data is context, not intent. A contact's company size matters, but it doesn't predict whether they'll convert to paid, expand to a higher tier, or churn next month.

Product usage data is the signal that shows actual intent. It tells you which users are getting value, which features drive conversion, and which accounts are at risk.

Firmographics Tell You Who, Product Data Shows Intent

Firmographic enrichment answers questions like:

• What industry are they in?
• How big is their company?
• What's their job title?

Product usage data answers:

• Did they activate the core workflow?
• How often do they log in?
• Are they hitting usage limits or staying well below their plan?
• Which features are they using, and which are they ignoring?

A Director of Marketing at a 200-person SaaS company looks great on paper. But if they signed up three weeks ago and haven't logged in since day two, they're not a priority. A solo founder at a 5-person startup who logged in 12 times last week and set up integrations on three of your key features is the lead your sales team should call.

Tracking product usage in HubSpot gives your RevOps team the behavioral layer that firmographics can't provide. You can score leads by engagement, trigger workflows based on feature adoption, and route high-intent users to sales before they go cold.

The RevOps Problem: Disconnected Product and CRM Data

Most PLG companies run product analytics in one tool (Mixpanel, Amplitude, PostHog) and customer data in HubSpot. Product data stays in the analytics tool, CRM data stays in HubSpot, and the two never meet.

Your sales team sees company size and email domain in HubSpot. They don't see that the contact just invited four teammates, upgraded to a paid plan feature, or stopped logging in two weeks ago. Your marketing team builds nurture campaigns based on signup date and industry, not on whether the user actually completed onboarding.

This disconnect means:

• Sales wastes time calling contacts who tried the product once and left
• Marketing sends feature announcements to users who haven't adopted the prerequisite feature
• Customer success doesn't get early churn signals until the renewal conversation
• PQL scoring models rely on guesswork instead of actual product engagement

Getting product usage data into HubSpot closes this gap. When behavioral signals live on the contact record, your entire go-to-market team works from the same source of truth.

How to Enrich HubSpot with Product Usage Data (Without Reverse ETL)

The traditional way to sync product data into HubSpot is a reverse ETL pipeline: you set up a data warehouse (Snowflake, BigQuery, Redshift), model your product usage data in the warehouse using dbt or SQL transformations, then use a reverse ETL tool (Hightouch, Census) to sync specific fields to HubSpot contact and company properties.

This approach works, but it requires:

• A data warehouse with product usage data already flowing in
• Engineering work to model the data (write SQL or dbt transformations to calculate metrics like "days since last login" or "features adopted")
• A reverse ETL tool subscription ($350-$800/mo)
• Ongoing maintenance when your product schema changes or HubSpot property mappings need updates

For teams with a data warehouse already in production and an analytics engineer on staff, reverse ETL makes sense. For RevOps teams at early-stage or mid-market PLG companies, it's overkill.

The Old Way: Reverse ETL Complexity

The reverse ETL stack looks like this:

1. Product events flow into your data warehouse (from Segment, RudderStack, or custom ETL)
2. You write SQL or dbt models to transform raw events into metrics (login count, feature adoption flags, engagement scores)
3. You configure a reverse ETL tool to map those warehouse columns to HubSpot properties
4. The sync runs on a schedule (hourly, daily) and writes data to HubSpot via the API

This setup gives you full control over transformations and works well if you're already maintaining a warehouse for other use cases. But it introduces multiple failure points (warehouse pipeline breaks, transformation logic needs updates, reverse ETL sync hits HubSpot API rate limits) and requires engineering resources to maintain.

If you're comparing reverse ETL options, see how to get product usage data into HubSpot for a full breakdown of methods.

The Zoody Approach: Real-Time Product Sync for HubSpot

Zoody connects directly to your product database and syncs usage data to HubSpot in real time, without a data warehouse or reverse ETL pipeline. You define which product events and properties matter (logins, feature usage, milestones), map them to HubSpot contact and company properties, and Zoody keeps them updated automatically.

How it works:

1. Connect your product database - Zoody reads from your Postgres, MySQL, or MongoDB database (read-only connection, no data leaves your infrastructure except the fields you choose to sync).
2. Define usage metrics - Set up tracking for events like "user logged in", "integration connected", "report generated", or custom milestones specific to your product.
3. Map to HubSpot properties - Zoody writes product signals to contact and company custom properties in HubSpot (you control the property names and types).
4. Automatic sync - Changes sync in real time as users engage with your product. No batch jobs, no hourly delays.

This setup takes under an hour, requires zero engineering work, and costs $149/mo (flat rate, unlimited contacts). You don't need a data warehouse, you don't write SQL transformations, and you don't manage a reverse ETL sync schedule.

Zoody only works with HubSpot (it's a native HubSpot integration), and it doesn't replace your product analytics tool. You still need Mixpanel, Amplitude, or PostHog to run cohort analysis and track funnels. Zoody is the bridge that gets the behavioral signals your RevOps team needs into HubSpot where they can trigger workflows and update contact records.

Use Cases: What You Can Do with Product-Enriched HubSpot Data

Once product usage data lives in HubSpot, you can build workflows and segments that weren't possible with firmographic enrichment alone.

Identifying Product-Qualified Leads (PQLs)

A product-qualified lead (PQL) is a contact who has demonstrated buying intent through their product behavior. Traditional lead scoring uses firmographic signals (company size, industry, job title), but PQL scoring combines those with usage signals.

With product data in HubSpot, you can score contacts by:

• Number of logins in the last 7 days
• Features activated (did they complete onboarding steps?)
• Depth of engagement (how many core workflows have they set up?)
• Team growth (did they invite teammates?)

A simple PQL score in HubSpot looks like this:

• +10 points for each login in the last week
• +20 points for activating your core feature
• +30 points for inviting a teammate
• +50 points for hitting a usage threshold (e.g., creating 10+ reports)

When a contact crosses your PQL threshold (say, 100 points), a HubSpot workflow triggers a sales notification, moves the contact to a high-priority list, or auto-assigns them to a sales rep.

This scoring model is impossible with firmographic data alone. A VP at a 500-person company who signed up last month but never logged in scores zero. A solo founder at a 3-person startup who logged in daily, activated three features, and invited two teammates scores 130 and gets routed to sales immediately.

Predicting and Preventing Churn

Churn signals live in product usage data, not firmographics. A paying customer who hasn't logged in for 14 days is at risk, regardless of their company size or contract value.

With product data in HubSpot, you can build retention workflows that trigger based on behavioral red flags:

• Engagement drop-off - Contact property "days_since_last_login" exceeds 14 days, trigger a customer success email or task.
• Feature abandonment - Contact used a feature 5 times in their first week, then stopped. Trigger a help article or onboarding checklist.
• Downgrade signals - Contact is on a paid plan but usage dropped below the free tier threshold. Trigger a retention offer before they downgrade.

These workflows run automatically in HubSpot, using the same workflow builder you already use for marketing and sales automation. No separate retention tool, no manual list building.

Spotting Expansion Opportunities

Product data shows which accounts are ready to expand to a higher tier or add seats. Common expansion signals:

• Usage limits - Contact hit 80% of their plan limit on key metrics (API calls, seats, storage). Trigger an upsell campaign or sales notification.
• Power user behavior - Contact using advanced features only available on higher tiers. Trigger a demo of premium features or a pricing comparison.
• Team growth - Contact invited 5+ teammates. Trigger a conversation about team plans or volume pricing.

With product usage data in HubSpot, you can build lists of expansion-ready accounts and route them to account executives automatically. Your sales team focuses on accounts showing buying intent, not random check-ins.

Building Smarter Lead Scores

Traditional lead scoring in HubSpot uses firmographic and engagement data:

• Company size: +10 points for 50-200 employees
• Job title: +15 points for Director or VP
• Email opens: +5 points
• Demo request: +30 points

Product-enriched lead scoring adds behavioral signals:

• Completed onboarding: +25 points
• Logged in 3+ times this week: +20 points
• Activated core feature: +40 points
• Invited a teammate: +35 points

This combined score (firmographic + behavioral) gives you a more accurate picture of buying intent. A contact with a fancy title who never uses the product scores lower than a junior employee who logs in daily and adopts features.

For a deeper dive into building product-based lead scores, see enriching HubSpot with product usage data.

Setting Up Product Usage Enrichment in HubSpot

Getting product data into HubSpot requires three steps: connect your product database, define which usage metrics to track, and map those metrics to HubSpot properties.

Connecting Your Product Data to HubSpot with Zoody

Zoody connects to your product database with a read-only connection. You provide credentials for Postgres, MySQL, or MongoDB, and Zoody queries the database for user activity.

Setup process:

1. In Zoody, create a new data source and select your database type (Postgres, MySQL, MongoDB).
2. Provide connection credentials (host, port, database name, read-only user).
3. Zoody tests the connection and confirms it can read from your user and events tables.
4. Define which tables and columns contain user identifiers (email, user ID) and event data.

This connection is read-only. Zoody never writes to your database, never deletes data, and only reads the fields you specify. The connection runs over SSL and doesn't require opening your database to the public internet (you can use SSH tunneling or VPC peering if needed).

Once connected, Zoody reads product usage in real time and syncs updates to HubSpot automatically.

Choosing the Right Product Signals to Track

Not every product event belongs in HubSpot. Your product analytics tool tracks hundreds of events for funnel analysis and cohort studies. HubSpot needs a focused set of signals that inform go-to-market decisions.

Focus on metrics tied to conversion, retention, and expansion:

• Activation milestones - Did the user complete onboarding, connect an integration, or set up their first workflow?
• Engagement frequency - Logins per week, days since last login, session count.
• Feature adoption - Which core features has the user activated? Which premium features are they using?
• Usage depth - Number of reports created, API calls made, records processed (whatever indicates real usage in your product).
• Team signals - Number of teammates invited, seats used, multi-user collaboration activity.

Start with 5-10 key metrics. You can always add more later, but starting lean keeps your HubSpot property list manageable and your workflows focused.

For each metric, decide whether it belongs on the contact record (individual user behavior) or the company record (account-level usage). Logins and feature adoption typically go on contacts. Total seats, account-level usage limits, and team growth go on companies.

Activating Product Data in HubSpot Workflows

Once product usage data flows into HubSpot properties, you can use it in workflows, lists, and reports just like any other contact or company field.

Common workflow triggers based on product data:

• PQL identification - When contact property "pql_score" is greater than 100, create a task for sales and send an email offering a demo.
• Churn prevention - When contact property "days_since_last_login" exceeds 14, enroll in a re-engagement email sequence and notify customer success.
• Expansion upsell - When company property "seats_used" exceeds 80% of "seats_purchased", send pricing information for the next tier and create a task for account executive.
• Feature adoption nudge - When contact property "integrations_connected" equals 0 and "signup_date" is more than 7 days ago, send a help article about connecting integrations.

These workflows run automatically in HubSpot's native workflow builder. No Zapier, no custom code, no external automation tool.

You can also build lists based on product data for ad targeting, email campaigns, or reporting. Example lists:

• Contacts who logged in 5+ times in the last 7 days (active users)
• Companies with usage above 80% of plan limits (expansion targets)
• Contacts who completed onboarding but haven't logged in for 30 days (reactivation campaign)

Product-enriched HubSpot data turns your CRM into a real-time view of user behavior, not just a contact database.

FAQ

What data does HubSpot native enrichment provide?

HubSpot's native enrichment adds firmographic and company data to contact and company records automatically. It pulls information like company size, industry, revenue range, headquarters location, social media profiles, and technologies used from third-party datasets. This enrichment happens in the background when you create a new contact with a valid business email domain. It does not include product usage data, behavioral signals, or engagement metrics from your application.

Can HubSpot enrich contacts with product usage data automatically?

No. HubSpot's native enrichment only covers firmographic and company information. To add product usage data (logins, feature adoption, engagement metrics) to HubSpot contact and company records, you need to sync that data from your product database or analytics tool. This requires either a reverse ETL pipeline from a data warehouse, a direct product sync tool like Zoody, or a custom API integration that writes product events to HubSpot properties.

What is the difference between data enrichment and reverse ETL?

Data enrichment pulls external third-party data (company size, industry, social profiles) from commercial datasets and writes it to your CRM. Reverse ETL pulls internal data from your data warehouse and syncs it to SaaS tools like HubSpot. Enrichment adds context from outside sources. Reverse ETL moves your own product, usage, or operational data from your warehouse into the tools your go-to-market team uses. Both write data to HubSpot, but they pull from different sources.

How do you identify product-qualified leads (PQLs) in HubSpot?

Create custom contact properties in HubSpot for key product usage metrics (logins, features adopted, milestones reached). Sync product data from your database or analytics tool to populate those properties. Build a lead scoring model that combines firmographic data (company size, role) with behavioral signals (login frequency, feature activation). When a contact crosses your PQL score threshold, trigger a workflow that notifies sales, assigns the contact to a rep, or moves them into a high-priority nurture sequence.

Do I need a data warehouse to sync product data to HubSpot?

Not necessarily. The traditional approach uses a data warehouse (Snowflake, BigQuery) and a reverse ETL tool (Hightouch, Census) to sync product data to HubSpot. This gives you full control over transformations but requires engineering resources and warehouse infrastructure. Alternatives include direct product sync tools like Zoody (connects your product database to HubSpot without a warehouse), custom API integrations (requires development work), or product analytics tools with native HubSpot connectors. The right approach depends on your existing stack and whether you already maintain a data warehouse.

{
 "meta_description": "HubSpot's native enrichment covers firmographics, but product usage data unlocks PLG success. Add behavioral signals to HubSpot in real time, no code required.",
 "word_count": 2100,
 "tag": "Guide",
 "faq_schema": {
 "@context": "https://schema.org",
 "@type": "FAQPage",
 "mainEntity": [
 {
 "@type": "Question",
 "name": "What data does HubSpot native enrichment provide?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "HubSpot's native enrichment adds firmographic and company data to contact and company records automatically. It pulls information like company size, industry, revenue range, headquarters location, social media profiles, and technologies used from third-party datasets. This enrichment happens in the background when you create a new contact with a valid business email domain. It does not include product usage data, behavioral signals, or engagement metrics from your application."
 }
 },
 {
 "@type": "Question",
 "name": "Can HubSpot enrich contacts with product usage data automatically?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "No. HubSpot's native enrichment only covers firmographic and company information. To add product usage data (logins, feature adoption, engagement metrics) to HubSpot contact and company records, you need to sync that data from your product database or analytics tool. This requires either a reverse ETL pipeline from a data warehouse, a direct product sync tool like Zoody, or a custom API integration that writes product events to HubSpot properties."
 }
 },
 {
 "@type": "Question",
 "name": "What is the difference between data enrichment and reverse ETL?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "Data enrichment pulls external third-party data (company size, industry, social profiles) from commercial datasets and writes it to your CRM. Reverse ETL pulls internal data from your data warehouse and syncs it to SaaS tools like HubSpot. Enrichment adds context from outside sources. Reverse ETL moves your own product, usage, or operational data from your warehouse into the tools your go-to-market team uses. Both write data to HubSpot, but they pull from different sources."
 }
 },
 {
 "@type": "Question",
 "