- 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 ActiveCampaign. 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 person, one record, across devices and identifiers.
- Bot and fraud filteringAutomated traffic never becomes a contact.
03 Activate
Delivered to ActiveCampaign
Resolved events and contacts into ActiveCampaign for automation and segmentation.
See the ActiveCampaign integration →
ActiveCampaignWhat it receives emailcontact keycustom fieldsautomation branchingdeal valuepipeline reporting
The catch
The landing domain and the checkout domain produce two different session records for one customer.
A CRM loading both without resolution ends up with duplicate contacts that never merge.
Where to check in ActiveCampaignRecords you can audit
ActiveCampaign › the contact record and the automation's contact log
What changes
What changes when Lasso Commerce feeds ActiveCampaign. Two gains on the ActiveCampaign side, two on the Lasso Commerce side.
ActiveCampaign
Server-side delivery
Events reach ActiveCampaign through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.
ActiveCampaign
Identity-resolved events
Events sent to ActiveCampaign 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, ActiveCampaign included, is forwarded the same resolved events.
Upstack dashboardExample
Lasso Commerce Data source Connected
ActiveCampaign Destination Healthy
Read the full ActiveCampaign 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 ActiveCampaign destination
Under Destinations, add ActiveCampaign. Every resolved Lasso Commerce event is then forwarded to it.
-
03
Check delivery to ActiveCampaign
Trace any property back to the event that set it.
FAQ
Questions about Lasso Commerce and ActiveCampaign.
How do I check that Lasso Commerce events are reaching ActiveCampaign?
Open ActiveCampaign › the contact record and the automation's contact log.
Will this create duplicate contacts?
No. One person, one record, across devices and identifiers.
How long does it take to connect Lasso Commerce to ActiveCampaign?
Most brands are live in under 20 minutes. Once Lasso Commerce is connected, every destination receives the same resolved events, ActiveCampaign included.