Customer events
Connect Stripe events
Use a one-time native webhook URL to turn billing events into canonical customer signals.
Set up the webhook
- 01
Create a Stripe connection
AttuneMail shows the native webhook URL once. Store it with the same care as an API credential.
- 02
Add a webhook destination
In Stripe, create a webhook endpoint and paste the URL without adding headers or changing the payload.
- 03
Choose lifecycle events
Subscribe to the billing events your journeys or goals use, such as checkout completion, subscription updates, or payment outcomes.
- 04
Send a test event
Use Stripe's test mode first, then confirm the event, customer identity, canonical name, and properties in AttuneMail.
Canonical mapping
Stripe event types are recorded as stripe.{event.type}. The Stripe event id provides idempotency. Customer ID and customer or email fields from data.object are used to resolve identity.
| Stripe input | AttuneMail value |
|---|---|
| event.type | stripe.{event.type} |
| event.id | message ID / deduplication key |
| data.object.customer | Customer external ID when present |
| data.object.customer_email or email | Email trait when present |
Operational safety
- ✓Use separate Stripe test and live connections
- ✓Rotate the AttuneMail connection if its URL appears in logs, tickets, or source control
- ✓Retain rejected events for diagnosis, but note that unresolved events never start a journey
- ✓Do not infer marketing consent from a payment event