Custom domains

Important

This page contains references of mautic.net and maestro.mautic.com because of products’ previous names. Note that these links are valid.

Campaign Studio and Campaign Factory subscribers use the Campaign Factory user interface to configure custom domains. This applies to any subscribers using Campaign Studio’s email delivery service, Sparkpost. Subscribers using their own email delivery provider (including their own Sparkpost credentials) aren’t required to add a custom domain.

Understanding custom domains

Creating a custom domain for the landing pages ensures that your message is seen and is on-brand.

When a contact views a landing page that you have created in Campaign Studio, you want the brand experience to be as seamless as possible. A custom domain for your Campaign Studio instance directs users to your domain not to Campaign Studio’s domain.

When users create instances, they are created as yourcompany.mautic.net. Landing pages from the instance have a URL such as https://yourcompany.mautic.net/landing-page-name. A custom domain would make the URL something like https://sample.yourdomain.com/landing-page-name.

Creating a custom domain

Important

You can create a custom subdomain after you start using Campaign Studio. However, Acquia highly recommends you to create one at instance creation. If you do not create a custom domain at instance creation, you might experience issues with images, links, forms, and your tracking code.

If you change an existing custom domain, all links and image URLs that point to the old custom domain are lost and must be recreated.
If those images were used from assets, you do not need to update them as those links are regenerated with the new custom domain.

If you change the customer domain for an instance that already contains existing forms, you must rebuild the cache for all forms in the instance. For more information, visit Forms.

To add your custom domain:

After determining your custom domain, add a record to your DNS manager, sign in to your domain name’s host, and create the following record:
```
Type: CNAME
Name: [subdomain]
Points to (insert your instance's subdomain):
<subdomain>.mautic.net; if the instance is hosted in US cloud
<subdomain>.eu.mautic.net; if the instance is hosted in EU cloud
<subdomain>.apj.mautic.net; if the instance is hosted in APJ cloud
```
A Certification Authority Authorization (CAA) record is required if you are also using other CAA records, such as sectigo.com. If you are adding a CAA record for your custom domain, add the following:
```
Type: CAA
Data: 0 issue "letsencrypt.org"
```
If you are unsure about the region for your instance, you can find this information in the Location field when editing the instance. If the location is:
- Mautic US or ACS US, use .mautic.net.
- Mautic EU or ACS EU, use .eu.mautic.net.
- Mautic APJ or ACS APJ, use apj.mautic.net.
Based on the TTL setting, the DNS change might take a few hours for the record to propagate.
- A custom domain cannot have both a CNAME record and another record type such as a TXT record. Your sender domain and custom domain cannot use the same subdomain name.
- Before updating the domain in Campaign Factory, ensure that you add the DNS record to point the domain to the custom domain. After adding the domain, navigate to the new custom domain. Although not mandatory, you can wait until you see a “Lost by chance?” page. Doing the opposite might cause validation delays. If you have added the record and cannot access your instance from the custom domain, create a Support ticket.
Log in to Campaign Factory at maestro.mautic.com.
Click Instances.
Locate the instance that you want to edit.
If you have not created the instance, you can create one during the instance creation process. For more information, see Instances.
Click the pencil icon next to the instance.
Enable the I have my own domain toggle bar.
Enter your custom domain.
You must include the Subdomain and your website’s domain, such as example.acquia.com. Campaign Studio saves a subdomain with mautic.net, which is necessary for its database.
- Your domain can only contain letters, numbers, or a dash. It cannot start or end with a dash or have two dashes in a row.
- Your subdomain must contain at least three characters.
- Custom domains may contain mixed-case letters.
Click Save.
After adding the DNS record, sign in to your Campaign Studio instance using the custom domain.

Validating custom domains

Campaign Factory provides an option to validate custom domains so that you can validate them instantly without waiting for the automated jobs that trigger after a fixed duration.

To validate custom domains:

Sign in to your Campaign Factory account.
Go to Instances and select a custom instance.
Click Manage Instance.
Click (Re)Validate Custom Domain.
The system sends the validation request.
- When you add a custom domain to an instance and click Save, Campaign Factory attempts to validate the domain. If the DNS records are already set, the system does not display the (Re)Validate Custom Domain option in the Manage Instance dropdown. The system also does not display this option if the I have my own domain toggle bar is disabled for the instance.
- When you add a custom domain to an instance and click Save before adding the CNAME record to the DNS manager, the custom domain validation fails and the system displays the (Re)Validate Custom Domain option in the Manage Instance dropdown. The system also displays this option if the custom domain is validated previously and the instance is updated to use a different custom domain.

