Skip to main content
  1. Home
  2. Connectors
  3. Lasso Commerce - StackAdapt

Send every Lasso Commerce event to StackAdapt, server-side

Each event is resolved to a person against a 750M+ device graph before it reaches StackAdapt, with restored click IDs, deduplicated conversions and delivery you can audit.

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 StackAdapt. 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
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.

Ad platforms accept almost anything and tell you very little. These controls exist so you can see what was sent and what was accepted, rather than inferring it from a reporting gap.

03 Activate

Delivered to StackAdapt

Server-side conversions to StackAdapt with hashed identifiers attached, so multi-channel programmatic is measured on your orders.

See the StackAdapt integration
StackAdaptWhat it receives
  • hashed email / phoneidentity matching on arrival
  • sa_click_idcredit the click that drove it
  • external_idstable person across sessions
  • event_iddedupe against the browser pixel
  • value / currencyvalue-based bidding

The catch

The checkout sits on its own domain, so the browser pixel that fired on your site is not the pixel that sees the purchase.

Sending the conversion server-side with the click ID recovered is what stops the order being attributed to direct traffic.

Where to check in StackAdaptDelivery you can audit

StackAdapt Conversions Conversion tracking

Server-side conversions are labeled by source, so a deduplicated pair is visible as one.

What changes

What changes when Lasso Commerce feeds StackAdapt. Two gains on the StackAdapt side, two on the Lasso Commerce side.

StackAdapt

Server-side delivery

Events reach StackAdapt through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.

StackAdapt

Identity-resolved events

Events sent to StackAdapt 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.

Connect Lasso Commerce once and every destination, StackAdapt included, is forwarded the same resolved events.

Upstack dashboardExample
Lasso Commerce Data source Connected
StackAdapt Destination Healthy
Read the full StackAdapt setup guide
  1. 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.

  2. 02

    Add the StackAdapt destination

    Under Destinations, add StackAdapt. Every resolved Lasso Commerce event is then forwarded to it.

  3. 03

    Check delivery to StackAdapt

    Every conversion is inspectable from the moment it fires to the moment the platform confirms it.

FAQ

Questions about Lasso Commerce and StackAdapt.

How do I check that Lasso Commerce events are reaching StackAdapt?

Open StackAdapt › Conversions › Conversion tracking. Server-side conversions are labeled by source, so a deduplicated pair is visible as one.

Will a purchase be counted twice?

No. Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.

How long does it take to connect Lasso Commerce to StackAdapt?

Most brands are live in under 20 minutes. Once Lasso Commerce is connected, every destination receives the same resolved events, StackAdapt included.

Related connectors

See all 408 connectors

Get Lasso Commerce talking to StackAdapt.

A 15-minute walkthrough of this connector on your own account.

21-day free trial, no card. Month to month.