Episerver Campaign is the Episerver platform for cross-channel campaign management and visual creation of campaign content, including email, SMS, and campaign analytics.
You can send emails via Episerver Campaign by using the sender domain of your hosted website or online shop. If you use another email server configured for your domain, answers to emails sent via Episerver Campaign will lead to this email server and not to ours.
The DNS delegation is divided into the configuration of the sender domain and the configuration of an additional subdomain. The subdomain is used by Episerver Campaign for the technical part of the email delivery and the creation of tracking links.
When the DNS delegation is configured, Episerver Campaign sends emails with a from address like firstname.lastname@example.org. If a recipient clicks a link in an email (e.g. https://www.example.com/special-offers), Episerver Campaign converts the link to a tracking link based on the technical subdomain (e.g. https://newsletter.example.com/trackingcode). The recipient is forwarded to our tracking servers to register action data and then forwarded to the original landing page.
Please forward this information to the party responsible for your domain.
Note: If you need to set a TTL, use the value "900 seconds". This ensures that in case of any mistakes, changes will propagate in about 15 minutes. Note also the different subdomains needed in the steps below.
To use a preferred domain, several DNS records must be created. The following configuration steps use the domain example.com. The domain t.example.com is the technical subdomain of example.com.
Leads tracking links to our tracking server.
Leads technical responses (e.g. bounce messages) to our email server.
Authorizes all IP addresses used by our email servers for your domain.
Authorizes the subdomain and ensures compatibility.
Authorizes our servers to use your domain for sending emails via Episerver Campaign.
The example.com entries can be summarised as below.
|t.example.com||900||IN||TXT||"v=spf1 include:spf.srv2.de -all"|
Last updated: Jun 13, 2017