Custom domains
By default, Active Reach serves every customer-facing surface on a subdomain of actii.me (the brand subdomain — e.g. sweet-truths.actii.me/bandra/rewards, sweet-truths.actii.me/b/abc123). With custom domains, you point your own domain at Active Reach and the same surfaces render on your brand’s URL.
What can run on a custom domain
| Surface | Default URL | On custom domain |
|---|---|---|
| Storefront | {brand}.actii.me | shop.your-brand.com |
| Customer pages (feedback, reviews, rewards, members) | {brand}.actii.me/{outlet}/{page} | pay.your-brand.com/{outlet}/{page} |
| Bill page | {brand}.actii.me/b/{code} | pay.your-brand.com/b/{code} |
| Short links | act.li/{code} | go.your-brand.com/{code} |
| Landing pages | {brand}.actii.me/lp/{slug} | www.your-brand.com/lp/{slug} |
You can mix — for example, run customer pages on pay.your-brand.com while leaving short links on act.li. Each surface is configured independently.
What you need
| Item | Required |
|---|---|
| A domain you own and can update DNS for | Yes |
| Ability to add CNAME records (most registrars) | Yes |
| TLS certificate | No — Active Reach provisions Let’s Encrypt automatically |
| WAF / Cloudflare in front of the domain | Allowed; must point at the Active Reach endpoint |
Configuring a custom domain
Add the domain in Active Reach
Go to Settings → Domains → Add custom domain. Enter the domain you want to use (e.g. pay.your-brand.com).
Pick the surface
Select which surface this domain serves: Storefront / Customer pages / Short links / Landing pages. You can add multiple domains, each binding to a different surface.
Add the CNAME record
Active Reach gives you a target — typically something like aegis-customer.edge.actii.me. Add a CNAME record from your subdomain to that target in your DNS provider.
If you’re using the apex domain (your-brand.com, no subdomain), use an ALIAS / ANAME record instead of a CNAME (most registrars support this).
Verify
Click Verify. Active Reach polls the CNAME and reports back. DNS propagation is typically a few minutes but can take up to a few hours.
Automatic TLS
Once verification passes, Active Reach provisions a Let’s Encrypt certificate within 1–2 minutes. The certificate auto-renews. You see green status on the domain when TLS is live.
Activate
Toggle Active. The surface is now served on the custom domain. The original actii.me URL continues to work as a redirect target — operators can use either internally.
How identity tokens survive
Customer pages link to each other using a ?t=... identity token. Custom domains preserve this — when a customer moves between pages on the custom domain, the token is read from cookie (first-party on the custom domain) and re-attached as needed.
The cookie is scoped to the custom domain you’ve registered, so customers who visit your default actii.me URL and then later your custom domain will need to re-authenticate (via the OTP fallback flow). For consistent UX, redirect all customer-page traffic from the default to the custom domain.
Storefront-overrides
For storefronts specifically, the custom domain serves as the canonical URL. SDK pings, analytics, and outbound notifications all reference the custom domain. Active Reach maintains a per-workspace overrides map (see storefront overrides) so embedded surfaces know which URL is the source of truth.
TLS renewal monitoring
Active Reach renews Let’s Encrypt certificates 30 days before expiry. If a renewal fails (typically because the CNAME was removed or DNS changed), you get:
- An alert in your operator dashboard
- An email to org admins
- A grace window where the old certificate still serves until expiry
Re-verifying the domain triggers an immediate retry.
Removing a custom domain
Disabling a custom domain returns the surface to the default actii.me URL. Existing links on the custom domain return 301 → default URL for 30 days so external references continue to work; after 30 days they 404.
Deleting a custom domain entirely removes the redirect — references to the custom domain will fail immediately. Confirm before deleting.
What’s next
- Commerce overview — broader commerce setup
- Customer pages — the five surfaces that custom domains host
- Commerce WebView — storefront-specific behaviour