Home
Connectors
Lasso Commerce - Omnisend

Send every Lasso Commerce 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 Lasso Commerce 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 Lasso Commerce to Omnisend?

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

01 Capture

Captured from Lasso Commerce

Capture Lasso Commerce checkouts and upsells server-side, so orders that never touch a storefront page are still resolved and forwarded.

See the Lasso Commerce integration

Lasso CommerceWhat it sends

order_idLasso checkout order reference
email / phonecontact captured at checkout
line_itemsproducts and quantities on the order
total / discountorder economics after adjustments
landing_domainthe site the shopper started on, before the checkout hop

02 Understand

Resolved to one person before it leaves

Every Lasso Commerce 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

The cross-domain hop drops the session, so a shopper who browsed on your site and bought on the checkout domain arrives at your email tool as a stranger with no browse history.

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

Lasso Commerce

Every event, server-side

Storefront and checkout events are captured from Lasso Commerce on the server, independent of the browser.

Lasso Commerce

One setup, every destination

Connect Lasso Commerce once and forward to every ad platform, email tool and warehouse you run.

Setup

Live in under 20 minutes.

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

Upstack dashboardExample

Lasso Commerce Data source Connected

Omnisend Destination Healthy

Read the full Omnisend setup guide

01

Connect Lasso Commerce

Capture Lasso Commerce checkouts and upsells server-side, so orders that never touch a storefront page are still resolved and forwarded.
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 Lasso Commerce 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 Lasso Commerce 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.