Campaign Settings: Setting Up Domain (URL)

Connecting a custom domain to your Raisely site can be a great way to enhance your brand recognition, making it simple for people to share and remember.

Configuring your settings in Raisely is simple. Though, to setup any custom domain you will need access to your domain provider, as much of the process is done there. If you have not setup domain names before, or lack access to your domain provider, we recommend working through this process with your IT support. We have made it simple for them with all the settings they’ll need below.

Already using a custom domain on Raisely? Follow Migrating Your Custom Domain to Raisely's New Security Setup to update your DNS to the new Cloudflare setup by 15 April 2027.

Skip Ahead to

What is a Domain?

Adding Domain name in Raisely

DNS Configuration settings for your domain provider

Moving a Custom Domain to Another Campaign

Common Issues and Troubleshooting Steps

FAQ’s

What is a Domain?

A domain is simply your site's address, also referred to as your URL. A website will always have a primary domain, example raisely.com. It may also have sub-domains, acting like an add-on to the primary domain, example support.raisely.com.

Adding Domain name in Raisely

Whether you are wanting to change to a primary domain or a sub-domain, the settings are simple within Raisely. Start here by following these steps:

Steps:

1. Within the campaign you'd like to connect the domain to, navigate to Settings > Domains.
2. In the Custom Domains section, simply add either your primary domain name or sub-domain into the field and click Save.
3. A verification pop-up is presented, providing you details for your DNS settings that need to be configured. Select Finish later if you have not yet configured your DNS, or select Check now if you are ready to verify your domain.

DNS Configuration settings for your domain provider

Once you've added your domain in Raisely, update your DNS with the two CNAME records shown in the Set up your domain dialog (Settings > Domains). Add both records with your DNS provider, then select Check now in Raisely and wait for the domain to show as Verified domain. DNS changes can take up to 24 hours.

The record values are specific to your domain and are shown in Raisely, so copy them exactly as displayed. If you enter a bare domain such as example.org, Raisely will create the www version (www.example.org). Redirect your bare domain to the www version with your domain provider.

If your domain doesn't verify immediately you may need to wait a few minutes for your DNS changes to propagate across the internet. We'll check your DNS records regularly and automatically verify your domain when it's ready.

In most instances, we recommend using a dedicated custom domain for your Raisely campaigns that is separate from your main Organisation's website. This prevents any duplication of DNS records that may cause the verification process to fail.

Moving a Custom Domain to Another Campaign

Once your custom domain is connected to Raisely, you can easily carry it from one campaign to another. You don't need to make any changes to your domain's DNS records. To move your domain, just follow these steps.

1. From your Raisely admin panel, go into the campaign you'd like to move the domain to and navigate to Settings > Domains.
2. In the Custom Domains section, enter in the domain you would like to move in the box called Add domain. Click Save.
3. Raisely will ask you if you'd like to move your domain. Click Yes, move my domain.
4. Your domain will immediately move over to your new campaign.

🟢 Note: If you have previously connected both your root domain as well as your subdomain to your Raisely Campaign, you'll want to ensure that both are moved over to your new campaign. If you do not see the option to move your root domain over, simply manually adding the domain to your new campaign settings will resolve this.

Common Issues and Troubleshooting Steps

1. Incorrect DNS Settings

Problem: The most common issue is incorrect DNS records. If your domain’s DNS is not configured correctly, it won’t point to your Raisely site.

Troubleshooting:

• Check your DNS records: Make sure both CNAME records at your DNS provider exactly match the values shown in Raisely under Settings > Domains. The values are specific to your domain.
• Migrate existing domains: If you set up your custom domain before the Cloudflare security update, follow Migrating Your Custom Domain to Raisely's New Security Setup.
• Verify DNS propagation: DNS changes can take up to 24 hours to propagate globally. Use tools like DNS Checker to check if your DNS records have propagated successfully.

2. TTL (Time to Live) Issues

Problem: TTL settings determine how long DNS records are cached before they’re updated. If TTL is too high, changes to your domain may take longer to reflect.

Troubleshooting:

• Lower the TTL temporarily: Set the TTL to a lower value (e.g., 300 seconds) when making changes to DNS records for quicker propagation.

3. Raisely Campaign Misconfiguration

Problem: Even with the correct DNS settings, your Raisely campaign may not display properly if the custom domain isn't linked correctly in your Raisely account.

Troubleshooting:

• Confirm domain setup in Raisely: Make sure that your custom domain is configured correctly in your Raisely campaign settings. Raisely requires you to enter and verify your custom domain.
• Verify that the campaign is live: Ensure that the campaign on Raisely is active and ready to display content. Sometimes, a campaign may not be live, leading to a “site not found” error or a redirection to the general Raisely site.

4. Duplicate or Conflicting Records

Problem: Having old or conflicting DNS records for the same hostname can cause DNS problems and stop your domain from verifying.

Fix:

• Remove duplicates: Check for any identical or redundant records for the same hostname and clean them up.
• Match Raisely: Keep only the two CNAME records shown in Raisely for your domain.

5. Caching Problems

Problem: DNS servers and devices cache records for a period of time. If you change your DNS records, users might still be directed to the old destination until the cache is cleared.

Fix:

• Clear DNS cache: Instruct users to clear their DNS cache or try accessing the site from a different network.
• Set low TTL: Lower TTL values can help DNS updates spread more quickly.

FAQs

Cannot find the support guide you are after? Head on over to our YouTube channel 📺 for more creative content to help you go further. You can even leave us comments, suggesting new content ideas.