How Stripe Contact Syncing Works in Audienceful
Once you've connected Stripe, your Stripe customers flow into Audienceful as contacts. Stripe syncing is one-way — Audienceful reads from Stripe and never creates or modifies customers in your Stripe account.
How customers become contacts
As Stripe events arrive, Audienceful upserts a contact for each customer, matched by email. A contact is created or updated on events like:
- Customer created
- Subscription changes — trial started, trial ending, activated, past due, paused, resumed, canceled
- Payments — succeeded or failed, and refunds
New contacts are tagged with a Stripe source. Audienceful pulls the customer's email, name, and location from Stripe. The subscription and payment events themselves drive your automations — for example, a payment failed event can start your dunning flow.
Payments become revenue
Every successful payment is recorded as a revenue event against the contact (refunds are netted out automatically). This is what powers conversion tracking on your automations and lets you segment contacts by total spend — so you can build audiences like "customers who've spent over $500."
One-way by design
Audienceful does not push contacts or changes back into Stripe. Stripe remains the source of truth for your billing data; Audienceful mirrors it for email.
What you can control
Customer syncing is a single toggle on the Stripe integration's settings, on by default:
- Sync customers — create/update contacts from Stripe events.
With it off, Stripe events still record revenue and can fire automations for existing contacts, but Audienceful won't create new contacts from Stripe.