Home
Connectors
Recharge - Omnisend

Send every Recharge event to Omnisend, server-side

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 Recharge 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 Recharge to Omnisend?

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

01 Capture

Captured from Recharge

Bring subscription events into the same resolved customer: new subscriptions, renewals, churn and reactivation.

See the Recharge integration

RechargeWhat it sends

subscription_idthe subscription, not the order
charge_ideach recurring charge
email / phonesubscriber contact
statusactive, cancelled, paused, reactivated
is_first_chargenew subscription versus renewal
product / frequencywhat they subscribed to and how often

02 Understand

Resolved to one person before it leaves

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

Renewals and new subscriptions look identical coming out of Recharge unless you split them.

Send both into the same flow and long-standing subscribers receive welcome sequences every billing cycle.

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

Recharge

Subscriptions as their own conversion

Send new subscriptions to the ad platforms as a distinct event, not lumped in with one-time orders.

Recharge

Renewals counted properly

Recurring charges are forwarded as real revenue, so LTV reporting reflects what the customer is actually worth.

Setup

Live in under 20 minutes.

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

Upstack dashboardExample

Recharge Data source Connected

Omnisend Destination Healthy

Read the full Omnisend setup guide

01

Connect Recharge

Bring subscription events into the same resolved customer: new subscriptions, renewals, churn and reactivation.
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 Recharge 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 Recharge 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.