- 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 BigCommerce event reaches ActiveCampaign. Captured on the server, resolved to a person, then sent.
01 Capture
Captured from BigCommerce
Server-side capture of BigCommerce storefront and checkout events, resolved and forwarded downstream.
See the BigCommerce integration →
BigCommerceWhat it sends order_idBigCommerce orderemail / phonecheckout contactcustomer_idBigCommerce customer recordproductscatalog items on the ordertotal_inc_taxorder value
02 Understand
Resolved to one person before it leaves
Every BigCommerce 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
Multi-storefront BigCommerce accounts produce overlapping customer IDs across stores, which merge badly in a CRM unless resolved first.
Where to check in ActiveCampaignRecords you can audit
ActiveCampaign › the contact record and the automation's contact log
What changes
What changes when BigCommerce feeds ActiveCampaign. Two gains on the ActiveCampaign side, two on the BigCommerce 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.
BigCommerce
Every event, server-side
Storefront and checkout events are captured from BigCommerce on the server, independent of the browser.
BigCommerce
One setup, every destination
Connect BigCommerce once and forward to every ad platform, email tool and warehouse you run.
Setup
Live in under 20 minutes.
Connect BigCommerce once and every destination, ActiveCampaign included, is forwarded the same resolved events.
Upstack dashboardExample
BigCommerce Data source Connected
ActiveCampaign Destination Healthy
Read the full ActiveCampaign setup guide → -
01
Connect BigCommerce
Server-side capture of BigCommerce storefront and checkout events, resolved and forwarded downstream.
-
02
Add the ActiveCampaign destination
Under Destinations, add ActiveCampaign. Every resolved BigCommerce event is then forwarded to it.
-
03
Check delivery to ActiveCampaign
Trace any property back to the event that set it.
FAQ
Questions about BigCommerce and ActiveCampaign.
How do I check that BigCommerce 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 BigCommerce to ActiveCampaign?
Most brands are live in under 20 minutes. Once BigCommerce is connected, every destination receives the same resolved events, ActiveCampaign included.