[CLOSED] Smart CRM AMA: Build a Data Foundation Your Team Can Rely On

Hi HubSpot Admins and RevOps folks,

I know it. You know it. Everyone knows it: you’re managing CRM data your team can’t trust and your AI can’t use. This isn’t a passing problem, it’s an existential one. The whole point of a CRM is to store — and act on — your customer data. When the data isn’t accurate, sales outreach is ill-timed and misinformed, marketing gets low engagement and MQLs dip, and service teams can’t properly help customers. Leadership can’t trust reports, and you spend more time trying to fix things and less time improving them. A shaky data foundation hurts the whole business.

At HubSpot, we want you to spend more time focused on meaningful work, which is why Maggie Philbin, a HubSpot product manager, and I will be here to host an Ask Me Anything about a topic that’s more important than ever: how to unify your CRM data and build a foundation your team can rely on.

During this AMA, you can ask us anything about unifying your data in HubSpot Smart CRM: pipeline rules, data modeling best practices, making AI reliable, and more. We’ll be answering your questions from May 25th to May 29th, 2026.

Need some suggestions for what to ask? Here are some example questions:

  • What’s the best way to organize my App Objects?
  • How can I use event data to reliably track attribution?
  • What can I do to make Breeze Assistant a trusted coworker?
  • What Smart CRM tools help me improve governance and SOPs?

Drop your questions below, and we’ll reply directly in this thread during the AMA week. Looking forward to hearing from you!

Je me sens très bien au milieu de cette communauté hubspot, c’est une merveilleuse famille

For SaaS companies, What is HubSpot’s recommended object for product subscription information? Historically, I’ve often used a custom object. Should that move to the contracts object, stay a custom object, or a third option?

For most standard SaaS commercial agreements, Contracts is the new default recommendation. If you need complex entitlement, usage-based, or nonstandard relationship modeling, a Custom Object is still the right architecture. Right now, Contract creation and editing is done via accepted quotes, and thus required a commerce seat. But, product team is targeting a change later in the year that will make direct creation / editing via the UI and API without a Commerce Seat possible. But for now, consider this answer to be the most thorough. Make sure to check the Product Updates section of your portal for the beta coming soon.

Path 1: Use HubSpot’s Contracts Object:
The Contracts object (beta) is the right choice when the commercial agreement has a fixed start and end, contract value matters, and renewal is a defined lifecycle event.

Path 2: Custom Object (may still the right call for complex setups) and/or Custom Events (appropriate for lightweight logging of subscription changes)
Custom Objects are still a great choice when HubSpot’s native options don’t fit. For example: multi-party agreements (like MSP > reseller > end customer), per-seat license keys, usage-based products with complex tiers, or data HubSpot doesn’t currently model (though this has expanded a lot over the past few months) will be better suited to custom objects. You can also use custom events to send subscription updates directly through your product to provide what is effectively an audit log of changes
Path 3: Subscriptions Object (billing-centric data models on HubSpot Payments or Stripe)
If you use HubSpot Payments or Stripe and primarily need to track recurring charges and payment status, the Subscriptions object is also an option. As a billing object, it tracks recurring charges, payment status, and the customer-facing side of billing.

One challenge I often see is historical records bypassed stages, which impacts conversion calculations. Does HubSpot have a recommended approach, or future direction around inferring missing lifecycle stages and backfilling timestamps to improve reporting accuracy?

Thanks for the question, @Patrick_Saab ! We’re aware that this is a pain point and are considering enhancements for the long-term roadmap.

In the meantime, our current recommended approach is to use Lifecycle Stage workflow automations to enforce stage transitions sequentially, rather than allowing direct jumps. You can try:

  • Set Lifecycle Stage via workflows (not manually or via integrations that jump stages) - Use the “only move forward” workflow logic to prevent backward movement.
  • Avoid letting users, integrations ,or imports set Lifecycle Stage directly without passing through intermediate stages
  • For historical data specifically, we recommended using bulk enrollment into workflows or data imports to retroactively set timestamps.

This post walks you through an example.

What plan of attack do you recommend for someone who had just joined an organization that does not currently, and has not in the past, practiced good data hygiene in Hubspot? I’m talkin customers who have been customers for years still being as ‘Opportunity’ or ‘Lead’ in the Lifecycle Stage, no Renewal Dates populated anywhere (relying on Deal Expiry Date as a backstop for now), no ACV populated for any customers, etc.

Where do I even begin as a new CSM just trying to make sense of our subscription and renewal data?

