Skip to main content
All Collections
Creating and adding a sender email
Creating and adding a sender email

Everything you need to know about creating and managing an email sender

Updated over a year ago

Would you like to use the Emailing editor to send emails to your participants during a campaign and/or post-campaign using the Segment Option, but you don't have a Sender?

Well, you've come to the right place. We're going to explain how to configure your sender.

First of all, let's get down to basics:

  • What is a domain?
    A domain is a unique entity on the Internet with a specific address, such as "example.com".

  • What is a sub-domain?
    A sub-domain is a subdivision of the main domain, such as "blog.example.com" where "blog" is the sub-domain. It's easy to recognise, there's always a "." between the sub-domain and the domain.

  • What is a sender?
    Bear in mind that your sender is always made up of 2 elements: your "contact", and the domain on which they can be "contacted" (at Adictiz, this contact domain can be different from the campaign delivery domain), for example:

Domain or sub-domain managed by you

In the case of a domain

If you have a dedicated domain of your own, it's very simple: you can attach an email address directly to it.

The choice is yours:

  • Create a real mailbox (if you want people to be able to reply to emails and you want to receive them)

  • Don't create a mailbox, and just define a sender of type [email protected]

In both cases, you must submit the sender to us via the Support Chat.

Once received, our team will enter it into the backoffice and send you a CSV file with all the DNS records you need to notify:

These DNS records (CNAME, TXT, DMARC, DKIM, SPF), whose purpose is to improve the deliverability of emails, must absolutely be notified on your side for it to be validated on ours.

In the case of a sub-domain

For reasons of performance and quality, and to avoid polluting the reputations of your internal email marketing domains, it is VERY strongly recommended that you dedicate a sub-domain to Adictiz for sending emails.
In this way, we can guarantee that we will have no impact on the performance of your campaigns outside Adictiz and we can control the delivery rate in the best possible conditions.

In this way, we can guarantee that we will have no impact on the performance of your campaigns outside Adictiz and we can control the deliverability rate in the best possible conditions. If you ever broadcast your Campaign on a sub-domain belonging to you, and you want the sender to also be under this sub-domain (for example: if your campaign is under jeux.mondomaine.com and you want your sender to be : [email protected]).

You'll need to contact us, as this is a technically complicated configuration via DNS delegation, but we have alternatives to offer that will be effective and functional, so don't hesitate to talk to your Account Manager or contact Support about this specific case.

Dedicated domain created by Adictiz

If your campaign publication domain was initially created by our teams, it's even simpler. You don't need to do anything technical, just send us your desired sender email via Chat.

We'll set it up for you directly in your account.

✍️ As a reminder, if you don't yet have a dedicated domain or sub-domain for publishing your campaigns, remember to create one. The "adbx.io" domain is intended exclusively for campaign testing and acceptance.

Under no circumstances should a campaign be published publicly on "adbx.io".

✍️ Special cases:

If you want your users to be able to reply to your emails, a special configuration is required. Discuss this with the Chat Support team (see above).

Meaning of DNS records

  • CNAME (Canonical Name) : This record is used to redirect a domain name to another domain name. It is used to create aliases and point a sub-domain to another domain name.

  • TXT (Text) : This record is used to contain arbitrary text. It is often used to provide textual information about a domain. For example, public keys for domain verification, verification information for messaging services, etc.

  • DMARC (Domain-based Message Authentication, Reporting, and Conformance): This record is used to specify email authentication policies for a domain. It helps protect against spoofing and identity theft by indicating how recipients should handle unauthenticated email.

  • DKIM (DomainKeys Identified Mail): This record is used to add a cryptographic signature to outgoing emails. It is used to check that the e-mail comes from the domain it claims to be from and that it has not been altered in transit.

  • SPF (Sender Policy Framework): This record specifies the servers authorised to send e-mail for a specific domain. It helps prevent spoofing by specifying the servers authorised to send e-mail on behalf of a given domain.

Why register DNS?

Beyond the "Deliverability" aspect discussed above, declaring these DNS records is crucial for several reasons:

  • Email authentication and security: DMARC, DKIM and SPF records help reduce the risk of spoofing, phishing and other email-related attacks by confirming the authenticity of the sender.

  • Domain reputation protection: DMARC, SPF and DKIM records help maintain domain reputation by letting email providers know which servers are authorised to send email on behalf of that domain. This can prevent legitimate emails from being flagged as spam.

  • Identification of services and configurations: CNAME and TXT records are used to redirect traffic to other domains or to provide specific information, such as verification keys, configuration data, service identifiers, and so on.

In short, the correct configuration of these DNS records is essential to guarantee the security of e-mail communications, protect the domain's reputation and make it easier to identify the services linked to a specific domain.

Check your DNS records

You can check whether your DNS records have been passed on and are effective. Here are the different links to check them:

I'm running my campaign on jeux.monsite.com and I'd like to have the Sender [email protected]. Is this possible?

This is a special case for us. We'd have to look at it together to make sure that DNS records can be deployed there, in which case it might work.

Are there any sender names to avoid?

Not really, we don't recommend the term "noreply" for example, but there are no contraindications to this, and it won't affect the deliverability of your emails. On the other hand, pay attention to the words in your email subject lines.

Did this answer your question?