Home
Connectors
Recharge - Attentive

Send every Recharge event to Attentive, server-side

Q: How do I check that Recharge events are reaching Attentive?

Open Attentive › the subscriber's timeline, where the event appears against the profile rather than as an unattached activity.

Q: Can one purchase trigger the same flow twice?

No. One order produces one event, so a single purchase cannot trigger the same flow twice.

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

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

Each event is resolved to a person against a 750M+ device graph before it reaches Attentive, so flows trigger on a known profile rather than an anonymous session.

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 Attentive. 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 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.

Messaging mistakes are expensive and public. These controls exist so a flow never fires against a profile that should not have received 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 key
emailsecondary identifier for cross-channel
event propertieswhat the journey triggers on

The catch

Renewals and new subscriptions look identical coming out of Recharge unless you split them.

Send both into the same flow and long-standing subscribers receive welcome sequences every billing cycle.

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 Recharge feeds Attentive. Two gains on the Attentive side, two on the Recharge 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.

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, Attentive included, is forwarded the same resolved events.

Upstack dashboardExample

Recharge Data source Connected

Attentive Destination Healthy

Read the full Attentive setup guide

01

Connect Recharge

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

Add the Attentive destination

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

Check delivery to Attentive

Trace any event to the profile it resolved to, and see why.