What tracking and sending domains actually are?

What tracking and sending domains actually are?

TRACKING DOMAINS:
If you have AppMail installed on email.a.com and you send campaigns, all your URL links will start with https://email.a.com and this is fine for most of the cases, but what if you want to handle emailing for b.com domain?
In this case, you will have to either install AppMail in a subdomain for b.com domain like email.b.com or you can still use the install from email.a.com but use a tracking domain for b.com domain.

A tracking domain is simply a CNAME (DNS Record).
In our case, we define a cname for b.com domain, namely email.b.com that will point to email.a.com subdomain.
Once we do this, propagation can take up to 48 hours, so after 48 hours, we can go in the backend of AppMail website and add a new tracking domain, the email.b.com domain. Once we did this, to check if everything works properly, we have to access https://email.b.com and we should get same page that we get when accessing https://email.a.com. If it’s not showing same page, then you don’t use a dedicated ip address for a.com domain and you should.
Now, our tracking domain is in place, all we have to do is to associate it with a delivery server and all emails that will be sent via that delivery server will change all the links from email.a.com into email.b.com.

SENDING DOMAINS:
You should use sending domains only if your delivery servers do not sign your emails with DKIM, because the only purpose of sending domains is to identify the domain from the “FROM” or “Return-Path” of your headers and generate a dkim signature for them.
Like in the above case, if your domain is b.com and you send emails from contact@b.com, then you can add a sending domain (b.com) for which AppMail will generate the dkim records (you have to add the public key into your dns records, as a TXT record).
Once the domain is confirmed, each time when AppMail finds an email that contains the domain b.com in it’s FROM/Return-Path headers it will append the right DKIM signature.

Note: If you are using CloudFlare or a similar service make sure you change the DNS records from the proper place.

    • Related Articles

    • Smart Tracking

      Starting with version 2.5.1, we have added a new feature that allows filtering out bot-generated opens and clicks, a functionality that has been long requested by our customers. Background on "Fake" Opens/Clicks The opens/clicks rate provides ...

    • Enable the use of temporary queue tables when sending campaigns

      The main issue we have with huge AppMail apps is that the campaign_delivery_log table becomes huge (I’ve seen installs with hundred GB’s of data in that table alone) and we use that table to join against when we send the campaigns so that we can see ...

    • Understanding how the sending quota and limits work

      This subject is always brought into our attention by our customers. Setting quota and limits can be done from Backend->Settings->Customers->Sending tab. These settings will apply to all customers registered into the system which are not assigned to a ...

    • Sending Groups

      Historically, until version 2.0, when you wanted to send a campaign to more than one list/segment, AppMail would merge the selected lists/segments into a new list and would then send the campaign to that new list. Performance wise, this is a very bad ...

    • My campaigns don’t send, they’re stuck in “Pending-Sending” status

      When this happens, most likely the cron jobs that must run in order to pick up the campaigns and send them are not running, and no, it’s not something wrong with the application, but you simply need to feed the application with the right data in ...