Custom stack to Omnisend
Forward every Custom stack event to Omnisend server-side, resolved to a person against a 750M+ device graph — so flows trigger on a known profile rather than an anonymous session.
Connection
Connect Custom stack to Omnisend with Upstack Data
Custom stack
Not on the list? Send events to Upstack from any stack over webhook or direct post, with the same schema and the same resolution.
Custom stack integration
Omnisend
Resolved events and profiles into Omnisend for email and SMS automation.
Omnisend integrationWhat changes
What changes when Custom stack feeds Omnisend.
Server-side delivery
Events reach Omnisend through its server API, not the browser — so ad blockers, ITP and consent banners don’t cost you conversions.
Identity-resolved events
Every event sent to Omnisend carries a resolved customer, matched against a 750M+ device graph.
Any stack, any framework
Headless, custom checkout, native app or a platform we haven’t listed — if it can make an HTTP request, it can send to Upstack.
The same event schema
Custom events are resolved, filtered and forwarded exactly like a Shopify order.
What actually moves
What Custom stack carries, and what Omnisend needs.
Custom stack and Omnisend describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what Custom stack can put on an event, the right is what Omnisend can actually use.
Custom stack sends
- event_name
- whatever you choose to call it
- user identifiers
- any of email, phone, external ID
- value / currency
- if the event carries revenue
- custom properties
- any attribute in your own schema
Omnisend receives
- email / phone
- contact key
- event properties
- workflow triggers
- cart / order value
- revenue attribution
Sending you can audit
How you know it is working.
Messaging mistakes are expensive and public. These controls exist so a flow never fires against a profile that should not have received it.
Per-profile inspection
Trace any event to the profile it resolved to, and see why.Deduplication
One order produces one event, so a single purchase cannot trigger the same flow twice.Bot and fraud filtering
Automated traffic never becomes a profile, so list quality and deliverability are not paying for it.
Where to check in Omnisend
OmnisendAudiencethe contact's activity, and the automation's own trigger log.
Related connectors
Other places Custom stack can send to.
- Custom stackMeta Conversions API
- Custom stackGoogle Ads Conversions
- Custom stackTikTok Events API
- Custom stackPinterest
- Custom stackSnapchat
- Custom stackReddit
- Custom stackMicrosoft Ads
- Custom stackX
Other sources that feed Omnisend.
- ShopifyOmnisend
- WooCommerceOmnisend
- BigCommerceOmnisend
- Checkout ChampOmnisend
- RechargeOmnisend
- FunnelishOmnisend
- Lasso CommerceOmnisend
- Phoenix TechnologiesOmnisend
- SkioOmnisend
- Loop SubscriptionsOmnisend
- StripeOmnisend
- Everything Omnisend can take12 sources feed Omnisend, and the setup is the same for each one.Omnisend integration
- How resolution worksEvery event matched against a 750M+ device graph before it is forwarded.Upstack Signal
- What it costsThree plans that scale with your order volume. Every connector is on every plan.See pricing
Get Custom stack talking to Omnisend.
A 15-minute walkthrough of this connector on your own account.