Home
Connectors
Custom stack - HubSpot

Send every Custom stack event to HubSpot, server-side

Q: How do I check that Custom stack 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.

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 Custom stack event reaches HubSpot. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from Custom stack

Not on the list? Send events to Upstack from any stack over webhook or direct post, with the same schema and the same resolution.

See the Custom stack integration

Custom stackWhat it sends

event_namewhatever you choose to call it
user identifiersany of email, phone, external ID
value / currencyif the event carries revenue
custom propertiesany attribute in your own schema

02 Understand

Resolved to one person before it leaves

Every Custom stack 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

Without a canonical person ID, a custom event stream produces a contact per identifier rather than a contact per person.

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 Custom stack feeds HubSpot. Two gains on the HubSpot side, two on the Custom stack 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.

Custom stack

Any stack, any framework

Headless, custom checkout, native app or a platform we haven’t listed: if it can make an HTTP request, it can send to Upstack.

Custom stack

The same event schema

Custom events are resolved, filtered and forwarded exactly like a Shopify order.

Setup

Post directly from your backend so nothing depends on the browser.

Connect Custom stack once and every destination, HubSpot included, is forwarded the same resolved events.

Upstack dashboardExample

Custom stack Data source Connected

HubSpot Destination Healthy

Read the full HubSpot setup guide

01

Connect Custom stack

Not on the list? Send events to Upstack from any stack over webhook or direct post, with the same schema and the same resolution.
02

Add the HubSpot destination

Under Destinations, add HubSpot. Every resolved Custom stack event is then forwarded to it.
03

Check delivery to HubSpot

Trace any property back to the event that set it.