CRM

HubSpot integration for digital marketing agencies

HubSpot is the CRM most digital marketing agencies' B2B clients run on, and tracking HubSpot configurations across an agency's book of clients is its own operational discipline. Some clients pay agencies specifically to manage their HubSpot — the agency tracks workflows, lifecycle stages, lead-scoring rules, and deal pipelines on the client's behalf. Phloz records HubSpot as a typed CRM-system node — no connection, no sync — so agencies running HubSpot management as a service have a structured place to document what's configured per client.

How Phloz models HubSpot

What Phloz records about HubSpot on each client's tracking map, and what it doesn't. Only GA4, Google Tag Manager and Google Ads connect to Phloz (read-only, through a connected Google account); everything else is recorded by your team. Health states are set by the person who checks, the structural audit re-runs weekly, and graph relationships show what each node connects to — so a node marked broken or overdue for verification shows up in the cross-client tracking-health view.

  • HubSpot portal as a CRM system node with its name, instance URL, and notes (hubs and plan level go in the notes)
  • Edges from the website, landing pages, or GTM container that load the HubSpot tracking code, and to the ad platforms it syncs leads to
  • Workflows and lifecycle stages stay in HubSpot — record what matters in the node's notes
  • Account owner (agency or client) and last-verified date on the node, so offboarding risk is visible

Common HubSpot configuration gotchas

The configuration mistakes agencies most often make with HubSpot, surfaced here as a checklist agencies can run at every client onboarding. Honest, useful, not gated behind a sales pitch — these are real and you should audit for them regardless of whether you use Phloz.

  • Tracking code installation: HubSpot's tracking script must be on every page including the checkout flow. Agencies install on the marketing site only and miss product-page + checkout activity.
  • Form submissions vs API events: HubSpot forms send tracking events natively, but custom JavaScript forms need explicit `_hsq` calls. Verify both event sources for clients with custom form components.
  • Lifecycle stage automation conflicts: two workflows that move contacts to different lifecycle stages on the same trigger event cause race conditions. Audit lifecycle-stage transition rules quarterly.

At launch (V1)

A client's HubSpot portal is a CRM system node (vendor: HubSpot) with its name, URL, and notes, so agencies managing client HubSpot instances can record what's configured where. There is no HubSpot connection.

Not built yet

HubSpot API sync: contact count, automation count, tracking-code install verification.

Why we built the integration this way

Most agency CRMs treat third-party tools as text fields: "GA4 Property ID" goes in a custom column on the client record. That works at one or two clients and breaks at five. With HubSpot recorded on each client's tracking map — as its own typed node where Phloz has one, as fields and notes where it doesn't — the agency can answer "is this client's HubSpot setup documented, and when was it last verified?" per client, and see every client ranked by tracking health.

Most of it is entered by hand at onboarding: only GA4 properties, GTM containers and Google Ads accounts can be imported from a connected Google account, and nothing syncs afterwards. The manual pass forces explicit verification at the exact moment the agency takes over the client's tracking — the cheapest moment to catch the gotchas listed above, before they become production issues.

When to use this in your client onboarding flow

The pattern we recommend: at every new client onboarding (see the client onboarding audit use case), spend 30 minutes documenting the client's HubSpot configuration on the tracking map — IDs, tracking-code installations, conversion setup, the relationships to other systems. Verify each one fires by triggering a test event, then mark the node verified so the date is recorded. Add a recurring task (monthly, say) for the re-check, assigned to whoever owns tracking — the audit flags anything unverified for 30+ days either way.

Thirty minutes at onboarding costs far less than finding the same tracking issues during the first month of campaign optimisation — when finding them would mean a refund conversation. See the broader tracking infrastructure map use case for the agency-wide pattern.

Frequently asked questions

The three questions agencies ask most often about Phloz's HubSpot integration. Honest answers — same data we'd give a friend evaluating the integration.

Can Phloz replace HubSpot for our agency's own use?
For many digital marketing agencies it can: Phloz keeps clients, projects, retainers and each client's tracking setup in one place. For agencies that primarily sell HubSpot implementation services, keeping HubSpot makes more sense. See /alternatives-to/hubspot for the full switch decision.
How does Phloz integrate with HubSpot for agencies that manage client HubSpot accounts?
It doesn't connect to HubSpot. Phloz models the client's HubSpot account as a CRM system node — agencies document what's configured (workflows, pipelines, tracking code install) on it. It's NOT a sync — Phloz doesn't pull HubSpot contacts into Phloz CRM. The two are separate systems doing separate jobs.
What about HubSpot Solutions Partner program tracking?
Phloz doesn't track it. The CRM system node has no partner fields, and with no HubSpot connection there is nothing to verify partner status against — keep partner-program details in HubSpot's partner portal.

Other integrations

Other crm and adjacent tools, and how Phloz handles each.

Start your free trial

14 days free for new workspaces · No credit card · Starter tier free forever