Omnisend integration: server-side events resolved to a known profile

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

Request a demo Start free trial

Role: Destination
Category: Email & SMS
Pre-built connectors: 12 sources
Plans: All plans

What Upstack sends

Every event reaches Omnisend attached to a profile. Captured on the server, resolved to a person, then sent.

In: from Shopify1 of 12 sources

order_idShopify order and checkout token
email / phonecustomer contact from checkout
customer_idShopify customer record, if they have one
line_itemsproducts, variants and quantities
total / subtotal / discountorder economics

Storefront events from the Upstack Pixel, orders directly from Shopify.

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.

Out: to OmnisendOn every event

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

Resolved events for email and SMS automation.

See the set-up reference See all 12 sources How resolution works

About Omnisend

Omnisend’s workflows and segments are both built from event history, so gaps in that history compound.

Upstack sends browse, cart and order events server-side with a resolved contact attached, which raises both what can be triggered and who can be targeted, from the same fix.

What Omnisend is

Omnisend is an email and SMS platform for ecommerce brands, combining campaigns, automation and segmentation in one place.

Automation quality depends on event quality: the workflows are only as good as the browse, cart and order events that reach them.

How Omnisend works

Omnisend combines email, SMS and push in a single automation builder. Contacts are keyed on email or phone, and workflows trigger on ecommerce events (product viewed, cart abandoned, order placed), then branch on contact properties and event data. Segments are built from the same event history, so the quality of the event feed determines both what can be triggered and who can be targeted.

What you can do with it

Three jobs this connector does inside Omnisend.

Send complete conversions

Conversions reach Omnisend through its server-side API with restored click IDs and hashed identifiers attached, so more of what you send is matched on arrival, and the conversions you never saw stop being invisible.

Optimize on the customer you want

Map any order attribute to the conversion Omnisend receives (profit rather than revenue, new customers rather than repeat buyers, high-value orders rather than every checkout), so the platform learns from the buyers worth acquiring.

Workflows on complete events

Browse, cart and order events reach Omnisend independently of the browser, so the automations run on the full picture rather than what survived the page.

How it works

How the Omnisend integration works.

Upstack sends Omnisend server-side events for browse, cart, checkout and purchase activity, enriched with the contact’s email when the visitor is identified.

Four steps per event

The Upstack Pixel captures the event and matches it to a known profile. If the visitor is identified, Upstack adds their email and other known properties, sends the event to Omnisend as a trackable activity that can trigger workflows, and can create or update the contact.

Server-side only

Omnisend receives events from the server only, so there is no browser tag to manage and no Tracking Method to choose.

Identity

Anonymous sessions are matched to known profiles using cookies, click IDs and cross-session behavior. Clicks from Omnisend emails carry an Omnisend click ID that Upstack captures.

Signup forms become Lead events

Upstack detects Omnisend popups, signup boxes and wheels, fires a Lead event and ties the session to the identity the form captured.

Subscription renewals

Renewals arrive in Omnisend as Subscription Recurring Order - Upstackified, sent by default.

Timing

Upstack starts sending as soon as you save the destination. New events typically appear within a few minutes of a test purchase or page view.

Setup

Set up the Omnisend integration.

What you need

Admin access to your Omnisend account.
Permission to create API keys. The key is typically a 64-character secret, a hyphen and a short identifier.

Complete Omnisend onboarding guide

Step 1

Create the API key

In Omnisend, open Store settings, then the API tab, click Create API key, name it UpstackData and copy it. It is shown once, and anyone with it can read and write your Omnisend data.
Step 2

Add the Omnisend destination

In Upstack, open Destinations, click New Destination, choose Omnisend, paste the key into API Key (the only field) and save. The destination shows Healthy.
Step 3

Turn off overlapping native events

If Omnisend’s native Shopify integration sends the same event types, disable them there and keep it for events Upstack doesn’t send.

Check it

How to verify it’s working, and common fixes.

How to verify it’s working

Upstack’s Destinations page shows Omnisend as Healthy.
Omnisend’s Audience or Reports show contacts and events from Upstack Data within minutes of a test purchase or page view.
After a test add to cart, the contact’s activity feed in Omnisend shows the event.

Common problems and fixes

Duplicate events.: Omnisend’s native Shopify integration sends the same event types. Disable those there.
The destination is Unhealthy.: Generate a new API key in Omnisend and paste it into the destination.
The key is rejected.: Check that you copied the whole key with no extra spaces. Don’t include the key when you contact support.

Pre-built connectors

12 sources connect to Omnisend. Whichever of these you run, Omnisend is one switch away.

See all connectors

Documentation

Set-up reference.

Set-up, event schema and field mapping for Omnisend as a destination, next to the Omnisend developer docs.

FAQ

Omnisend integration questions.

What does Upstack send to Omnisend?

Browse, cart, checkout and purchase events, sent server-side as trackable activities that can trigger workflows. When Upstack has identified the visitor, each event carries the contact’s email and other known properties.

How is this different from Omnisend’s native Shopify integration?

The native integration only sees visitors Shopify has identified, typically logged-in customers or shoppers who entered an email at checkout. Upstack matches anonymous sessions to known profiles and sends their events with the email attached, so abandoned cart and browse workflows fire for more visitors.

Will I get duplicate events if I keep the native integration?

Possibly. Disable the event types Upstack sends in the native integration, and keep it only for events you don’t route through Upstack.

What permissions does the Omnisend API key need?

Permission to write events and contacts. Upstack doesn’t need account management or billing permissions.

How quickly do events appear in Omnisend?

Upstack starts sending when you save the destination. New events typically appear within a few minutes of a test purchase or page view.

Does Upstack set up Omnisend workflows for me?

The mirrored abandonment-flow setup the Upstack team configures is built for Klaviyo. In Omnisend, Upstack’s events are activities your own workflows can trigger on.