Custom Domains
Custom domains let you host your public FeedbackJar portal on your own hostname instead of the default FeedbackJar subdomain.
| Without | With a verified custom domain |
|---|---|
https://your-slug.feedbackjar.com | https://feedback.yourcompany.com |
Once active:
- The portal is served at your domain over HTTPS
your-slug.feedbackjar.com301-redirects to your custom domain (path and query preserved, including auto-login tokens)- Public post links, notification links, and widget portal URLs use your branded domain
- Widget auto-login lands users on your domain
Add a domain
- Open Settings → Domains (under Portal)
- Enter a hostname like
feedback.yourcompany.com - Click Add domain
Only the project owner can manage domains. Each project supports one custom domain — delete the existing one before adding another.
Configure DNS
After you add a domain, FeedbackJar shows the DNS records to create. Typical production setup:
| Type | Name | Value |
|---|---|---|
| CNAME | Your subdomain label (e.g. feedback) | portal.feedbackjar.com |
| TXT | Ownership verification name from the UI | Value from the UI |
Copy each record from Settings → Domains. Propagation usually takes a few minutes.
Cloudflare tip
If your DNS is on Cloudflare, set the CNAME to DNS only (grey cloud). Proxying (orange cloud) breaks hostname validation.
Verify
- Wait for DNS to propagate
- Click Check status
- When both the hostname and SSL are active, the domain shows Active
SSL is provisioned automatically. The first verified domain becomes Primary.
When active, you’ll see that the portal is live at https://your-domain and that your-slug.feedbackjar.com redirects there.
Status meanings
| Badge | Meaning |
|---|---|
| Pending | DNS not fully validated yet — add the CNAME + TXT records, then check again |
| Error | Provisioning failed — re-check DNS values against the UI |
| Active | Hostname + SSL are live; portal traffic uses this domain |
Limits & notes
- One domain per project — delete before replacing
- Owner only — members can’t add or verify domains
- Verified only — redirects, CORS, and public URLs use the domain only after it is Active
- No shared cookies with
app.feedbackjar.com— seamless login from the widget uses auto-login / short-lived handoff tokens, not a shared session cookie - Apex / root domains are supported when the UI shows the matching records; prefer a subdomain like
feedback.for simplest CNAME setup
Related
- Auto-Login — carry identified widget users onto your branded portal
- Single Sign-On — let visitors log in on the public board through your auth system