Both the self-hosted as well as the SaaS version of Campaigns+ offers you the ability to keep the application URL different than the installation domain. When using Campaigns+ SaaS app, you get Campaigns+ installed on an instance belonging primarily to Mumara. After the subscription, the URL you will get to login to your account would seem like domain.mumara.host, in this URL structure, you have the ability to choose the prefix value only, rest (mumara.host) remains unchanged.
However, majority of clients look for a white label solution and want their own domain URL to open/access the application, instead mumara.host. And also in case of self-hosted version of Mumara, clients look for a way to avoid exposing their main business domain in the trace route. This function of primary domain setup will help you do that.
When you first log into your account, you will see the indication of 5 basic steps right on your dashboard, steps you would need to go through before you can finally send the first broadcast/campaign. Among these steps, first one is the Setup of Primary Domain. You can initiate the process of setting up a domain by clicking on it or you can also take another course of doing so, discussed in the following area. You cannot add a Sending Domain before you setup a primary domain. If you haven't setup a primary domain and you are clicking Sending Domain from the navigation, it may give you the caution to first setup the primary domain.
Navigate to Setup Primary Domain
Main Navigation -> Settings -> White Labeling (Primary Domain)
As mentioned earlier, a primary domain is the part of the white labeling process; therefore, the setup can be reached under one of the tabs in White Labeling function. There is a simple one field operation on Campaigns+ layout, and one step to perform in the DNS zone of the domain you want to set as primary domain.
For the primary domain field in Campaigns+, you will provide a complete URL of the domain that you will want to use as primary URL to open the login page and access your account. It can be a subdomain on your main domain like primary.yourdomain.com that you can provide for Primary domain. It can also be a complete qualified path of the main business domain as well. But most of the cases users don’t want to restrict the main domain URL and prefer to use a subdomain.
To make the domain work properly, you would need to access primary domain's DNS zone and create an A record, as indicated by the message in the above image. In the DNS Zone of your primary domain, you will need to provide the Host value of your primary domain (Prefix in case of Subdomain), selecting the record type as “A” and finally need to provide IP of the Mumara Assigned instance or installation domain (Self-Hosted Version) as a value to point the primary domain to.
The message that appears underneath the Primary Domain field reveals the IP address to point your primary domain to, or alternatively you can also ping the Mumara Assigned URL to know the IP address for providing as value in the DNS. You will see that when you provide live and fully propagated domain URL in the Primary Domain field, a check mark appears as token of acceptance of domain, a cross will appear otherwise.
Note: If you don't have any preference of your own primary domain, you can put forward the same Mumara provided instance URL to proceed with the same Mumara provided domain.