HubSpot Platform and Product Knowledge
HubSpot Platform and Product Knowledge
This domain tests practical knowledge of HubSpot's hubs, objects, properties, automation, and reporting. You need to choose the right tool for a client's use case and know the edition limits that change the answer.
Hubs and objects
- Marketing Hub covers campaigns, forms, landing pages, email, ads, social, and marketing automation.
- Sales Hub covers deals, pipelines, sequences, playbooks, forecasting, quotes, and meetings.
- Service Hub covers tickets, help desk, SLAs, knowledge base, customer portal, and CSAT.
- Content Hub (formerly CMS Hub) covers websites, blogs, and CMS; Operations Hub covers data sync, data quality, and programmable automation; Commerce Hub covers quotes, invoices, and payments.
- Standard objects are contacts, companies, deals, tickets, products, line items, and quotes. Custom objects extend the CRM for things like projects or locations.
- Properties have types (text, number, date, enumeration, calculation) and must be created before use in workflows and reports.
Automation and data
Workflows automate actions based on enrollment criteria. Sequences are one-to-one sales follow-up, not marketing automation. Lists are dynamic or static groups of records. Use the right enrollment trigger and suppression logic to avoid duplicate sends. Lifecycle stage and lead status are separate properties: stage measures relationship, status measures sales action.
Reporting
Campaigns group assets. Attribution reports show which interactions created deals; multi-touch attribution requires Enterprise. Dashboards should answer a business question, not display every available metric.
Worked example
A client wants high-value demo requests routed to a senior rep within one hour. Reasoning: use a form with a company-size property, a workflow enrollment trigger on deal amount or company size, round-robin or specific-user assignment, an internal notification, a task with due date, and an SLA property. Test with a test contact and document the fallback owner.
Traps
- Assuming all features exist in every edition; workflows and attribution vary by tier.
- Using a sequence where a workflow is needed, or vice versa.
- Creating duplicate properties instead of reusing existing ones.
- Deleting properties or records without checking dependencies.
- Reporting on activity metrics without tying them to pipeline or revenue.