Skip to main content
  1. Home
  2. Integrations
  3. Lasso Commerce
Upstack Data

Lasso Commerce integration: every order captured server-side and resolved to a person

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

Role
Source
Category
E-commerce
Pre-built connectors
34 destinations
Plans
All plans

What Upstack captures

Every Lasso Commerce event leaves resolved to a person. Captured on the server, resolved to a person, then sent.

In: from Lasso CommerceWhat it carries
  • 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

Every funnel checkout, server-side.

Upstack DataResolved 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.
  • DeduplicationBrowser and server copies of the same purchase collapse on event ID, so nothing is counted twice.
  • Bot and fraud filteringAutomated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.
Out: to Meta Conversions API1 of 34 destinations
  • em, ph (SHA-256)raise Event Match Quality
  • fbclid / _fbpcredit the click that drove it
  • external_idstable person across sessions
  • event_iddedupe against the browser pixel
  • value / currencyvalue-based bidding

Conversions API with higher Event Match Quality.

About Lasso Commerce

Upstack reads the order from the server, so the cross-domain hop stops mattering: there is no cookie to survive it.

The click ID is recovered from the graph and the buyer resolved against it, so the order is attributed to the campaign that produced it rather than to direct traffic.

What Lasso Commerce is

Lasso Commerce runs checkout and funnel infrastructure for direct-response and subscription brands.

Checkouts that live outside a storefront are exactly where browser tracking fails.

How Lasso Commerce works

Lasso hosts the checkout itself, often on its own domain, separate from the brand site a shopper started on. That cross-domain hop is where cookies are dropped, click IDs lost and sessions split in two, which is why funnel checkouts routinely under-report.

What you can do with it

Three jobs Lasso Commerce does once it is connected.

01

Capture every order server-side

Lasso Commerce events are captured from the server rather than the shopper’s browser, so ad blockers and ITP stop deciding which of your conversions get counted. Nothing depends on a script surviving the page.

02

Resolve each event to a person

Every Lasso Commerce event is matched against a 750M+ device graph before it leaves, so a phone browse and a desktop checkout resolve to one customer rather than two strangers. Returning buyers are recognized as returning.

03

The cross-domain hop stops mattering

Orders are read server-side, so attribution does not depend on a cookie surviving the move from your site to the checkout domain.

Pre-built connectors

Lasso Commerce forwards to 34 destinations. Connect Lasso Commerce once. Every destination is already wired.

See all 34 Lasso Commerce connectors

Documentation

Set-up reference.

Set-up, event schema and field mapping for Lasso Commerce as a source.

FAQ

Lasso Commerce integration questions.

What does Upstack capture from Lasso Commerce?

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

Which plans include the Lasso Commerce integration?

All plans. Upstack has three plans that scale with your order volume, and the same integrations are on every plan.

Which destinations can Lasso Commerce send to?

34 destinations, including Meta Conversions API, Google Ads Conversions, TikTok Events API, Pinterest, Snapchat and Reddit. Each one has its own pre-built connector.

Will Upstack slow down my store?

Upstack’s own pixel loads asynchronously and fails silently, so it doesn’t hold up your pages. What each destination adds depends on its Tracking Method. The default, Browser + Server, loads that platform’s own tag on your store, in place of the copy you would otherwise install yourself, and also sends the same events from Upstack’s servers. Choose Server for any destination that offers it and its tag never loads, while its events still arrive from Upstack’s servers.

Similar integrations

Other sources to connect.

See all integrations

Get Lasso Commerce tracking right.

A 15-minute walkthrough tailored to your stack and channels.