Skip to main content
Request a demo
  1. Home
  2. Integrations
  3. HubSpot
Upstack Data

HubSpot integration: identity-resolved events and contacts

Push identity-resolved events and contacts into HubSpot so CRM records match what actually happened.

Request a demo Start free trial
Role
Destination
Category
Analytics & CRM
Pre-built connectors
12 sources
Plans
All plans

What Upstack sends

Every event reaches HubSpot attached to one person. Captured on the server, resolved to a person, then sent.

In: from Shopify1 of 12 sources
  • order_idShopify order and checkout token
  • email / phonecustomer contact from checkout
  • customer_idShopify customer record, if they have one
  • line_itemsproducts, variants and quantities
  • total / subtotal / discountorder economics

Storefront events from the Upstack Pixel, orders directly from Shopify.

Upstack DataResolved before it is sent
  • IdentityMatched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer.
  • customer_typeNew or returning, resolved before send.
  • DeduplicationOne person, one record, across devices and identifiers.
  • Bot and fraud filteringAutomated traffic never becomes a contact.
Out: to HubSpotOn every event
  • emailthe contact key
  • lifecycle propertiesstage and pipeline
  • deal / order valuerevenue on the record

CRM records that match what actually happened.

See the set-up reference See all 12 sources How resolution works

About HubSpot

HubSpot’s object graph is only as good as the keys written into it.

Upstack resolves identity before contacts and events are created, so one buyer stays one contact across devices, sessions and channels. Lifecycle stage, workflow enrollment and pipeline reporting all inherit that, and the duplicate-management queue stops growing.

What HubSpot is

HubSpot is a CRM and marketing platform used by brands with a considered sales motion, wholesale channels or a B2B side to the business.

CRM records are only as accurate as the events feeding them. Without resolved identity, one buyer becomes several contacts and the pipeline stops reflecting reality.

How HubSpot works

HubSpot models the world as contacts, companies, deals and tickets, tied together by associations. Contacts are keyed on email; events and properties written against a contact drive lifecycle stage, list membership, workflow enrollment and reporting. Custom behavioral events can be sent through the API and used in workflows and reports like any native property. The object graph is only as clean as the keys used to write into it: two emails for one human produce two contacts and two histories.

What you can do with it

Three jobs this connector does inside HubSpot.

01

Send complete conversions

Conversions reach HubSpot through its server-side API with restored click IDs and hashed identifiers attached, so more of what you send is matched on arrival, and the conversions you never saw stop being invisible.

02

Optimize on the customer you want

Map any order attribute to the conversion HubSpot receives (profit rather than revenue, new customers rather than repeat buyers, high-value orders rather than every checkout), so the platform learns from the buyers worth acquiring.

03

Records that match reality

Resolved events and contacts keep one buyer as one record, so pipeline and reporting stop inflating on duplicates.

Pre-built connectors

12 sources connect to HubSpot. Whichever of these you run, HubSpot is one switch away.

See all connectors

Documentation

Set-up reference.

Set-up, event schema and field mapping for HubSpot as a destination, next to the HubSpot developer docs.

FAQ

HubSpot integration questions.

What does Upstack send to HubSpot?

Push identity-resolved events and contacts into HubSpot so CRM records match what actually happened.

How do I check that events are reaching HubSpot?

Open HubSpot › the contact timeline, and the duplicate-management view, which should stop growing.

Which plans include the HubSpot integration?

All plans. Upstack has three plans that scale with your order volume, and the same integrations are on every plan.

Which sources can send events to HubSpot?

12 sources: Shopify, WooCommerce, BigCommerce, Checkout Champ, Recharge, Custom stack, Funnelish, Lasso Commerce, Phoenix Technologies, Skio, Loop Subscriptions and Stripe. Each one has its own pre-built connector.

Will Upstack slow down my store?

Upstack’s own pixel loads asynchronously and fails silently, so it doesn’t hold up your pages. What each destination adds depends on its Tracking Method. The default, Browser + Server, loads that platform’s own tag on your store, in place of the copy you would otherwise install yourself, and also sends the same events from Upstack’s servers. Choose Server for any destination that offers it and its tag never loads, while its events still arrive from Upstack’s servers.

Similar integrations

Other destinations to send to.

See all integrations

Get HubSpot tracking right.

A 15-minute walkthrough tailored to your stack and channels.

Request a demo Start free trial