Funnelish to Omnisend
Forward every Funnelish 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 Funnelish to Omnisend with Upstack Data
Funnelish
Capture every Funnelish order and one-click upsell from the server, so funnel revenue is counted in full rather than at the first step.
Funnelish integration
Omnisend
Resolved events and profiles into Omnisend for email and SMS automation.
Omnisend integrationWhat changes
What changes when Funnelish 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.
Every event, server-side
Storefront and checkout events are captured from Funnelish on the server, independent of the browser.
One setup, every destination
Connect Funnelish once and forward to every ad platform, email tool and warehouse you run.
What actually moves
What Funnelish carries, and what Omnisend needs.
Funnelish and Omnisend describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what Funnelish can put on an event, the right is what Omnisend can actually use.
Funnelish sends
- order_id
- Funnelish order, including the upsell sequence
- email / phone
- contact from the order form
- line_items
- initial offer plus every accepted upsell
- total / upsell_total
- the full amount taken, not the first step
- funnel_id / step
- which funnel and which step converted
- customer_type
- new or returning, resolved before send
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 Funnelish can send to.
- FunnelishMeta Conversions API
- FunnelishGoogle Ads Conversions
- FunnelishTikTok Events API
- FunnelishPinterest
- FunnelishSnapchat
- FunnelishReddit
- FunnelishMicrosoft Ads
- FunnelishX
Other sources that feed Omnisend.
- ShopifyOmnisend
- WooCommerceOmnisend
- BigCommerceOmnisend
- Checkout ChampOmnisend
- RechargeOmnisend
- Custom stackOmnisend
- 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 Funnelish talking to Omnisend.
A 15-minute walkthrough of this connector on your own account.