Note: You will need access to your DNS (Domain Name Server) in order to setup the below CNAME records. Your DNS is typically used for managing your website domain and email sender domain.
Ongage requires that you setup at least 1 custom tracking domain (aka branded tracking domain) for your entire account. Ongage does not offer a generic shared tracking domain, you will need to setup a custom/branded one.
The tracking domain is used to track open and click stats.
The image domain is optional, but recommended if you'd like to make use of the convenient built-in Ongage image library. Alternatively you can host the images you'll use in your HTML emails on an external internet server.
It is recommended to only use the Ongage open and click tracking, and turn it off in any of your outbound SMTP vendor accounts (e.g., SendGrid, SparkPost, Mailgun, etc.). Double tracking, for a variety of reasons is not considered good practice by ISP mailbox providers (e.g., Gmail, Outlook, etc.) and may impact on deliverability.
There is an exception to the above, if you're using SparkPost deliverability services, then you'll want to keep tracking on both in SparkPost and Ongage. The latter is set via the SparkPost vendor connection.
What is a custom/branded tracking/image domain
That means that you need to configure a tracking domain (and optionally an image domain) based on a domain that you own.
Best practice is to base your tracking/image domain on your sending domain
It's recommended best practice that the tracking and image sub-domains share the same primary domain as your sending domain. For example if your sending domain is mybrand.com, then your tracking domain would be along the lines of trk.mybrand.com. Thus the term branded tracking domain. For deliverability and consistent branding this is best practice. There could be some edge cases where one might not want to follow this rule, and instead setup a custom tracking domain, that is different from your sending domain.
Note about DNS propagation
Note: any time that DNS changes are made (like in the below) , you need to wait for DNS propagation to complete. DNS propagation usually takes a few hours, but in rare cases can take longer if it's a brand new domain, anywhere from 24 hrs - 72 hrs (i.e., 1 - 3 days).
Sample CNAME DNS Configuration
Configure the image and tracking domains in your DNS with the following values:
The Tracking & Image Domains page is where you configure this in Ongage. There it will display the exact account ID number you need to use instead of your_account_id indicated above. Here's how this page looks for Account ID 8882. Each account will have a different account id number indicated, for your account, it will be your account id number.
Many DNS management systems might require that you also have a "." at the end of each definition.
The word "ongage" cannot be part of the image or tracking domain definition.
Assign Tracking Domain Per List
You can add and allocate different tracking domains to different lists in Ongage. In order to do so, please follow steps given below.
Go to Image and Tracking Domains >> Click on "Advanced" and go to "Domains per List"
From the list of Tracking Domains added, Click on the edit button for which you want to assign the domain per list. You can also search for the list using the search option.
On the pop up opened, select the Tracking and Image Domain.
Note: Definitions made on the list level will overrule definitions made on the ESP level.
Assign Tracking Domain Per ESP Connection
You can add and allocate different tracking domains to different ESP connections used in Ongage. In order to do so, please follow steps given below.
Go to Image and Tracking Domains >> Click on "Advanced" and go to "Domains per ESP"
From the list of Tracking Domains added, Click on the edit button for which you want to assign the ESP Connection. You can also search ESP Connection using the search option.
On the pop up opened, select the Tracking and Image Domain.
Note: You can configure domains per ESP for ESPs that are defined in your account. These settings will overwrite, for the chosen ESP, any previous domain settings that were done in the account level. For that you must first need to setup the ESP to enable the domain setup per ESP.
Configuration to Match Sending Domain and Tracking Domain for each list
In order to make sure the same Tracking Domain and Sending Domain is used for each campaign from each list, you can follow the steps given below.
Setup ESP Connection with the From Address/Reply Address with the Sending Domain you want to use. For example: firstname.lastname@example.org where domain.com is your sending domain.
Configure a Tracking domain with a sub-domain of the sending domain. For example, configure track.domain.com as Tracking Domain as per the instructions shared above in this page.
Allocate the configured tracking domain with the relevant ESP connection where you have used the same Sending Domain as per the steps shared above.
Go to List Management >> Edit List in which you want to Match the Sending Domain and Tracking domain >>> Allocate the ESP connection configured above and Save.
Follow the same process from Step 1 to Step 4 above for each list in your account where there will be a List Specific ESP connection and a relevant tracking domain configured for each of your list.
Note: While setting up new ESP connections with separate sending domains, you can use the same API credentials.
Self Service SSL Tracking & Image Domains Setup
In recent years (since 2019-2020 and even before) it's become best and widespread practice to use SSL/HTTPS links in your email messages. SSL/HTTPS in general has become a universal standard for the Internet, email included. You can now setup your custom/branded Ongage tracking domains with SSL, without any need to go through Ongage Support and Ongage's back-end DevOp services. Following you'll find instructions on how to go about that.
In order to proceed with the setup, please ensure that you have the following:
Ask Ongage Support to enable your account for SSL certificate upload (depending on your Ongage package and number of domains you need to setup with SSL, this might come with an additional cost).
Note:To validate the above files received from your domain service provider and check the domains associated with certificate files, you can use online SSL decoders like https://www.sslshopper.com/certificate-decoder.html and make sure the files and respective domains are aligned.
In additional to verifying the status it also checks DNS propagation around the globe.
Enter your tracking domain and choose the CNAME option to check verification and DNS propagation for that domain. On the results page it should point to: account_number.trkpnt.ongage.net.
Note: any time that DNS changes are made, you need to wait for DNS propagation to complete. DNS propagation usually takes a few hours, but in rare cases can take longer if it's a brand new domain, anywhere from 24 hrs - 72 hrs (i.e., 1 - 3 days).
DNS Query Command
nslookup -type=cname track.yourdomain.com 188.8.131.52 will show you the status of your tracking (and or image domain).
nslookup -type=nsyourdomain.com184.108.40.206 will show you where your domain is hosted and which DNS management system you need to use to set your tracking and image domains.
CNAME in Cloudflare not getting Verified after Configuration
In order to avoid this from happening, follow the steps below:
Go to the Cloudflare DNS setup screen.
Select the CNAME
And before adding the Record click on the orange cloud icon to make it grey.
About SSL and Tracking
The default Ongage tracking domain is implemented using regular http.
You can setup your Ongage tracking with SSL – see earlier section above on this matter.
Note: there could be additional costs related to SSL tracking setup.
Regarding HSTS Policy and Tracking Domains
There's another scenario, where you're using Ongage's regular http tracking, but your destination landing page is https (i.e., SSL) and not http. If you choose setup your tracking domain to be under that https landing page domain (e.g., trk.landingpage.com) then you'll need to make sure that the top level domain does not have an HSTS policy, or choose a different top level domain for your tracking that does not have an HSTS policy.
In order to check and delete HSTS settings in Chrome: