Home
Connectors
Stripe - HubSpot

Stripe

HubSpot

Send events from your Stripe-billed app to HubSpot

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

Most brands are live in under 20 minutes. Once Stripe events reach Upstack, 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 Stripe event reaches HubSpot. Sent from your app, resolved to a person, then forwarded.

01 Capture

Captured from Stripe

For apps that bill through Stripe, send payment and subscription events to Upstack with the Upstack Pixel and JavaScript SDK, resolved to a customer before they reach the tools you spend on.

See the Stripe integration

StripeWhat it sends

subscription_initial_purchaseyou fire it for the first subscription order
subscription_recurring_purchaseon invoice.paid for an existing subscription
payment_succeededmaps to invoice.paid or charge.succeeded
payment_refundedmaps to charge.refunded
amount / currencyamount in cents, with invoiceId and subscriptionId

02 Understand

Resolved to one person before it leaves

Every Stripe 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

A Stripe charge has no session, campaign or referrer attached: it is the money and nothing else.

Loading it into a CRM without resolution produces accurate revenue with no attribution, which is the failure mode that looks fine until someone asks which channel paid for it.

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

Stripe

Subscription purchases as events

Fire subscription_initial_purchase for the first order and subscription_recurring_purchase each time a renewal is paid, so first orders and renewals are reported separately.

Stripe

Payments and refunds

payment_succeeded, payment_failed and payment_refunded each map to a Stripe event (invoice.paid or charge.succeeded, invoice.payment_failed, charge.refunded), so money events reach Upstack when your app fires them.

Setup

Live in under 20 minutes.

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

Upstack dashboardExample

HubSpot Destination Healthy

Read the full HubSpot setup guide

01

Install the Upstack Pixel and SDK

Add the Upstack Pixel to your app, then fire the subscription and payment events with the JavaScript SDK when Stripe reports them, such as subscription_recurring_purchase when invoice.paid fires for an existing subscription.
02

Add the HubSpot destination

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

Check delivery to HubSpot

Trace any property back to the event that set it.