Skip to main content

Event Types

User events are sent to POST /api/v1/user. The Kafka topic is fixed: atlas.events.raw.user.

Track a Registration

Send this event when a player creates a new account on your platform.

Track a Profile Update

Send this event when a player updates their profile data, KYC status changes, or address is verified. Only include the fields that changed.

Request Fields

Envelope Fields (all events)

string
required
Your organization ID. Found in Dashboard -> Settings -> Organization.
string
required
Brand identifier where this user belongs.
string
required
Event type: register or update.
string
Player IP address at event time (IPv4 or IPv6).
number
Player latitude at event time.
number
Player longitude at event time.

User Profile Fields

string
required
Your internal user identifier. Must be stable across all events for the same player.
string
Player full name.
string
Player email. Must be a valid email format when provided.
string
Player phone number.
string
Player document (CPF or equivalent). Send masked or hashed values whenever possible.
string
Birth date as string (for example 1990-05-15).
integer
Gender code from your platform model.
string
Country code (for example BR).
string
Postal code / ZIP code.
string
City name.
string
State / region code.
string
Registration timestamp in ISO 8601.
string
Profile update timestamp in ISO 8601.
string
Allowed values: DESKTOP, MOBILE, APP.
string
Allowed values: ACTIVE, BLOCKED, SUSPENDED, BANNED, SELF_EXCLUDED, DEACTIVATED, PENDING.
boolean
Indicates whether this user is a test account.
string
KYC verification status from your platform workflow.

Batch Registration

For bulk imports (e.g., migrating players from a legacy system):
For historical data migrations, include the original registered_at timestamp. Atlas will backfill the analytics using the actual registration dates.

Privacy & PII

User events may contain PII (Personally Identifiable Information). Atlas handles all data in compliance with LGPD (Lei Geral de Proteção de Dados) and GDPR.Best practice: Never send raw CPF or document numbers — always hash or mask them before sending to Atlas unless your Data Processing Agreement explicitly allows it.