- 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 Yotpo. 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 referenceemail / phonecontact captured at checkoutline_itemsproducts and quantities on the ordertotal / discountorder economics after adjustmentslanding_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 purchase, one request, even when the order is amended.
- Bot and fraud filteringFraudulent orders never enter the request queue.
03 Activate
Delivered to Yotpo
Enrich post-purchase touchpoints in Yotpo with identity-resolved order data.
See the Yotpo integration →
YotpoWhat it receives emailwho to ask for the revieworder_idwhich purchase the request is aboutproduct IDswhich product is being reviewed
The catch
A Lasso order carries checkout contact fields only.
Repeat buyers accumulate separate records unless the order is resolved against a graph first.
Where to check in YotpoDelivery you can audit
Yotpo › Reviews › the request queue
which should now contain the orders that previously had no email attached.
What changes
What changes when Lasso Commerce feeds Yotpo. Two gains on the Yotpo side, two on the Lasso Commerce side.
Yotpo
Server-side delivery
Events reach Yotpo through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.
Yotpo
Identity-resolved events
Events sent to Yotpo 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, Yotpo included, is forwarded the same resolved events.
Upstack dashboardExample
Lasso Commerce Data source Connected
Yotpo Destination Healthy
Read the full Yotpo 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 Yotpo destination
Under Destinations, add Yotpo. Every resolved Lasso Commerce event is then forwarded to it.
-
03
Check delivery to Yotpo
Trace any request back to the order and customer it came from.
FAQ
Questions about Lasso Commerce and Yotpo.
How do I check that Lasso Commerce events are reaching Yotpo?
Open Yotpo › Reviews › the request queue, which should now contain the orders that previously had no email attached.
Will a customer be asked twice about one order?
No. One purchase, one request, even when the order is amended.
How long does it take to connect Lasso Commerce to Yotpo?
Most brands are live in under 20 minutes. Once Lasso Commerce is connected, every destination receives the same resolved events, Yotpo included.