- 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 Loop Subscriptions event reaches HubSpot. Captured on the server, resolved to a person, then sent.
01 Capture
Captured from Loop Subscriptions
Capture Loop Subscriptions events server-side (new subscriptions, renewals, swaps and cancellations), each as what it actually is.
See the Loop Subscriptions integration →
Loop SubscriptionsWhat it sends subscription_idthe Loop subscription across its whole lifeemail / phonesubscriber contactevent_typerenewal, swap, skip, pause, cancel or saveline_itemsproducts after any swaptotal / intervalcharge amount and billing cadence
02 Understand
Resolved to one person before it leaves
Every Loop Subscriptions 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.
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 keylifecycle propertiesstage and pipelinedeal / order valuerevenue on the record
The catch
Cancel-flow outcomes are the most valuable CRM field in a subscription business and the least likely to be synced, so churn reasons live only in Loop.
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 Loop Subscriptions feeds HubSpot. Two gains on the HubSpot side, two on the Loop Subscriptions 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.
Loop Subscriptions
Every event, server-side
Storefront and checkout events are captured from Loop Subscriptions on the server, independent of the browser.
Loop Subscriptions
One setup, every destination
Connect Loop Subscriptions once and forward to every ad platform, email tool and warehouse you run.
Setup
Live in under 20 minutes.
Connect Loop Subscriptions once and every destination, HubSpot included, is forwarded the same resolved events.
Upstack dashboardExample
Loop Subscriptions Data source Connected
HubSpot Destination Healthy
Read the full HubSpot setup guide → -
01
Connect Loop Subscriptions
Capture Loop Subscriptions events server-side (new subscriptions, renewals, swaps and cancellations), each as what it actually is.
-
02
Add the HubSpot destination
Under Destinations, add HubSpot. Every resolved Loop Subscriptions event is then forwarded to it.
-
03
Check delivery to HubSpot
Trace any property back to the event that set it.
FAQ
Questions about Loop Subscriptions and HubSpot.
How do I check that Loop Subscriptions events are reaching HubSpot?
Open HubSpot › the contact timeline, and the duplicate-management view, which should stop growing.
Will this create duplicate contacts?
No. One person, one record, across devices and identifiers.
How long does it take to connect Loop Subscriptions to HubSpot?
Most brands are live in under 20 minutes. Once Loop Subscriptions is connected, every destination receives the same resolved events, HubSpot included.