Customer Data Platform
Segment-compatible source: identify, track, group
Send identify, track, page, screen and group messages in Segment's spec to one source URL, singly or in batches of up to 500.
POST /v1/sources/:key takes one message, or { "batch": [ … ] } of up to 500, in Segment's spec. Create the source key on the Acquisition page. Segment, RudderStack, Make, or a server of your own can send to it.
type | What happens |
|---|---|
identify | the contact is created or updated (e-mail or phone; first and last name from firstName and lastName or a split name). Every other scalar trait is kept as a custom field |
track | a behavioural event (event, properties, messageId as the dedupe id, timestamp) |
page, screen | an event (page_viewed, screen_viewed); they create no contact |
group | a company object from groupId and traits, with the identified person related to it |
alias | accepted and ignored |
The person is read from email or phone at the top, in traits, in context.traits, or from userId when it is an e-mail address. A plain userId is not an identity here. A message without type is a track when it has an event, otherwise an identify.
One bad message does not stop a batch: each gets its own result, and a rejected one is dead-lettered. Custom fields from identify become snake_case, scalars only, at most 100 keys, strings cut at 1,000 characters.
A Stripe account as a source
Create a source with { "name": "…", "kind": "stripe", "signing_secret": "whsec_…" } and point a Stripe webhook endpoint at /v1/sources/<key>. Events are verified with Stripe-Signature over the raw body, and the secret is stored sealed and never returned.
| Stripe event | Becomes |
|---|---|
checkout.session.completed (paid) | purchase with revenue and currency |
invoice.paid and invoice.payment_failed | invoice_paid and payment_failed |
charge.refunded | payment_refunded |
customer.created and customer.updated | the contact is created or updated, tagged stripe |
Only events that carry an e-mail address can be tied to a person. No Stripe API key is held, so nothing is fetched from Stripe.
One platform. Every customer interaction.
Replace your patchwork of messaging APIs, CDP and automation tools with a single engagement platform built for scale.
No credit card required · EU data residency · 99.99% uptime SLA