Home
Connectors
Lasso Commerce - HubSpot

HubSpot

Send every Lasso Commerce event to HubSpot, server-side

Q: How do I check that Lasso Commerce events are reaching HubSpot?

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

Q: Will this create duplicate contacts?

No. One person, one record, across devices and identifiers.

Q: How long does it take to connect Lasso Commerce to HubSpot?

Most brands are live in under 20 minutes. Once Lasso Commerce is connected, every destination receives the same resolved events, HubSpot included.

Each event is resolved to a person against a 750M+ device graph before it reaches HubSpot, so records and reporting reflect the person, not the device.

Request a demo Start free trial

US device IDs in the graph: 750M+
Match rate on events: 90%+
Identity window, per customer: Lifetime
Most brands are live: <20 min

How it flows

How a Lasso Commerce event reaches HubSpot. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from Lasso Commerce

Capture Lasso Commerce checkouts and upsells server-side, so orders that never touch a storefront page are still resolved and forwarded.

See the Lasso Commerce integration

Lasso CommerceWhat it sends

order_idLasso checkout order reference
email / phonecontact captured at checkout
line_itemsproducts and quantities on the order
total / discountorder economics after adjustments
landing_domainthe site the shopper started on, before the checkout hop

02 Understand

Resolved to one person before it leaves

Every Lasso Commerce event is matched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer rather than two strangers.

How resolution works

Resolved 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.

A CRM is only as trustworthy as its worst duplicate. These controls exist so the record reflects the person.

03 Activate

Delivered to HubSpot

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

See the HubSpot integration

HubSpotWhat it receives

emailthe contact key
lifecycle propertiesstage and pipeline
deal / order valuerevenue on the record

The catch

The landing domain and the checkout domain produce two different session records for one customer.

A CRM loading both without resolution ends up with duplicate contacts that never merge.

Where to check in HubSpotRecords you can audit

HubSpot the contact timeline

and the duplicate-management view, which should stop growing.

What changes

What changes when Lasso Commerce feeds HubSpot. Two gains on the HubSpot side, two on the Lasso Commerce side.

HubSpot

Server-side delivery

Events reach HubSpot through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.

HubSpot

Identity-resolved events

Events sent to HubSpot carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.

Lasso Commerce

Every event, server-side

Storefront and checkout events are captured from Lasso Commerce on the server, independent of the browser.

Lasso Commerce

One setup, every destination

Connect Lasso Commerce once and forward to every ad platform, email tool and warehouse you run.

Setup

Live in under 20 minutes.

Connect Lasso Commerce once and every destination, HubSpot included, is forwarded the same resolved events.

Upstack dashboardExample

Lasso Commerce Data source Connected

HubSpot Destination Healthy

Read the full HubSpot setup guide

01

Connect Lasso Commerce

Capture Lasso Commerce checkouts and upsells server-side, so orders that never touch a storefront page are still resolved and forwarded.
02

Add the HubSpot destination

Under Destinations, add HubSpot. Every resolved Lasso Commerce event is then forwarded to it.
03

Check delivery to HubSpot

Trace any property back to the event that set it.