Monetly Docs
Custom Domains
Understand Monetly subdomains, custom subdomains, and customer-owned domains for validation experiments.
Public usage documentation: this page explains how to use Monetly. It does not define product logic. Core behavior is governed by Monetly's internal Decision OS and platform contracts.
Summary
Monetly can serve experiments on generated Monetly URLs, custom Monetly subdomains when your plan allows it, or customer-owned domains when custom-domain setup is available.
Use a custom domain when trust and audience context matter, and finish DNS verification before sending traffic.
Key Rules
- Default Monetly subdomains are generated for experiments that do not use a custom domain.
- Custom Monetly subdomains are a plan-gated convenience feature.
- Customer-owned custom domains require DNS verification before launch.
- After an experiment is owned by a custom-domain flow, public traffic should use the connected domain instead of Monetly-owned public URLs.
Steps
- Choose the domain option during experiment creation when available.
- For customer-owned domains, enter the full domain or subdomain you control.
- Add the DNS records shown in Monetly at your DNS provider.
- Return to Monetly and verify the domain.
- Launch only after the connected domain is verified and ready.
Common Mistakes
- Adding DNS records at the wrong provider or managed zone.
- Sending traffic before verification finishes.
- Expecting a released custom-domain experiment to keep serving from a Monetly public URL.
Default Monetly Subdomains
Default subdomains are generated by Monetly and are useful when you want the fastest setup path.
They keep domain setup simple, but they may be less natural for audiences that expect your own brand domain.
Customer-Owned Domains
A customer-owned domain can make the experiment feel closer to the real product context. This can be useful when trust affects behavior.
DNS changes can take time to propagate. Wait for Monetly verification before relying on the URL in traffic campaigns.