Custom domains are available on Professional and Enterprise plans. Upgrade your plan to enable this feature.
api.yourgame.com), providing a seamless white-label experience for your users.
Domain Types
You can configure custom domains for different purposes:Adding a Custom Domain
Step 1: Add the Domain
Step 2: Configure DNS Records
Add the provided DNS records to your domain’s DNS settings:1
Add TXT Record
This verifies you own the domain:
- Type: TXT
- Name:
_engagefabric-verify.api.yourgame.com - Value:
{verificationToken from response}
2
Add CNAME Record
This routes traffic to EngageFabric:
- Type: CNAME
- Name:
api.yourgame.com - Value:
custom.engagefabric.com
3
Wait for Propagation
DNS changes can take up to 48 hours to propagate, though most complete within 15 minutes.
If you’re using Cloudflare, disable the proxy (orange cloud) for the CNAME record to allow SSL certificate provisioning.
Step 3: Verify the Domain
Once DNS records are configured, verify the domain:Step 4: SSL Certificate Provisioning
After verification, we automatically provision an SSL certificate for your domain:
Check the status:
sslStatus is ACTIVE and isActive is true.
Using Your Custom Domain
Once active, configure your SDK to use your custom domain:Managing Custom Domains
List All Domains
Get Domain Details
Remove a Domain
DNS Record Reference
TXT Record (Verification)
CNAME Record (Traffic Routing)
SSL Certificate Details
We use Let’s Encrypt to provision SSL certificates:- Certificate Authority: Let’s Encrypt
- Validity: 90 days (auto-renewed)
- Protocol: TLS 1.2 and 1.3
- Cipher Suites: Modern, secure defaults
Troubleshooting
Domain verification fails
Domain verification fails
Common causes:
- DNS records haven’t propagated yet (wait up to 48 hours)
- TXT record has the wrong name or value
- Domain has conflicting DNS records
- Use
dig TXT _engagefabric-verify.yourdomain.comto check the record - Verify the token matches exactly (no trailing spaces)
- Try verification again after confirming DNS
SSL certificate fails to provision
SSL certificate fails to provision
Common causes:
- CNAME record not configured correctly
- Cloudflare proxy enabled (disable orange cloud)
- Domain has CAA records blocking Let’s Encrypt
- Check CNAME resolves:
dig CNAME yourdomain.com - Check CAA records:
dig CAA yourdomain.com - If using Cloudflare, set DNS-only mode (gray cloud)
Domain works but shows certificate error
Domain works but shows certificate error
Common causes:
- Certificate still provisioning (check
sslStatus) - Certificate expired (check
sslExpiresAt) - Browser caching old certificate
- Check domain status in API
- Clear browser cache and try incognito mode
- Wait 5 minutes for certificate propagation
API Reference
Related
Enterprise SSO
Configure single sign-on for your organization
SDK Overview
Learn how to configure the SDK with your custom domain
