Home
Connectors
Stripe - Omnisend

Send events from your Stripe-billed app to Omnisend

Q: Which customer parameters are sent to Omnisend?

When Upstack identifies a visitor, it enriches the event with the contact’s email and any other known properties, and can create or update the contact in Omnisend.

Q: How do I check that Stripe events are reaching Omnisend?

Upstack marks the destination Healthy, and Audience or Reports in Omnisend shows contacts and events from Upstack Data, typically within a few minutes of a test purchase or page view.

Q: How long does it take to connect Stripe to Omnisend?

Most brands are live in under 20 minutes. Once Stripe events reach Upstack, every destination receives the same resolved events, Omnisend included.

Each event is resolved to a person against a 750M+ device graph before it reaches Omnisend, so flows trigger on a known profile rather than an anonymous session.

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 Omnisend. 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 order produces one event, so a single purchase cannot trigger the same flow twice.
Bot and fraud filteringAutomated traffic never becomes a profile, so list quality and deliverability are not paying for it.

Messaging mistakes are expensive and public. These controls exist so a flow never fires against a profile that should not have received it.

03 Activate

Delivered to Omnisend

Resolved events and profiles into Omnisend for email and SMS automation.

See the Omnisend integration

OmnisendWhat it receives

email / phonecontact key
event propertiesworkflow triggers
cart / order valuerevenue attribution

The catch

Stripe sees the payment, not the browse.

A customer who abandoned twice before paying looks like a first-time buyer with no history, so flows built on Stripe data alone have nothing to personalize against.

Where to check in OmnisendSending you can audit

Omnisend Audience the contact's activity

and the automation's own trigger log.

What changes

What changes when Stripe feeds Omnisend. Two gains on the Omnisend side, two on the Stripe side.

Omnisend

Server-side delivery

Upstack sends events to Omnisend from its servers only, so ad blockers and browser privacy settings can’t block delivery.

Omnisend

Identity-resolved events

Events sent to Omnisend 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.

You need admin access to your Omnisend account, with permission to create API keys.

Upstack dashboardExample

Omnisend Destination Healthy

Read the full Omnisend 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 Omnisend destination

Under Destinations, add Omnisend with an API key created under Store settings, API in Omnisend: typically a 64 character secret followed by a hyphen and a short identifier. It is the only field the destination needs.
03

Check contacts and events in Omnisend

Upstack marks the destination Healthy, and Audience or Reports in Omnisend shows contacts and events from Upstack Data, typically within a few minutes of a test purchase or page view.

FAQ

Questions about Stripe and Omnisend.

Which customer parameters are sent to Omnisend?

When Upstack identifies a visitor, it enriches the event with the contact’s email and any other known properties, and can create or update the contact in Omnisend.

How do I check that Stripe events are reaching Omnisend?

Upstack marks the destination Healthy, and Audience or Reports in Omnisend shows contacts and events from Upstack Data, typically within a few minutes of a test purchase or page view.