Set up custom domain
If you want a specific url for your event site and you've already got the domain at your registrar, this article describes how to connect it to your Confetti site. To set up a custom domain for your event site you must do settings both at your domain provider and in Confetti.
Set up custom domain at domain provider
First you need to point your domain to Confetti through your domain provider. If you are not familiar with setting up domains we recommend you to send this article to you domain provider.
Go to the DNS (Domain Name System) setup for your domain. Then add a CNAME (Canonical Name) record from the subdomain you want to use and point it to cname.confetti.events. This change usually take a few minutes but it can take a few hours in worst case.
Setup custom domain at Confetti
This is how you set up your domain at Confetti:
Click on `Settings`
Click on `Setup`
Click on `Domains`
Add www.yourevent.com to the list of domains. Your new domain should be primary.
Subdomains (www e.g.) is most common and recommended!
Naked domains (domain without www)
A naked domain is the domain without www or similar in front of it. A naked domain would for example look like this: yourevent.com. It works a bit different and can't be used with CNAME on all domain providers. Some providers allow you to add a CNAME or ALIAS record for your domain. In that case you point it to cname.confetti.events, just as mentioned above, and then add yourevent.com to Confetti.
If your provider doesn't allow this handling of naked domains the best solution is to make yourevent.com redirect to a subdomain of your choice, like www.yourevent.com. This is sometimes supported by the domain provider, contact them for more information.
Read more here: http://wwwizer.com/naked-domain-redirect
Don’t put Confetti in an iframe
Don't put Confetti in an iframe (inline frame) to handle the support of the named domain, as this will have unpredictable results. When you click the `Signup`-button the url should change to yourevent.com/signup, if not, you're probably using the iframe "solution".