Enabling Multiple Custom Tracking Domains
A tracking domain (also referred to as an "engagement tracking domain") is the domain that a tracked link will redirect through before reaching the final URL path of the original link. It is also used as the path for the tracking pixel to track message opens. A recipient will see this domain if they mouse over a tracked link in an HTML message or if they receive a plain text message. SparkPost offers the option to configure one or multiple tracking domains per account.
There is a system default tracking domain that is used for tracking if you choose not to configure a custom tracking domain. For SparkPost this is "spgo.io". For SparkPost EU this is "eu.spgo.io". For PMTA+Signals, check your User Guide. For SparkPost Enterprise, it is the domain configured by your Technical Account Manager during onboarding. Once a single custom tracking domain is configured, it becomes the default and will be the tracking domain used for all of your messages. When you configure multiple tracking domains, you will associate each one with a sending domain and designate one as the default for any sending domains that don’t have a tracking domain associated with it.
To summarize, when a message is sent:
- If the sending domain has an associated tracking domain, that tracking domain will be used.
- If the sending domain does not have an associated tracking domain, the designated default tracking domain will be used.
- If there is not a designated default or if no customer tracking domains are configured, SparkPost will use the system default as described above (Note: This is for SparkPost customers only).
Process and Configuration
If you would like to configure your account to use a custom tracking domain, the process is as follows:
- Determine what subdomain you wish to use for your custom tracking domain (e.g. click.myawesomedomain.com). Please note, the tracking domain must be a subdomain and not a root domain!
- Make sure that the custom tracking domain you choose to use is one for which you have access and permission to modify the DNS.
- Edit your DNS zone file for your tracking domain to include the new CNAME (this is different depending upon who you use as your domain registrar, such as GoDaddy.com, Ghandi, or Moniker).
- Create a new CNAME record in your DNS zone file and set the host to your tracking sub-domain (e.g. click.myawesomedomain.com) with the value: "spgo.io" for SparkPost, or "eu.spgo.io" for SparkPost EU. For PMTA+Signals, refer to your User Guide (Note: For SparkPost Enterprise users, your CNAME record value should point to the tracking domain configured during your onboarding).
- Once you have completed creating your CNAME record(s) and have successfully saved the DNS changes, complete the set up through either the API or the UI (instructions for both below).
- Associate the custom tracking domain to a sending domain via UI or API.
Setting Up Custom Tracking domains through the app
To configure one or more custom tracking domains through the SparkPost app, follow the steps below.
Select Configuration and then Tracking Domains from the main menu.
Click Create Tracking Domain to add a new tracking domain.
Complete the Domain Name and then click Add Tracking Domain to complete the process of adding a tracking domain.
Associate your Tracking domain(s) with one or more Sending domains
To associate custom tracking domains to sending domains through the SparkPost user interface, the custom tracking domains must be verified first and then follow the steps below.
- Select Configuration and then Sending Domains from the main menu.
- Click the Add a Domain button to create the new sending domain or select an existing sending domain.
- Complete the Sending Domain Name for each sending domain and select the Linked Tracking Domain you want to associate with it. Note: If you do not select a linked tracking domain, the sending domain will use the default tracking domain.
- Click the Add Domain or Update Tracking Domain button to complete the association.
Note: For information on how to configure your Sending Domains, please see this article.
Note: Any newly configured tracking domains have to route back, either through delegation or use of CNAME records, in order for us to be able to report on opens and clicks. Misconfiguration of your tracking domain(s) could mean link redirection could fail, so please ensure you test prior to placing any new domains into production!
Note: Deleting a tracking domain will automatically disassociate it from all sending domains.
API Configuration: Custom Tracking Domains
You can also configure custom tracking domains by using the SparkPost REST API.
- Creating a Tracking Domain
- List all Tracking Domains
- Retrieve a Tracking Domain
- Verify a Tracking Domain
Initiate a check against the CNAME DNS record for the specified tracking domain. The domain’s status object is returned on success.
- Deleting a Tracking Domain
Using a Tracking Domain
Once a tracking domain has been associated with a verified sending domain, the appropriate tracking domain will be inserted into all links if click tracking is turned on. Note that click tracking is turned on by default and you must specifically include the option to turn it off in either the transmissions options (REST), or the SMTP API (SMTP).
More information about our click tracking options can be found here: