ChirpBack
AppBlog
Settings

Custom domain

Serve your portal, board, surveys, and changelog from your own subdomain.

By default, your public pages live on a chirpback.io subdomain. With a custom domain you can serve them from a subdomain you own — feedback.yourcompany.com, talk.yourcompany.com, and so on.

What gets mapped

One custom domain covers all your project's public surfaces:

  • The public portal (board, surveys, changelog)
  • Survey share links — https://<your-domain>/s/<publicId>
  • Announcement permalinks
  • Changelog feeds

Setup

1. Add the domain in ChirpBack

Project Settings → Custom Domain → enter your domain (e.g. feedback.yourcompany.com).

ChirpBack generates two DNS records you'll need to publish at your DNS provider:

  • A TXT record — used to verify domain ownership and issue the certificate
  • A CNAME at <your-domain> pointing to ChirpBack's edge

The dashboard shows the exact Name and Value for each one — copy them as-is. The TXT name comes from the certificate provider and can vary, so don't hard-code it from a guide.

2. Add the DNS records at your provider

In your DNS host (Cloudflare, GoDaddy, Route53, Namecheap, etc.):

  1. Create the TXT record exactly as shown to verify ownership
  2. Wait a few minutes for DNS to propagate (some providers are slower than others)
  3. Create the CNAME record pointing at the edge target shown in ChirpBack
  4. If your provider is proxied / CDN-aware, you can usually leave proxying on
  5. For apex (root) domains, use CNAME flattening, ALIAS, or ANAME if your provider supports it

3. Verify

Back in Custom Domain → Verify. ChirpBack checks both records and the certificate. When the certificate is ACTIVE, your domain goes live.

Changing the domain

Click Change domain on the Custom Domain page to swap in a new one. The new one will need to go through the same verify flow.

Troubleshooting

DNS not verifying?

  • Wait 5–10 minutes — propagation can take time
  • Use dig CNAME <your-domain> and dig TXT <the-txt-name-shown-in-the-dashboard> to confirm both records are published
  • Double-check the values match exactly what ChirpBack shows

Still stuck? Email support@chirpback.io with your domain.

Next steps

Developer

Your SDK credentials, allowed origins, and the snippet to wire up the feedback widget.

Brand

Customize your public portal — name, colors, logo, cover image, and which tabs appear.

On this page

What gets mappedSetup1. Add the domain in ChirpBack2. Add the DNS records at your provider3. VerifyChanging the domainTroubleshootingNext steps