Home
Connectors
Stripe - Attentive

Send events from your Stripe-billed app to Attentive

Q: How do I check that Stripe 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 Stripe to Attentive?

Most brands are live in under 20 minutes. Once Stripe events reach Upstack, 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 Stripe event reaches Attentive. Sent from your app, resolved to a person, then forwarded.

01 Capture

Captured from Stripe

For apps that bill through Stripe, send payment and subscription events to Upstack with the Upstack Pixel and JavaScript SDK, resolved to a customer before they reach the tools you spend on.

See the Stripe integration

StripeWhat it sends

subscription_initial_purchaseyou fire it for the first subscription order
subscription_recurring_purchaseon invoice.paid for an existing subscription
payment_succeededmaps to invoice.paid or charge.succeeded
payment_refundedmaps to charge.refunded
amount / currencyamount in cents, with invoiceId and subscriptionId

02 Understand

Resolved to one person before it leaves

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

Stripe sees the payment, not the browse.

A customer who abandoned twice before paying looks like a first-time buyer with no history, so flows built on Stripe data alone have nothing to personalize against.

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

Stripe

Subscription purchases as events

Fire subscription_initial_purchase for the first order and subscription_recurring_purchase each time a renewal is paid, so first orders and renewals are reported separately.

Stripe

Payments and refunds

payment_succeeded, payment_failed and payment_refunded each map to a Stripe event (invoice.paid or charge.succeeded, invoice.payment_failed, charge.refunded), so money events reach Upstack when your app fires them.

Setup

Live in under 20 minutes.

Connect Stripe once and every destination, Attentive included, is forwarded the same resolved events.

Upstack dashboardExample

Attentive Destination Healthy

Read the full Attentive setup guide

01

Install the Upstack Pixel and SDK

Add the Upstack Pixel to your app, then fire the subscription and payment events with the JavaScript SDK when Stripe reports them, such as subscription_recurring_purchase when invoice.paid fires for an existing subscription.
02

Add the Attentive destination

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

Check delivery to Attentive

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