Customer events
Connect Segment or RudderStack
Reuse a Segment-compatible server library by changing the data-plane URL and write key.
Connection settings
| Setting | Value |
|---|---|
| Data-plane or API base URL | https://www.attunemail.com/v1 |
| Write key | The one-time AttuneMail connection secret |
| Collection environment | Server-side only |
| Preferred transport | Batch, up to 500 messages |
Supported calls
- ✓track for customer behavior
- ✓identify for customer traits
- ✓group for company or account context
- ✓alias for identifier transitions
- ✓page and screen for deliberate server-side navigation signals
- ✓batch for mixed message types and efficient delivery
Safe cutover
- 01
Create a staging connection
Mirror a small, non-sensitive event set and compare received counts and schemas.
- 02
Preserve messageId
Forward the producer's original message ID so retries and dual-delivery do not create duplicate customer events.
- 03
Validate identity
Confirm anonymous-to-known transitions and customer email traits before enabling any journey.
- 04
Move production traffic
Create a separate production connection, update the destination, then monitor failures and unknown schemas.
Send compatible messages
Mixed batch payload
CopycURLNode.jsPython
curl -u 'ame_replace_me:' -H 'Content-Type: application/json' -d '{"batch":[{"type":"identify","messageId":"id_123","userId":"cus_123","traits":{"email":"customer@example.com"}},{"type":"track","messageId":"evt_123","userId":"cus_123","event":"workspace.created"}]}' https://www.attunemail.com/v1/batch