The best product analytics in the world has no commercial value if it stays inside the analytics platform. Sales reps work in the CRM. They open a contact record, they want to see whether that user has activated, how often they log in, and whether they have hit any paywall. If that data is not in the CRM, it does not exist for sales — and the PQL motion does not work. This article covers which product data is GTM-relevant, how to get it into your CRM, and what use cases it enables.
The gap between product analytics and commercial action
Most PLG companies have two separate data realities. The product team lives in Mixpanel or Amplitude, looking at funnels, retention curves, and feature adoption. The sales team lives in HubSpot, looking at contact records, deal stages, and activity timelines. Between these two systems sits a gap that costs revenue every day.
A user who reaches the paywall at 9 AM on a Tuesday represents a qualified buying signal. If that signal never reaches a sales rep's CRM view, no one acts on it. By Wednesday, the user's intent has cooled, they may have found a workaround, or they may have started evaluating a competitor. The window was there; it was invisible to the people who could have acted on it.
The solution is not to give sales access to Mixpanel. Most sales reps will not adopt a separate analytics tool, and even if they did, they would not know which users to prioritize. The solution is to bring the right product data into the CRM, in a format that is immediately interpretable by someone who is not a data analyst.
Which product data is GTM-relevant?
Not all product data belongs in the CRM. A sales rep does not need every page view, every button click, or every API call. They need a small set of high-signal properties that answer two questions: is this user ready for a sales conversation, and what context is relevant for that conversation?
Activation events
The most important single data point: has this user completed the activation sequence? Activation is the moment when a user experiences the core value of the product for the first time. In HubSpot, this would be something like "first deal created" or "first workflow activated." In Notion, it might be "first database created." In a project management tool, it might be "first task assigned to a team member."
The CRM properties to create:
- activation_completed (boolean): Has the user reached the activation milestone?
- activation_date (date): When did activation happen?
- days_to_activation (number): How many days from signup to activation?
Usage frequency
Activation tells you that a user got started. Frequency tells you whether they are sticking. A user who activated three months ago and has not been seen since is a very different commercial conversation than a user who activated last week and logs in daily.
Key frequency properties:
- sessions_last_7_days and sessions_last_30_days
- last_active_date: The most recent date of any meaningful product activity
- days_since_last_active: Derived from last_active_date — useful for churn risk scoring
Feature usage signals
Feature usage tells you what the user has discovered and what they have not. High-value features — collaboration features, advanced configuration, enterprise-adjacent capabilities — are leading indicators of commercial intent.
Key feature properties:
- collaboration_features_used (boolean or count): Has the user used team or sharing features?
- enterprise_features_accessed (boolean): Has the user tried to access SSO, admin settings, or other enterprise-gated features?
- paywall_hit_date: The first time the user hit a paywall or usage limit
- paywall_hit_count: How many times total they have encountered a paywall
Account-level data
Individual user data answers "is this person ready?" Account-level data answers "is this company ready?" Both are needed for PQL scoring.
Key account properties (on the Company object in HubSpot):
- active_users_count: Total active users from this domain in the past 30 days
- activated_users_count: How many users from this domain have completed activation
- team_invitations_sent: How many invitations have been sent from users in this account
- account_pql_score: Computed score combining user-level and account-level signals
Integration routes: how to get product data into HubSpot
There are three main routes for getting product data into HubSpot, each with different trade-offs on technical complexity, reliability, and real-time latency.
Route 1: Segment as the event bus
If you are already using Segment for event tracking, adding HubSpot as a destination is the cleanest approach. In Segment's dashboard, you add the HubSpot destination and configure property mappings: which Segment event properties should update which HubSpot contact properties.
For example: when Segment fires an "Activation Completed" event with a timestamp property, you configure the destination to update the HubSpot contact's activation_date property with that timestamp. When Segment fires a "Paywall Hit" event, it updates paywall_hit_date and increments paywall_hit_count.
The advantage of this route: you implement the tracking once in Segment, and all downstream systems — HubSpot, Mixpanel, Amplitude, your data warehouse — receive the same events. No duplicate tracking code, no separate integration maintenance.
Route 2: Direct Contacts API
For teams that prefer more control or do not use Segment, HubSpot's Contacts API allows direct property updates from your backend. A nightly or real-time job queries your product database, computes the relevant properties (sessions_last_30_days, days_since_last_active), and calls the HubSpot API to update the corresponding contact records.
This is the most flexible route — you can compute any derived property your backend can calculate — but it requires more backend development and ongoing maintenance. Use this route when you need computed properties that go beyond simple event forwarding.
Route 3: Native integrations via Amplitude or Mixpanel
Both Amplitude and Mixpanel offer native HubSpot integrations that can sync user cohorts and properties. Amplitude's HubSpot integration, for example, allows you to define a cohort of "activated users who used collaboration features in the past 14 days" in Amplitude and sync that cohort to a HubSpot list. You can then trigger HubSpot workflows based on cohort membership.
This route is accessible to teams without significant backend engineering resources, but it has limitations: the sync is typically not real-time (batch updates every few hours), and the property granularity is lower than a direct API integration. For PQL scoring based on time-sensitive signals like paywall hits, the latency may be too high.
GTM use cases that product data enables
PQL identification and routing
The primary use case: identify free users who have reached a combination of activation, usage frequency, and firmographic fit that makes them strong candidates for a paid conversion conversation. A HubSpot workflow scores contacts based on their product properties, and when a score threshold is crossed, it creates a deal in the sales pipeline, assigns it to the appropriate rep, and sends a notification with the full product context.
Engagement-based nurturing
Users who have signed up but not activated represent a segment that is neither ready for a sales conversation nor satisfied enough to convert on their own. Product data lets you segment this group precisely — by signup date, days since signup, and activation status — and trigger specific onboarding email sequences designed to get them to the activation moment. Generic drip sequences treat everyone the same; product-data-driven sequences are responsive to where each user actually is in the product.
Churn prediction and proactive CS
For paying customers, the same product data that identifies PQLs also identifies churn risk. A customer whose usage drops from 20 sessions per month to 3 sessions over 30 days is showing early churn signals. Product data in the CRM allows your customer success team to see those signals in their regular workflow — no separate analytics tool required — and trigger proactive outreach before the customer submits a cancellation request.
Expansion identification
Existing customers who expand their product usage, add new team members, or start accessing higher-tier features are showing expansion signals. Product data in the CRM lets your CS or expansion team spot these signals systematically rather than relying on customers to raise their hand when they are ready to upgrade.
For the specific HubSpot implementation — the custom properties, the workflow configurations, and the reporting setup — the article on product data in HubSpot covers the step-by-step technical detail.