hi christina!! this is something a lot of teams struggle with! my thoughts:

  • don’t wait for perfect data--data health is an ongoing process, so i’d anchor on what data in your crm is more reliable for you today. if not lifecycle stage, are close date, deal owner, last activity/source data in a better state? what can you use to build a reliable view so you’re not entirely blocked by what’s messier?
    • as a csm, you own your book of business. as you work your accounts, update lifecycle stage to customer, populate renewal date, and log acv as you go. you of course won’t fix the whole crm this way, but you’ll have clean data for the records that matter most to you and that will compound over time
  • all hubs at starter have access to the data agent, which can help fill in missing properties automatically. you can ask it to enrich records by pulling data from the web, emails, and calls to populate fields
  • what can you automate:
    • for things like acv and renewal data, where does that live for your teams? is it in a billing system or your product? is it possible to have that system update properties automatically? HubSpot has thousands of integrations that may work with your other apps.
    • for lifecycle stage, a workflow which sets closed/won deal’s associated contacts to lifecycle stage of customer will stop the problem from continuing to get worse
  • the data quality command center is a great home base for general data quality help, though not as applicable with customer data inaccuracies in specific.
    • the data quality overview page surfaces duplicate issues, formatting problems, and property insights across your crm, this is important because it flags issues proactively.
    • the weekly data quality digest is worth setting up too, so you’re not discovering problems months later.

it won’t get fixed overnight, but asking these questions and getting a plan together is a great first step!!

In free tier (developer id), how do I integrate hubspot CRM on something new development as on a web application?

Hi @seosiri , can you please elaborate on your question so we can answer this more specifically?

Hi jjurenek, thanks for following up!

I am looking to integrate HubSpot CRM into a custom web application (built with React/Node.js). Specifically, I want to use my HubSpot Developer Account to:

  1. Sync Lead Data: When a user signs up on my web app, I want to automatically create or update a “Contact” in the HubSpot CRM.
  2. Authentication: Since I am on the free/developer tier, should I be using a Private App Access Token for a single portal, or is an OAuth flow required for this type of integration?
  3. Tracking: I’d also like to know if the standard HubSpot Tracking Code works effectively for tracking user behavior inside a Single Page Application (SPA), or if I should use the Identified Visitors API.

Any guidance on the best API endpoints or documentation to start with for these specific use cases would be greatly appreciated!

Hi Happy to help!. For the use cases you described, here’s the path we recommend. (Note: the best way to get further help is in our Developers Forum as this AMA will close today.)
TLDR answer;

  • For a single portal, you can generally do this with a free HubSpot developer account using a private app token, with OAuth only needed for a multi-account/distributed integration.
  • SPA analytics: tracking code with setPath + trackPageView
  • Logged-in user attribution: add identify
  • Chat widget behind login: Visitor Identification API

Detailed answer:
For syncing lead data from your React/Node app into HubSpot, the best starting point is the Contacts API. You can create a contact with POST /crm/v3/objects/contacts, update a contact with PATCH /crm/v3/objects/contacts/{contactId} or PATCH /crm/v3/objects/contacts/{email}?idProperty=email, and if you want create/update behavior in one operation for batches, you can use POST /crm/v3/objects/contacts/batch/upsert with email or another unique identifier as the idProperty. One nuance: partial upserts are not supported when using email as the identifier, so if you need partial upsert behavior, a custom unique ID property is the better option.
On authentication: if this integration is only for a single HubSpot portal that you control, a private app access token is the simplest option. HubSpot’s docs say private apps are for accessing data in your HubSpot account, private apps can only be installed into the account where they’re uploaded, and if you only need an access token for a few APIs, a legacy private app may be the right choice. OAuth is the right choice when you need a distributed integration that other HubSpot accounts can install/connect themselves. HubSpot’s usage guidance is explicit that apps installed in a single account can use a static auth token, while publicly distributed apps should use OAuth.
For tracking in a single-page application, the standard HubSpot tracking code can work well, but you need to handle route changes manually. HubSpot’s tracking code docs say the code automatically records the initial page view, and for SPAs you should call setPath and then trackPageView on subsequent client-side route changes. If you know the user’s email after login, you can also use the tracking code’s identify method so HubSpot ties the visitor’s hubspotutk cookie and analytics activity to the contact record; the identity is actually sent when followed by a trackPageView or trackEvent call.
We don’t recommend the Visitor Identification API as the default answer for SPA behavior tracking. That API is specifically for identifying authenticated users in the HubSpot chat widget / Conversations inbox, so the visitor shows as a known contact in chat rather than an unknown visitor. In other words: use the tracking code (plus identify where appropriate) for analytics/pageview behavior, and use the Visitor Identification API only if you’re embedding HubSpot chat in an authenticated part of the app.
Helpful docs:

thank you @MPhilbin

Hey @jjurenek,
Thanks so much for hosting this space; it holds a lot of value for all of our users!
I’d like to tag in some of our Community experts to see if there’s any specific questions, comments, or concerns they may have to add to the conversation. @TomM2, @Mike_Eastwood, and @Ben_M - tagging you all in to see if there’s anything you’d like to add or inquire about.
Shane, Senior Community Moderator