Important

If a custom domain is invalid, an email notification to resolve the issue is sent immediately to all users attached to the Campaign Factory Account. If not resolved, a second email notification is sent on the 3rd day. If the issue is still not resolved, the domain will be deleted on the 6th day after the first notification.

Did not find what you were looking for?

If this content did not answer your questions, try searching or contacting our support team for further assistance.

Important

This page contains references of mautic.net and maestro.mautic.com because of products’ previous names. Note that these links are valid.

Understanding custom domains

Creating a custom domain for the landing pages ensures that your message is seen and is on-brand.

Creating a custom domain

Important

If you change an existing custom domain, all links and image URLs that point to the old custom domain are lost and must be recreated.
If those images were used from assets, you do not need to update them as those links are regenerated with the new custom domain.

If you change the customer domain for an instance that already contains existing forms, you must rebuild the cache for all forms in the instance. For more information, visit Forms.

To add your custom domain:

After determining your custom domain, add a record to your DNS manager, sign in to your domain name’s host, and create the following record:
```
Type: CNAME
Name: [subdomain]
Points to (insert your instance's subdomain):
<subdomain>.mautic.net; if the instance is hosted in US cloud
<subdomain>.eu.mautic.net; if the instance is hosted in EU cloud
<subdomain>.apj.mautic.net; if the instance is hosted in APJ cloud
```
A Certification Authority Authorization (CAA) record is required if you are also using other CAA records, such as sectigo.com. If you are adding a CAA record for your custom domain, add the following:
```
Type: CAA
Data: 0 issue "letsencrypt.org"
```
If you are unsure about the region for your instance, you can find this information in the Location field when editing the instance. If the location is:
- Mautic US or ACS US, use .mautic.net.
- Mautic EU or ACS EU, use .eu.mautic.net.
- Mautic APJ or ACS APJ, use apj.mautic.net.
Based on the TTL setting, the DNS change might take a few hours for the record to propagate.
- A custom domain cannot have both a CNAME record and another record type such as a TXT record. Your sender domain and custom domain cannot use the same subdomain name.
- Before updating the domain in Campaign Factory, ensure that you add the DNS record to point the domain to the custom domain. After adding the domain, navigate to the new custom domain. Although not mandatory, you can wait until you see a “Lost by chance?” page. Doing the opposite might cause validation delays. If you have added the record and cannot access your instance from the custom domain, create a Support ticket.
Log in to Campaign Factory at maestro.mautic.com.
Click Instances.
Locate the instance that you want to edit.
If you have not created the instance, you can create one during the instance creation process. For more information, see Instances.
Click the pencil icon next to the instance.
Enable the I have my own domain toggle bar.
Enter your custom domain.
You must include the Subdomain and your website’s domain, such as example.acquia.com. Campaign Studio saves a subdomain with mautic.net, which is necessary for its database.
- Your domain can only contain letters, numbers, or a dash. It cannot start or end with a dash or have two dashes in a row.
- Your subdomain must contain at least three characters.
- Custom domains may contain mixed-case letters.
Click Save.
After adding the DNS record, sign in to your Campaign Studio instance using the custom domain.

Validating custom domains

Campaign Factory provides an option to validate custom domains so that you can validate them instantly without waiting for the automated jobs that trigger after a fixed duration.

To validate custom domains:

Sign in to your Campaign Factory account.
Go to Instances and select a custom instance.
Click Manage Instance.
Click (Re)Validate Custom Domain.
The system sends the validation request.
- When you add a custom domain to an instance and click Save, Campaign Factory attempts to validate the domain. If the DNS records are already set, the system does not display the (Re)Validate Custom Domain option in the Manage Instance dropdown. The system also does not display this option if the I have my own domain toggle bar is disabled for the instance.
- When you add a custom domain to an instance and click Save before adding the CNAME record to the DNS manager, the custom domain validation fails and the system displays the (Re)Validate Custom Domain option in the Manage Instance dropdown. The system also displays this option if the custom domain is validated previously and the instance is updated to use a different custom domain.

Important

Did not find what you were looking for?

If this content did not answer your questions, try searching or contacting our support team for further assistance.

Important

This page contains references of mautic.net and maestro.mautic.com because of products’ previous names. Note that these links are valid.

Understanding custom domains

Creating a custom domain for the landing pages ensures that your message is seen and is on-brand.

Creating a custom domain

Important

If you change an existing custom domain, all links and image URLs that point to the old custom domain are lost and must be recreated.
If those images were used from assets, you do not need to update them as those links are regenerated with the new custom domain.

If you change the customer domain for an instance that already contains existing forms, you must rebuild the cache for all forms in the instance. For more information, visit Forms.

To add your custom domain:

After determining your custom domain, add a record to your DNS manager, sign in to your domain name’s host, and create the following record:
```
Type: CNAME
Name: [subdomain]
Points to (insert your instance's subdomain):
<subdomain>.mautic.net; if the instance is hosted in US cloud
<subdomain>.eu.mautic.net; if the instance is hosted in EU cloud
<subdomain>.apj.mautic.net; if the instance is hosted in APJ cloud
```
A Certification Authority Authorization (CAA) record is required if you are also using other CAA records, such as sectigo.com. If you are adding a CAA record for your custom domain, add the following:
```
Type: CAA
Data: 0 issue "letsencrypt.org"
```
If you are unsure about the region for your instance, you can find this information in the Location field when editing the instance. If the location is:
- Mautic US or ACS US, use .mautic.net.
- Mautic EU or ACS EU, use .eu.mautic.net.
- Mautic APJ or ACS APJ, use apj.mautic.net.
Based on the TTL setting, the DNS change might take a few hours for the record to propagate.
- A custom domain cannot have both a CNAME record and another record type such as a TXT record. Your sender domain and custom domain cannot use the same subdomain name.
- Before updating the domain in Campaign Factory, ensure that you add the DNS record to point the domain to the custom domain. After adding the domain, navigate to the new custom domain. Although not mandatory, you can wait until you see a “Lost by chance?” page. Doing the opposite might cause validation delays. If you have added the record and cannot access your instance from the custom domain, create a Support ticket.
Log in to Campaign Factory at maestro.mautic.com.
Click Instances.
Locate the instance that you want to edit.
If you have not created the instance, you can create one during the instance creation process. For more information, see Instances.
Click the pencil icon next to the instance.
Enable the I have my own domain toggle bar.
Enter your custom domain.
You must include the Subdomain and your website’s domain, such as example.acquia.com. Campaign Studio saves a subdomain with mautic.net, which is necessary for its database.
- Your domain can only contain letters, numbers, or a dash. It cannot start or end with a dash or have two dashes in a row.
- Your subdomain must contain at least three characters.
- Custom domains may contain mixed-case letters.
Click Save.
After adding the DNS record, sign in to your Campaign Studio instance using the custom domain.

Validating custom domains

Campaign Factory provides an option to validate custom domains so that you can validate them instantly without waiting for the automated jobs that trigger after a fixed duration.

To validate custom domains:

Sign in to your Campaign Factory account.
Go to Instances and select a custom instance.
Click Manage Instance.
Click (Re)Validate Custom Domain.
The system sends the validation request.
- When you add a custom domain to an instance and click Save, Campaign Factory attempts to validate the domain. If the DNS records are already set, the system does not display the (Re)Validate Custom Domain option in the Manage Instance dropdown. The system also does not display this option if the I have my own domain toggle bar is disabled for the instance.
- When you add a custom domain to an instance and click Save before adding the CNAME record to the DNS manager, the custom domain validation fails and the system displays the (Re)Validate Custom Domain option in the Manage Instance dropdown. The system also displays this option if the custom domain is validated previously and the instance is updated to use a different custom domain.

Important

Did not find what you were looking for?

If this content did not answer your questions, try searching or contacting our support team for further assistance.

Important

This page contains references of mautic.net and maestro.mautic.com because of products’ previous names. Note that these links are valid.

Understanding custom domains

Creating a custom domain for the landing pages ensures that your message is seen and is on-brand.

Creating a custom domain

Important

If you change an existing custom domain, all links and image URLs that point to the old custom domain are lost and must be recreated.
If those images were used from assets, you do not need to update them as those links are regenerated with the new custom domain.

If you change the customer domain for an instance that already contains existing forms, you must rebuild the cache for all forms in the instance. For more information, visit Forms.

To add your custom domain:

