Home
Connectors
Custom stack - ActiveCampaign

Send every Custom stack event to ActiveCampaign, server-side

Q: How do I check that Custom stack events are reaching ActiveCampaign?

Open ActiveCampaign › the contact record and the automation's contact log.

Q: Will this create duplicate contacts?

No. One person, one record, across devices and identifiers.

Each event is resolved to a person against a 750M+ device graph before it reaches ActiveCampaign, so records and reporting reflect the person, not the device.

Request a demo Start free trial

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 Custom stack event reaches ActiveCampaign. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from Custom stack

Not on the list? Send events to Upstack from any stack over webhook or direct post, with the same schema and the same resolution.

See the Custom stack integration

Custom stackWhat it sends

event_namewhatever you choose to call it
user identifiersany of email, phone, external ID
value / currencyif the event carries revenue
custom propertiesany attribute in your own schema

02 Understand

Resolved to one person before it leaves

Every Custom stack 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.

A CRM is only as trustworthy as its worst duplicate. These controls exist so the record reflects the person.

03 Activate

Delivered to ActiveCampaign

Resolved events and contacts into ActiveCampaign for automation and segmentation.

See the ActiveCampaign integration

ActiveCampaignWhat it receives

emailcontact key
custom fieldsautomation branching
deal valuepipeline reporting

The catch

Without a canonical person ID, a custom event stream produces a contact per identifier rather than a contact per person.

Where to check in ActiveCampaignRecords you can audit

ActiveCampaign the contact record and the automation's contact log

What changes

What changes when Custom stack feeds ActiveCampaign. Two gains on the ActiveCampaign side, two on the Custom stack 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.

Custom stack

Any stack, any framework

Headless, custom checkout, native app or a platform we haven’t listed: if it can make an HTTP request, it can send to Upstack.

Custom stack

The same event schema

Custom events are resolved, filtered and forwarded exactly like a Shopify order.

Setup

Post directly from your backend so nothing depends on the browser.

Connect Custom stack once and every destination, ActiveCampaign included, is forwarded the same resolved events.

Upstack dashboardExample

Custom stack Data source Connected

ActiveCampaign Destination Healthy

Read the full ActiveCampaign setup guide

01

Connect Custom stack

Not on the list? Send events to Upstack from any stack over webhook or direct post, with the same schema and the same resolution.
02

Add the ActiveCampaign destination

Under Destinations, add ActiveCampaign. Every resolved Custom stack event is then forwarded to it.
03

Check delivery to ActiveCampaign

Trace any property back to the event that set it.