- 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 Gorgias. 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 Gorgias
Give support the resolved customer: every order and touchpoint attached to one profile.
See the Gorgias integration →
GorgiasWhat it receives email / phonematch the ticket to a customerorder historygive the agent contextexternal_idone profile, not three
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 GorgiasDelivery you can audit
Gorgias › open any ticket
The customer sidebar should show the full order history rather than a single order.
What changes
What changes when Lasso Commerce feeds Gorgias. Two gains on the Gorgias side, two on the Lasso Commerce side.
Gorgias
Server-side delivery
Events reach Gorgias through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.
Gorgias
Identity-resolved events
Events sent to Gorgias 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, Gorgias included, is forwarded the same resolved events.
Upstack dashboardExample
Lasso Commerce Data source Connected
Gorgias Destination Healthy
Read the full Gorgias 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 Gorgias destination
Under Destinations, add Gorgias. Every resolved Lasso Commerce event is then forwarded to it.
-
03
Check delivery to Gorgias
Trace any request back to the order and customer it came from.
FAQ
Questions about Lasso Commerce and Gorgias.
How do I check that Lasso Commerce events are reaching Gorgias?
Open Gorgias › open any ticket. The customer sidebar should show the full order history rather than a single order.
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 Gorgias?
Most brands are live in under 20 minutes. Once Lasso Commerce is connected, every destination receives the same resolved events, Gorgias included.