Customer events
Identity resolution and aliases
Link anonymous activity, durable user IDs, email traits, groups, and identifier changes without merging the wrong customers.
Updated 2026-08-238 min
Use the strongest available identifier
| Field | Use |
|---|---|
| userId | Your durable application or customer ID |
| anonymousId | A pre-login identifier generated by your trusted collection layer |
| traits.email | Permissioned contact address and a useful identity signal |
| groupId | Company, workspace, or account context |
| previousId | The older identifier in an alias transition |
Anonymous-to-known sequence
- 01
Track anonymous activity
Use one anonymousId consistently before authentication.
- 02
Identify after authentication
Send both anonymousId and durable userId with trusted traits.
- 03
Continue with userId
Use the durable userId for subsequent server events. Preserve message IDs across retries.
Identity transition
CopycURLNode.jsPython
curl -u 'ame_replace_me:' -H 'Content-Type: application/json' -d '{"messageId":"identify_456","anonymousId":"anon_789","userId":"cus_123","traits":{"email":"customer@example.com"}}' https://www.attunemail.com/v1/identifyUse alias only for a real ID transition
Alias links a previous source identifier to a new one. It is useful after an ID migration or when a temporary server ID becomes a durable account ID. It is not a general-purpose customer merge tool.
Add company context with group
A group message associates a customer with a company, workspace, or account and stores useful group traits for downstream context. Keep customer consent and suppression at the person level.