Home
Connectors
Skio - HubSpot

Skio

HubSpot

Send every Skio event to HubSpot, server-side

Q: How do I check that Skio 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 Skio to HubSpot?

Most brands are live in under 20 minutes. Once Skio 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 Skio event reaches HubSpot. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from Skio

Capture Skio subscription events server-side, with the first charge distinguished from every renewal that follows it.

See the Skio integration

SkioWhat it sends

subscription_idthe Skio subscription, stable across charges
email / phonesubscriber contact
charge_typefirst charge, renewal, swap or skip
line_itemsproducts on this charge
total / intervalcharge amount and billing cadence

02 Understand

Resolved to one person before it leaves

Every Skio 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 subscription ID and the order ID are different keys.

A CRM built on order ID sees a new relationship every billing cycle rather than one continuing subscription.

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

Skio

Every event, server-side

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

Skio

One setup, every destination

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

Setup

Live in under 20 minutes.

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

Upstack dashboardExample

Skio Data source Connected

HubSpot Destination Healthy

Read the full HubSpot setup guide

01

Connect Skio

Capture Skio subscription events server-side, with the first charge distinguished from every renewal that follows it.
02

Add the HubSpot destination

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

Check delivery to HubSpot

Trace any property back to the event that set it.