- 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 Shopify event reaches Omnisend. Captured on the server, resolved to a person, then sent.
01 Capture
Captured from Shopify
One Upstack app setup that captures Shopify storefront and checkout events with the Upstack Pixel, records every order directly from Shopify, and forwards both to every tool you spend on.
See the Shopify integration →
ShopifyWhat it sends order_idShopify order and checkout tokenemail / phonecustomer contact from checkoutcustomer_idShopify customer record, if they have oneline_itemsproducts, variants and quantitiestotal / subtotal / discountorder economics
02 Understand
Resolved to one person before it leaves
Every Shopify 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.
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 keyevent propertiesworkflow triggerscart / order valuerevenue attribution
Shopify to Omnisend, in detail
How Shopify events reach Omnisend through Upstack.
Omnisend’s native Shopify 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 customer profiles and sends browse, cart, checkout and purchase events to Omnisend with the contact’s email attached, so abandoned cart and browse abandonment workflows fire for many more visitors.
| From Shopify and Upstack | In Omnisend |
| Product views, add to carts, checkouts and orders Trackable activities that can trigger workflows. | Activities on the contact |
| The email Upstack resolved Added when the visitor is identified, which is what lets a workflow trigger. | Contact email |
| Other known properties Upstack can create or update the contact so it can be segmented and messaged. | Contact properties |
Server-side only
Omnisend receives events from Upstack’s servers only, so there’s no extra browser tag to manage.
Overlap with the native integration
If Omnisend’s Shopify integration sends the same event types, Omnisend may record both. Disable those events there and keep the native integration for anything Upstack doesn’t route.
Identified visitors only
Upstack attaches the contact’s email only when it identifies the visitor. Events from visitors it can’t match carry no contact for a workflow to reach.
The catch
Shopify only knows a customer at checkout.
Everything before that (the browse, the add to cart, the return visit four days later) is anonymous unless something resolves it. That is the gap the flows fall into, not a problem with the flows.
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 Shopify feeds Omnisend. Two gains on the Omnisend side, two on the Shopify 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.
Shopify
Orders recorded from Shopify itself
Purchases also reach Upstack directly from Shopify, about 10 minutes after the order, so an order still counts when an ad blocker stopped the pixel or the shopper closed the page.
Shopify
Recognize returning customers
Shopify customer IDs, emails and phones are matched against the graph, so repeat buyers are identified across devices.
Setup
Live in under 20 minutes.
App install, no theme edits and no developer. You need admin access to your Omnisend account, with permission to create API keys and owner or staff access to Shopify.
Upstack dashboardExample
Shopify Data source Connected
Omnisend Destination Healthy
Read the full Omnisend setup guide → -
01
Connect Shopify
In the Upstack dashboard, open System, then Data Sources, and click Connect Shopify. Approve the install in your Shopify Admin: Upstack reads products, orders and customers, and writes only its own pixel.
-
02
Create an Omnisend API key
In Omnisend, open Store settings, API and create a key with permission to write events and contacts: typically a 64 character secret followed by a hyphen and a short identifier.
-
03
Add the Omnisend destination
Under Destinations, click New Destination, choose Omnisend, paste the API key and click Create Configuration. It’s the only field the destination needs.
-
04
Turn off the overlap
In Omnisend’s native Shopify integration, disable the event types Upstack now sends.
-
05
Check contacts and events
Add a product to cart on your store, then check the contact’s activity feed, or Audience and Reports, in Omnisend.
After setup
What to check in Omnisend.
Upstack shows the Omnisend destination as Healthy.
Audience or Reports in Omnisend shows contacts and events from Upstack Data within a few minutes of a test purchase or page view.
The test contact’s activity feed shows the add to cart you made.
Troubleshooting
Common problems and fixes.
-
Duplicate events in Omnisend
Both Upstack and Omnisend’s native integration send that event type. Disable it in the native integration.
-
Nothing arrives
Check the destination is Healthy and that the API key can write events and contacts. Upstack doesn’t need account management or billing permissions.
FAQ
Questions about Shopify and Omnisend.
How do I connect Shopify to Omnisend with Upstack?
Connect Shopify to Upstack, create an Omnisend API key under Store settings, API, and add it as the Omnisend destination. Then turn off the overlapping events in Omnisend’s native Shopify integration. Most brands are live in under 20 minutes.
How is this different from Omnisend’s native Shopify integration?
Omnisend’s 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 customer profiles and sends those events to Omnisend with the contact’s email attached, so abandoned cart and browse abandonment workflows fire for many more visitors.
Will I get duplicate events if I keep Omnisend’s native Shopify integration?
Possibly. Disable the corresponding events in Omnisend’s native integration for any event types Upstack sends, and keep the native integration only for events you are not routing through Upstack.
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 Shopify 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.
Do I need a developer to connect Shopify to Omnisend?
No. Shopify connects as an app install with no theme edits, and most brands are live in under 20 minutes. Headless storefronts add the Upstack Pixel script instead of the theme app extension.
What permissions does the Omnisend API key need?
Permission to write events and contacts. Use the minimum scope: Upstack doesn’t need account management or billing permissions.
Does Upstack create contacts in Omnisend?
It can. When it identifies a visitor, Upstack can create or update the contact in Omnisend, so it can be segmented and messaged.
Keep reading
More on Shopify and Omnisend.