🌐Custom Domain Setup
Serve request links and video recordings from your own domain instead of birdie.so. Give customers a fully branded experience they recognize and trust.
Setting up a custom domain for the first time
If your links are currently under birdie.so and you enable a custom domain, all existing birdie.so links will continue to work. We will continue to support those links.
Changing from one custom domain to another
If you already use a custom domain, for example capture.acme.com, and switch to a different one, for example capture.acme.app, all links generated under the previous custom domain will stop working.
Make sure to update any support flows that include these links, such as AI bots, macros, etc...
What is Custom Domain?
A custom domain lets you serve Birdie recording pages from your own domain instead of a Birdie domain.
For example, instead of sharing a link like: https://notion.birdie.so
You can use your own branded link such as: https://capture.notion.com
The recording experience remains exactly the same for your users. The only difference is that the page is hosted under your company’s domain, which helps maintain brand consistency and can simplify security or compliance requirements.
How to set it up?
Step 1 – Register Your Domain in Birdie
Open your Birdie Workspace
Go to Settings → Incoming Recordings → Identity
Next to Custom Domain, click Set up
Enter your Apex Domain (without subdomain), e.g.:
yourdomain.com
Birdie will automatically provision and use a subdomain such as: capture.yourdomain.com This subdomain will serve recordings and related assets.
Step 2 – Configure Domain Ownership & Traffic Routing
Add the first CNAME record exactly as provided in the Birdie interface.
Example (values will differ):
⚠️ Important: Do not modify the target value. Do not replace CNAME with A/AAAA, or ALIAS records.
DNS propagation typically completes within a few minutes but may vary depending on your DNS provider.
Once this record is detected, Birdie will automatically proceed with TLS certificate validation.
Step 3 – Configure TLS Certificate Validation
Add the second CNAME record exactly as provided.
Example (values will differ):
⚠️ Important: Do not modify the target value. Do not replace CNAME with A/AAAA, or ALIAS records.
After DNS propagation, AWS Certificate Manager (ACM) will automatically validate the certificate. No additional action is required.
Step 4 – Automatic Activation
When both CNAMEs resolve correctly:
Domain ownership is verified
TLS certificate is issued automatically
The domain becomes active
Status updates are reflected in the Birdie UI
No manual approval or support intervention is required.
Custom Storage Buckets & CORS (Important)
If you do not use a custom bucket, you may skip this section.
If you use a custom storage bucket (AWS S3, Google Cloud Storage, or Azure Blob Storage), you must update your CORS configuration.
Add your new fully qualified domain name (FQDN) to the allowed origins list:
Example for AWS S3 CORS Policy:
This configuration is required for:
Video playback
Recording uploads
Web recorder access
If not configured correctly, browsers will block requests due to CORS policy restrictions.
Update Your Integrations
After activating your custom domain, update any existing integrations or hardcoded URLs.
For example:
Common locations requiring updates:
Helpdesk signatures
Helpdesk macros
AI bot
Automated workflows
Troubleshooting
Ensure both DNS records are configured as CNAME (not A, AAAA, or ALIAS)
Verify DNS propagation:
dig capture.yourdomain.comConfirm there are no conflicting DNS records
For CORS-related issues, review browser console errors first
Once validation completes, Birdie will securely serve all recording traffic from your custom domain.
Last updated