Domains
A domain is your attribution anchor. Every player that registers on it belongs to you — your funnel, your stats, your earnings. You can run multiple domains (your manager sets a cap).
Connect flow
Add a hostname under Domains in the portal. It moves through these states:
| Status | Meaning |
|---|---|
PENDING_DNS | Added; waiting for your DNS to point at our ingress and be verified. |
PROVISIONING | DNS verified; SSL/CDN provisioning in flight. |
ACTIVE | Live and serving traffic. |
ERROR | Provisioning failed — fix DNS and retry verify. |
DNS verification
To prove you control the hostname, add the TXT record shown in the portal at _lastdrop.<host>. Then point the host at our ingress (CNAME/A as instructed) and click verify.
_lastdrop.play.example.com. TXT "lastdrop-verify=<token-from-portal>"
play.example.com. CNAME ingress.lastdrop.example.
The platform can set a per-partner domain cap and may suspend a domain for policy reasons. You always see the current status in the portal and via the GET /v1/domains endpoint.
Per-domain settings
Open a domain to customize how it looks and tracks:
- Branding — site name, logo, brand colors.
- Landing — design template (from your allowed set) + copy overrides (headline, sub-line, CTA).
- Pixels — Meta Pixel allowlist + default pixel. Events with a pixel id outside the allowlist are dropped. The built-in event debugger shows the last events recorded on the domain with their match signals (
fbp/fbc/fbclid) so you can verify wiring before spending. - Game pacing — activity presets for the demo stage and for real play, plus the table-chat toggle. Pick by the type of traffic landing on this domain; each preset's description says what it's tuned for. Presets are independent — combine freely.
Unsaved changes are marked with a dot on the tab; Branding/Landing/Pixels save together with the Save changes bar, pacing presets apply per-card.