If you want to use your own email sender domain (e.g. @company.com) to send survey invitations, this article explains the necessary configuration steps.
There is one precondition to setup your own sender domain
- You purchased the Survalyzer Corporate Package (If you haven’t please contact Sales)
It is important that your email sender domain & survey domain are aligned. Please see the files below for the options.
Setting up a custom email sender domain requires an interaction between you , your IT department (DNS Management) and Survalyzer.
Step 1: Decide which email sender domain (e.g. @company.com) shall be used for invitations.
If you work for a company using @company.com usually you would like to use this domain for sending survey invitation (e.g. firstname.lastname@company.com). Therefore your IT department needs to enable Survalyzer to grant the permission using @company.com for sending emails.
After the email sender domain has been agreed, go to step 2
Step 2: Configuration through IT department/domain management
To meet the technical requirements of modern email providers (such as Microsoft, Google, and Yahoo), you need to add the following DNS records to your domain. These settings improve email deliverability and ensure that your sent emails are authenticated correctly.
DKIM EU Datacenter
Only add the record below when the link to your Survalyzer account is [yourcompany].survalyzer-eu.app
| Field | Value |
| NAME | survalyzer2._domainkey |
| TYPE | TXT |
| CONTENT | v=DKIM1; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDKyMtpfoipHUnOITQ8ZzsfQO/u5iuIVLblgQtnrlQMyPt5+oOhWteViqJZxo/5TC79Ir1MeQP8l/F/t1Nq6zCmU/8l7pBTGp1VrMV4rGOuLaoWNRHBDPVn2GRrutHp4ud8I7V19QoTkCffH6uY/Zcbtmte28LECmxj6Cxi2GJldwIDAQAB |
DKIM Swiss Datacenter
Only add the record below when the link to your Survalyzer account is [yourcompany].survalyzer-swiss.app
| Field | Value |
| NAME | survalyzer2._domainkey |
| TYPE | TXT |
| CONTENT | v=DKIM1; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCyLEF4ub+ESZoHRu5rRsiFsVF0icl8SqwNJQ3n4jv4TN77yKuBPEwjkiJmnhPK/Vq3nurJaH7C1TbMHtblTKVIOqOHP74R5FxUcsPgq65Hxd+3EFEYWHgSN20Rf0EmHNYGk/UJCzGx8SwAWrWQcnJIq7Pl6mwXIoutiveBIKHgTQIDAQAB |
Custom MAIL FROM Domain
Replace [company.com] with your domain. This means sula. is always added before your domain.
| Field | Value |
| NAME | sula.[company.com] |
| TYPE | MX |
| CONTENT | 10 feedback-smtp.eu-central-1.amazonses.com |
| Field | Value |
| NAME | sula.[company.com] |
| TYPE | TXT |
| CONTENT | “v=spf1 include:amazonses.com ~all” |
DMARC
At minimum, the following TXT record must be configured:
| Field | Value |
| NAME | _dmarc.[company.com] |
| TYPE | TXT |
| CONTENT | “v=DMARC1;p=none” |
Google, Yahoo and Microsoft require a DMARC record for bulk senders.
* p=none is often used as the default setting, but this does not protect against spoofing or misuse of your domain name and is intended for monitoring, not security.
Since your domain must meet the technical requirements for SPF and DKIM, it is wise to configure a protective DMARC policy, such as p=quarantine or p=reject. Do NOT do this without knowing the impact it will have. For help setting up an effective DMARC policy and gaining insight through reporting, we recommend the DMARC Advisor platform. By doing so, you will not only ensure compliance with the guidelines, but also actively protect your brand and your customers.
Step 3: Confirmation through Survalyzer
When your IT department/domain management updated your system please let us know and we do then necessary updates in your Survalyzer account.