Multi-Brand Setup

Manage multiple operator brands under a single Atlas organization — with full data isolation and consolidated analytics.

What is a Brand?

A Brand in Atlas represents a single product — typically a domain or white-label:

• apostas.seusite.com.br → Brand “Seu Site Sports”
• casino.seusite.com.br → Brand “Seu Site Casino”
• whitelabel-client.com → Brand “Client A”

Each brand has:

• Its own API keys
• Its own event data (fully isolated)
• Its own analytics views
• Its own user base

All brands belong to a single Organization and can be viewed in aggregate.

Create a Brand

1. Go to Dashboard → Settings → Brands

2. Click Add Brand

3. Configure:

   • Brand Name — Display name in the dashboard
   • Domain — Your platform domain (for reference)
   • Currency — Primary currency (can have multi-currency events)
   • Jurisdiction — Operating country/region for compliance defaults
   • Sport / Casino / Both — Which event types you’ll use

4. Copy the Brand ID — you’ll need it in all API calls

Using Brand IDs in Events

Every event must include the brand_id:

{
  "org_id": "org_abc123",
  "brand_id": "brand_sports_001",
  "event": "open",
  "user_id": "user_12345",
  "bet_id": "bet_abc_001"
}

A user can exist in multiple brands (if they have accounts on both your sports and casino products). Always use the same user_id for the same physical person across brands to enable cross-brand player analytics.

Dashboard: Per-Brand vs. Consolidated Views

View	What You See
Brand View	All data filtered to a single brand
Organization View	Aggregated data across all brands

Switch between views in the top-left brand selector in the Dashboard.

User Management per Brand

Team members can be granted access to specific brands:

• Organization Admin — Access to all brands
• Brand Analyst — Access to one or more specific brands only
• Brand Compliance — Compliance reports for specific brands

API Keys per Brand

Each brand has separate API keys. Never mix keys from different brands — events will be attributed incorrectly.

# Sports brand key
X-API-Key: atl_live_sports_xxxxxxxx   → brand_id: "brand_sports_001"

# Casino brand key
X-API-Key: atl_live_casino_xxxxxxxx   → brand_id: "brand_casino_001"

Use separate deployment environments (separate .env files) per brand to avoid accidentally sending production events with a staging key.