- 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 Attentive. 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 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.
03 Activate
Delivered to Attentive
Feed resolved customer profiles into Attentive so SMS journeys trigger on people, not sessions.
See the Attentive integration →
AttentiveWhat it receives phonethe subscriber keyemailsecondary identifier for cross-channelevent propertieswhat the journey triggers on
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 AttentiveSending you can audit
Attentive › the subscriber's timeline
where the event appears against the profile rather than as an unattached activity.
What changes
What changes when Lasso Commerce feeds Attentive. Two gains on the Attentive side, two on the Lasso Commerce side.
Attentive
Server-side delivery
Events reach Attentive through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.
Attentive
Identity-resolved events
Events sent to Attentive 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, Attentive included, is forwarded the same resolved events.
Upstack dashboardExample
Lasso Commerce Data source Connected
Attentive Destination Healthy
Read the full Attentive 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 Attentive destination
Under Destinations, add Attentive. Every resolved Lasso Commerce event is then forwarded to it.
-
03
Check delivery to Attentive
Trace any event to the profile it resolved to, and see why.
FAQ
Questions about Lasso Commerce and Attentive.
How do I check that Lasso Commerce events are reaching Attentive?
Open Attentive › the subscriber's timeline, where the event appears against the profile rather than as an unattached activity.
Can one purchase trigger the same flow twice?
No. One order produces one event, so a single purchase cannot trigger the same flow twice.
How long does it take to connect Lasso Commerce to Attentive?
Most brands are live in under 20 minutes. Once Lasso Commerce is connected, every destination receives the same resolved events, Attentive included.