After determining your custom domain, add a record to your DNS manager, sign in to your domain name’s host, and create the following record:
```
Type: CNAME
Name: [subdomain]
Points to (insert your instance's subdomain):
<subdomain>.mautic.net; if the instance is hosted in US cloud
<subdomain>.eu.mautic.net; if the instance is hosted in EU cloud
<subdomain>.apj.mautic.net; if the instance is hosted in APJ cloud
```
A Certification Authority Authorization (CAA) record is required if you are also using other CAA records, such as sectigo.com. If you are adding a CAA record for your custom domain, add the following:
```
Type: CAA
Data: 0 issue "letsencrypt.org"
```
If you are unsure about the region for your instance, you can find this information in the Location field when editing the instance. If the location is:
- Mautic US or ACS US, use .mautic.net.
- Mautic EU or ACS EU, use .eu.mautic.net.
- Mautic APJ or ACS APJ, use apj.mautic.net.
Based on the TTL setting, the DNS change might take a few hours for the record to propagate.
- A custom domain cannot have both a CNAME record and another record type such as a TXT record. Your sender domain and custom domain cannot use the same subdomain name.
- Before updating the domain in Campaign Factory, ensure that you add the DNS record to point the domain to the custom domain. After adding the domain, navigate to the new custom domain. Although not mandatory, you can wait until you see a “Lost by chance?” page. Doing the opposite might cause validation delays. If you have added the record and cannot access your instance from the custom domain, create a Support ticket.
Log in to Campaign Factory at maestro.mautic.com.
Click Instances.
Locate the instance that you want to edit.
If you have not created the instance, you can create one during the instance creation process. For more information, see Instances.
Click the pencil icon next to the instance.
Enable the I have my own domain toggle bar.
Enter your custom domain.
You must include the Subdomain and your website’s domain, such as example.acquia.com. Campaign Studio saves a subdomain with mautic.net, which is necessary for its database.
- Your domain can only contain letters, numbers, or a dash. It cannot start or end with a dash or have two dashes in a row.
- Your subdomain must contain at least three characters.
- Custom domains may contain mixed-case letters.
Click Save.
After adding the DNS record, sign in to your Campaign Studio instance using the custom domain.

Validating custom domains

Campaign Factory provides an option to validate custom domains so that you can validate them instantly without waiting for the automated jobs that trigger after a fixed duration.

To validate custom domains:

Sign in to your Campaign Factory account.
Go to Instances and select a custom instance.
Click Manage Instance.
Click (Re)Validate Custom Domain.
The system sends the validation request.
- When you add a custom domain to an instance and click Save, Campaign Factory attempts to validate the domain. If the DNS records are already set, the system does not display the (Re)Validate Custom Domain option in the Manage Instance dropdown. The system also does not display this option if the I have my own domain toggle bar is disabled for the instance.
- When you add a custom domain to an instance and click Save before adding the CNAME record to the DNS manager, the custom domain validation fails and the system displays the (Re)Validate Custom Domain option in the Manage Instance dropdown. The system also displays this option if the custom domain is validated previously and the instance is updated to use a different custom domain.

Important

Did not find what you were looking for?

If this content did not answer your questions, try searching or contacting our support team for further assistance.

Custom domains

Understanding custom domains

Creating a custom domain

Validating custom domains

Did not find what you were looking for?

Custom domains

Understanding custom domains

Creating a custom domain

Validating custom domains

Did not find what you were looking for?

Custom domains

Understanding custom domains

Creating a custom domain

Validating custom domains

Frequently asked questions

Do I need to rebuild templates or update asset links after changing the custom domain?

Do all previous emails and analytics remain available after changing the custom domain?

Do I need to rebuild existing forms after changing the custom domain?

Do I need to rebuild anything other than form cache after changing the custom domain?

Did not find what you were looking for?

Custom domains

Understanding custom domains

Creating a custom domain

Validating custom domains

Frequently asked questions

Do I need to rebuild templates or update asset links after changing the custom domain?

Do all previous emails and analytics remain available after changing the custom domain?

Do I need to rebuild existing forms after changing the custom domain?

Do I need to rebuild anything other than form cache after changing the custom domain?

Did not find what you were looking for?

Frequently asked questions

Do I need to rebuild templates or update asset links after changing the custom domain?

Do all previous emails and analytics remain available after changing the custom domain?

Do I need to rebuild existing forms after changing the custom domain?

Do I need to rebuild anything other than form cache after changing the custom domain?

Frequently asked questions

Do I need to rebuild templates or update asset links after changing the custom domain?

Do all previous emails and analytics remain available after changing the custom domain?

Do I need to rebuild existing forms after changing the custom domain?

Do I need to rebuild anything other than form cache after changing the custom domain?