If you use Privy’s landing pages, your landing page URLs will look like:
Customers can also use domain mapping so that the landing page appears on your own domain, like:
You will need to work with our support staff to successfully configure custom domains, following the below steps.
Please be aware that custom domains will not work until all steps are completed.
1) Add a DNS CNAME record for the custom domain
A) Log into your domain’s DNS provider. [Instructions vary based on where your site is hosted and/or the registrar for your domain name.]
B) Create a new CNAME record in your DNS entries.
C) For the subdomain value, enter the subdomain you’d like to use for your landing page (e.g., “info.domain.com“).
D) For the domain name value, enter {{your Privy account identifier here}}.privy.com. To locate your Privy account identifier, go to Business Settings > Privy Code
The end result should look something like:
6F0ZB143125R8F9FCFYDBAA0.privy.com
- Save the new entry.
2) Contact Privy Support
A) After you've added the DNS records to your domain, you now have to contact Privy support with your new custom domain name (e.g., “info.example.com“) to add it to your account.
B) Once Privy support has the custom domain you want to use, we will add this to our back-end.
C) Once added to our back-end, your landing pages will have the new custom domain name, however SSL is not set up yet and you will receive an insecure warning when navigating to it.
3) Enable SSL
Your Privy landing pages must be served over SSL (HTTPS). There are two ways of approaching this. You can use your own SSL certificate, or use Cloudflare's SSL proxy
First Method: To use your own SSL Certificate:
A) Reach out to Privy support, provide us with your FQDN (Fully Qualified Domain Name) from Step 2 that you want to secure
B) We will then generate a CSR and send it to you.
Note: A Certificate Signing Request (CSR) is not the certificate itself.
Note for support: Certificates should be for Nginx or Apache2x. If given an option between PKCS or X.509 format, please choose X.509. This process to generate a CSR can take 24-48 hours to complete.
C) Provide the CSR we provided you, to your SSL provider (your web host) - In return, they will give you a SSL Certificate.
D) Reach back out to Privy support with the SSL Certificate. We will add this to our server's back-end, securing the landing page.
This process can take 24-48 hours.
I already have my own SSL Certificate:
In the instance where you already have the SSL certificate, skip steps A-C and provide Privy support with your valid SSL Certificate and matching Private Key for your FQDN to install on our back-end.
This process can take 24-48 hours.
Second Method: To use Cloudflare SSL proxy
First, log into your Cloudflare account and navigate to the DNS section:
Ensure that your CNAME record from step 2 has proxying enabled, as indicated by the orange cloud.
In the crypto section, ensure that the SSL setting is "Full."
Alternatively, add a page rule for all pages in the subdomain to have an SSL setting of "Full."
FAQs
What services are compatible with Privy custom domains?
- Privy custom domains are compatible with most services and DNS providers that allow custom CNAME records.
- Privy custom domains are not compatible with websites hosted on heroku.com because of Heroku's domain name rules.
Does Privy support wildcard subdomains?
- At this time, Privy does not support wildcard subdomains. You must provide a single subdomain for your account.
Can I use domain mapping to map to the root (apex) of my domain?
- No, mapping to the root of your domain (like http://example.com/campaigns/1) is not officially supported. If you like, you can use a www subdomain instead.
Can I customize the path of my landing pages?
- Landing pages cannot have their paths customized.
Can I host other content on a subdomain that I use with Privy?
- If you create and map a custom subdomain to Privy, that subdomain will only serve landing pages and hosted pages from Privy.