Campaign Factory

Custom domains


There are references to and due to the 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 you’ve 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 Campaign Studio’s.

When users create instances, they’re created as Landing pages from the instance have a URL such as A custom domain would make the URL something like

Creating a custom domain


You can create a custom subdomain after you start using Campaign Studio. However, Acquia highly recommends that you 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.

To add your custom domain:

  1. 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>; if the instance is hosted in US cloud
    <subdomain>; if the instance is hosted in EU cloud
    <subdomain>; 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 If you are adding a CAA record for your custom domain, add the following:

    Type: CAA
    Data: 0 issue ""

    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 EU or ACS EU, use
    • Mautic APJ or ACS APJ, use

    The DNS change might take a few hours for the record to propagate, depending on the TTL setting.


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.

  1. Log in to Campaign Factory at
  2. Click Instances.
  3. 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.

  4. Click the pencil icon next to the instance.

  5. Toggle the switch for I have my own domain.
  6. Enter your custom domain.

    You must include the Subdomain and your website’s domain, such as Campaign Studio saves a subdomain with, 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 3 characters.
    • Custom domains may contain mixed-case letters.
  7. After adding the DNS record, sign in to your Campaign Studio instance using the custom domain.

Validating custom domains

Campaign Factory allows you to validate custom domains. Thus, you can get the domains validated instantly without depending on automated jobs that get triggered after a fixed duration.

To validate custom domains:

  1. Sign in to your Campaign Factory account.
  2. Go to Instances and select a custom instance.
  3. Click (Re)Validate Custom Domain.

    The system sends the validation request.