Home
Connectors
Recharge - ActiveCampaign

ActiveCampaign

Send every Recharge event to ActiveCampaign, server-side

Q: How do I check that Recharge 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.

Q: How long does it take to connect Recharge to ActiveCampaign?

Most brands are live in under 20 minutes. Once Recharge is connected, every destination receives the same resolved events, ActiveCampaign included.

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

01 Capture

Captured from Recharge

Bring subscription events into the same resolved customer: new subscriptions, renewals, churn and reactivation.

See the Recharge integration

RechargeWhat it sends

subscription_idthe subscription, not the order
charge_ideach recurring charge
email / phonesubscriber contact
statusactive, cancelled, paused, reactivated
is_first_chargenew subscription versus renewal
product / frequencywhat they subscribed to and how often

02 Understand

Resolved to one person before it leaves

Every Recharge 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

Subscription state is not a property of an order.

It changes between them. A CRM fed only order events shows a customer as active long after they canceled.

Where to check in ActiveCampaignRecords you can audit

ActiveCampaign the contact record and the automation's contact log

What changes

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

Recharge

Subscriptions as their own conversion

Send new subscriptions to the ad platforms as a distinct event, not lumped in with one-time orders.

Recharge

Renewals counted properly

Recurring charges are forwarded as real revenue, so LTV reporting reflects what the customer is actually worth.

Setup

Live in under 20 minutes.

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

Upstack dashboardExample

Recharge Data source Connected

ActiveCampaign Destination Healthy

Read the full ActiveCampaign setup guide

01

Connect Recharge

Bring subscription events into the same resolved customer: new subscriptions, renewals, churn and reactivation.
02

Add the ActiveCampaign destination

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

Check delivery to ActiveCampaign

Trace any property back to the event that set it.