Artifact GuideEU

EU ePrivacy Directive direct marketing rules

Article 13 of the ePrivacy Directive sets the EU baseline for electronic mail direct marketing: prior consent is the default, with a narrow existing-customer exception for a seller's own similar products or services.

Use this page to separate consent-based campaigns from soft opt-in campaigns, preserve opt-out evidence, prevent disguised sender practices, and flag points that still depend on Member State law.

Author
Sorena AI
Published
May 9, 2026
Updated
May 9, 2026
Sections
6

Structured answer sets in this page tree.

Primary sources
4

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated May 9, 2026
Overview

For EU electronic mail marketing, the ePrivacy Directive is not a general newsletter best-practice checklist. Article 13 controls when automated calling systems, fax, and electronic mail may be used for direct marketing, when an existing customer soft opt-in can be used, and what unsubscribe and sender-identity controls must exist before a campaign is sent.

Section 1

Article 13 baseline: prior consent for electronic mail marketing

Treat electronic mail direct marketing as opt-in by default. Article 13 allows automated calling systems, fax, or electronic mail for direct marketing only for subscribers or users who have given prior consent, unless the existing-customer exception in Article 13(2) applies.

Because the ePrivacy Directive now points consent references through the GDPR framework, consent records should show a freely given, specific, informed, and unambiguous choice, plus the information presented at the time and a way to withdraw as easily as consent was given.

  • Classify the channel first: email, SMS, app message, or any text, voice, sound, or image message that can be stored until collected may fall within electronic mail analysis.
  • Separate consent-based campaigns from soft opt-in campaigns before audience selection, creative approval, or CRM export.
  • Keep campaign purpose, consent text, timestamp, source form, recipient identifier, and withdrawal status together so the marketing system can prove the permission used for each send.
  • Do not treat a GDPR legitimate-interest assessment as a substitute for Article 13 prior consent where Article 13 requires consent for the sending of the communication.
Section 2

Existing-customer soft opt-in conditions

Article 13(2) creates a narrow exception for electronic contact details collected from customers in the context of selling a product or service. The same natural or legal person may use those details for direct marketing of its own similar products or services only if the customer had a clear, distinct, free, and easy opportunity to object when the details were collected and in every later message.

Do not expand this exception to purchased lists, third-party promotions, unrelated product lines, or contacts collected outside a sale unless national implementation and a fresh source-linked review support that route. The artifact should state why the product or service is similar and why the sender is the same person or entity that collected the details.

  • Evidence the original sale or service context that produced the contact detail.
  • Record the collecting entity and sending entity; the exception is not a general group-company marketing permission.
  • Describe the similar product or service link in business terms before launch.
  • Save the opt-out text shown at collection and the opt-out mechanism included in each message.
  • Exclude any recipient who objected at collection, later unsubscribed, or is on a relevant suppression list.
Section 3

Opt-out handling and suppression lists

Soft opt-in campaigns require an opportunity to object at two points: when the electronic contact details are collected and on the occasion of each message. Consent-based campaigns also need an easy withdrawal route under GDPR consent standards. In both cases, the marketing system needs a suppression control that prevents future sends after an objection or withdrawal.

A suppression list should be limited to what is needed to honor the cease request, but it must be operationally effective. Keep enough information to match future campaign audiences against opted-out recipients, including the channel, brand or sender scope, date, source of opt-out, and any country or entity scope applied under national implementation.

  • Place the unsubscribe or objection route in every marketing email and test it before launch.
  • Process unsubscribe, withdrawal, and objection events into the suppression system before the next send.
  • Block manual uploads, CRM segments, and automation journeys from overriding suppression status.
  • Keep proof that the opt-out was free of charge and easy for the recipient to use.
  • When consent is withdrawn, stop the consent-based processing unless a separate lawful basis and transparency record support any limited retention.
Section 4

Sender identity and message integrity checks

Article 13 separately prohibits direct-marketing electronic mail that disguises or conceals the sender identity or lacks a valid address for cease requests. This is not optional formatting; it is a pre-send compliance gate.

Run this check on the final rendered message, not only the campaign brief. The sender name, reply handling, unsubscribe address, landing-page URL, and on-page commercial information should all align with the entity on whose behalf the communication is made.

  • Confirm the sender identity is visible and matches the entity responsible for the communication.
  • Verify the message contains a valid address or mechanism where the recipient can request that marketing cease.
  • Check that landing pages do not undermine required commercial identification information.
  • Reject campaigns that hide the advertiser behind a misleading domain, no-reply flow, or affiliate wrapper.
  • Store final creative, headers, landing-page URL, sender approval, and unsubscribe test result with the campaign record.
Section 5

GDPR, ePrivacy, and Member State caveats

The ePrivacy Directive particularises and complements GDPR. Where Article 13 sets a special rule for sending unsolicited communications, do not skip that rule because personal-data processing also has a GDPR lawful-basis analysis. GDPR still matters for consent quality, transparency, records, downstream processing, rights handling, and data minimisation around contact data and suppression lists.

Article 13 also leaves implementation choices to Member States for cases outside the prior-consent and customer-soft-opt-in provisions, and it requires protection for subscribers other than natural persons under Community law and applicable national law. Use this page for the EU baseline, then check the national law for the recipient market before relying on a call, fax, B2B, corporate-subscriber, enforcement, or penalty conclusion.

  • Record the national law checked for each target market when the campaign is not a straightforward prior-consent email send.
  • Do not invent penalty amounts from the Directive; Article 15a says Member States shall lay down the rules on penalties for infringements of the national provisions adopted pursuant to this Directive, and Article 13(6) says Member States may also lay down specific rules on penalties applicable to providers of electronic communications services which by their negligence contribute to infringements.
  • Escalate campaigns involving non-natural-person subscribers, telemarketing, fax, cross-border lists, or mixed consent and soft opt-in audiences.
  • Keep GDPR records for contact data processing, but keep the Article 13 send-permission analysis as its own campaign gate.
  • When several authorities may have roles, route incidents and complaints according to the relevant national implementation.
Section 6

Pre-send checklist for EU direct marketing emails

Use this checklist before a direct-marketing email, SMS, or similar electronic mail send reaches production. It is designed to catch the legal questions that Article 13 makes material, not to replace national-law review where the Directive leaves choices to Member States.

The campaign record should let a reviewer reconstruct why every recipient was eligible, how each recipient can stop future messages, and which source supported the chosen route.

Can an EU marketing team email existing customers without fresh consent?

Only if the Article 13(2) customer exception is satisfied: the contact detail was obtained in the context of a sale, the same sender markets its own similar products or services, and the customer had a clear, distinct, free, easy opt-out at collection and in every message.

Does GDPR legitimate interest replace ePrivacy consent for marketing emails?

No. Where Article 13 requires prior consent for electronic mail direct marketing, a GDPR lawful-basis analysis does not remove that ePrivacy send rule. GDPR still governs consent quality, records, transparency, and later personal-data processing.

What evidence should teams keep for Article 13 direct marketing?

Keep the campaign route, consent or soft opt-in basis, source form, sale context if used, sender identity approval, unsubscribe test, suppression-list application, final creative, landing-page URL, target countries, and national-law caveats.

  • Campaign route is labelled prior consent or existing-customer soft opt-in.
  • Consent route has consent text, capture event, proof of information shown, and withdrawal mechanism.
  • Soft opt-in route has sale context, same sender, own similar product or service rationale, collection opt-out, and per-message opt-out.
  • Suppression lists are applied to the final audience after all imports, joins, and segmentation rules.
  • Sender identity, valid cease-request address, unsubscribe link, and landing-page commercial identification have been tested.
  • National-law caveats are documented for target countries, non-natural-person subscribers, calls, fax, enforcement, and penalties where relevant.
Recommended next step

Use this EU ePrivacy Directive guide as a cited campaign review workflow

Sorena can turn the direct marketing rules on this page into cited send-permission checks, owner assignments, suppression-list tests, and reusable evidence requests for EU marketing operations.

Primary sources

References and citations

edpb.europa.eu
Referenced sections
  • Supports checklist items requiring demonstrable consent and easy withdrawal for consent-based campaigns.
"demonstrate that valid consent has been obtained"
Related guides

Explore more topics

Are cookie walls allowed under the EU ePrivacy Directive?
FAQ answer on cookie walls under the EU ePrivacy Directive, covering freely given consent, refusal and withdrawal paths, banner evidence, and national-law caveats.
Do Analytics Cookies Require Consent under the EU ePrivacy Directive?
FAQ answer on analytics cookies under Article 5(3) ePrivacy, limited analytics exemptions, configuration evidence, consent logs, and national-law caveats.
ePrivacy cookie consent vs DSA ads obligations: source-limited comparison
Compare ePrivacy cookie and tracking-consent duties with DSA ads workstreams without merging consent, transparency, and evidence obligations.
ePrivacy Directive vs GDPR: cookies, communications, consent, and evidence
Compare the EU ePrivacy Directive and GDPR across subject matter, lex specialis overlap, terminal equipment, communications confidentiality, marketing, consent, enforcement, and evidence.
EU cookie banner requirements under the ePrivacy Directive
EU ePrivacy cookie banner requirements for non-exempt cookies and trackers: prior consent, reject choices, no pre-ticked boxes, withdrawal, analytics limits, cookie walls, and evidence logs.
EU ePrivacy analytics cookies: consent, exemption, and evidence guide
source-linked guide to analytics cookies under EU ePrivacy: Article 5(3) scope, when consent is usually needed, limited analytics exemptions, consent records, and evidence gaps.
EU ePrivacy Applicability Test for Cookies, SDKs, Pixels, Communications, and Marketing
A concrete EU ePrivacy Directive applicability test for electronic communications services, terminal-equipment storage or access, cookies, SDKs, pixels, local storage, direct marketing, GDPR overlap, and evidence.
EU ePrivacy Article 5(3) terminal equipment test
A source-linked Article 5(3) test for cookies, pixels, local identifiers, device APIs, strictly necessary exceptions, and consent evidence.
EU ePrivacy Confidentiality of Communications: Article 5 controls
Article 5 confidentiality guide for EU ePrivacy communications, traffic data, metadata, terminal-equipment access, consent limits, and GDPR interplay.
EU ePrivacy consent-log evidence workflow for cookies and trackers
Build an ePrivacy consent-log workflow that records cookie and tracker decisions, banner versions, consent signals, withdrawals, vendor evidence, and audit-ready outputs.
EU ePrivacy cookie banner UX test cases
source-linked cookie banner UX tests for Article 5(3) ePrivacy consent: reject all, pre-ticked boxes, withdrawal, cookie walls, analytics toggles, and consent evidence.
EU ePrivacy Cookie Scope Classifier Workflow
Classify cookies, pixels, SDKs, local storage, device identifiers, and analytics tracers under Article 5(3) ePrivacy rules, with consent and exemption evidence outputs.
EU ePrivacy direct-marketing consent checklist
Checklist for ePrivacy Directive direct-marketing messages: consent, soft opt-in, sender identity, opt-out handling, proof records, suppression, and national-law caveats.
EU ePrivacy Directive compliance calendar for cookies, consent, and marketing
source-linked ePrivacy calendar covering Directive milestones, Article 5(3) cookie reviews, consent evidence, direct marketing checks, and national-law follow-up.
EU ePrivacy Directive Compliance Checklist
A concrete ePrivacy checklist for terminal equipment access, cookie consent, exemptions, banner UX, direct marketing, confidentiality, GDPR interplay, and evidence records.
EU ePrivacy Directive Compliance Guide for Cookies, Marketing, and Communications
Practical ePrivacy Directive compliance checks for terminal equipment, communications confidentiality, cookie consent, exemptions, direct marketing, evidence, and national-law caveats.
EU ePrivacy Directive Cookies and Consent: Article 5(3), exemptions, and banner evidence
Cookie consent guide for the EU ePrivacy Directive: Article 5(3) scope, strictly necessary and transmission exemptions, consent UX, withdrawal, logs, analytics caveats, and GDPR interplay.
EU ePrivacy Directive Enforcement and Fines
Source-grounded guide to ePrivacy Directive enforcement, national penalties, competent authorities, GDPR interplay, cookie-banner risk, and evidence limits.
EU ePrivacy Directive FAQ: cookies, consent, marketing, GDPR interplay
Answers to recurring EU ePrivacy Directive questions on Article 5(3), terminal-equipment access, cookie consent, exemptions, analytics, direct marketing, GDPR interplay, national enforcement, and evidence.
EU ePrivacy Directive Member State Cookie Rules
How to evidence EU ePrivacy cookie compliance when Article 5(3) is implemented through Member State law and national authority practice.
EU ePrivacy Directive Metadata and Location Data Guide
source-linked guide to EU ePrivacy Directive rules for traffic data, location data, anonymisation, consent, value-added services, Article 5(3) overlap, and national-law limits.
EU ePrivacy Directive penalties and fines: national enforcement caveats
source-linked guide to ePrivacy Directive penalty exposure, national transposition caveats, cookie enforcement evidence, consent defects, and GDPR overlap limits.
EU ePrivacy Directive Requirements: cookies, communications and marketing
source-linked map of EU ePrivacy Directive requirements for communications confidentiality, terminal-equipment access, consent, traffic and location data, and direct marketing.
EU ePrivacy Directive vs GDPR: cookies, communications, marketing, and evidence
Compare the EU ePrivacy Directive and GDPR by trigger, consent standard, lex specialis overlap, enforcement caveats, and evidence outputs for cookies, device access, communications, and marketing.
EU ePrivacy Directive vs UK PECR: source-limited cookie and marketing comparison
Compare EU ePrivacy Directive rules with a source-limited UK PECR workstream for cookies, terminal equipment, direct marketing, consent, soft opt-in, and evidence.
EU ePrivacy soft opt-in FAQ for email marketing
When Article 13(2) soft opt-in can support EU customer email marketing, including existing-customer, similar-offer, opt-out, sender-identity, suppression-list, and national-law checks.
EU ePrivacy soft opt-in marketing checklist
source-linked checklist for using the EU ePrivacy Directive soft opt-in exception for customer email marketing, opt-outs, sender identity, suppression records, and national-law caveats.
EU ePrivacy soft opt-in marketing review workflow
Review whether an EU electronic-mail marketing send can rely on the ePrivacy soft opt-in, with checks for customer relationship evidence, similar products, opt-out, sender identity, suppression records, and national-law caveats.
EU ePrivacy Strictly Necessary Cookie Exemptions
source-linked guide to the Article 5(3) ePrivacy exemptions for transmission cookies, requested-service cookies, analytics caveats, evidence, and national-law checks.
Is a reject-all button required for EU ePrivacy cookie consent?
Standalone FAQ answer on EU ePrivacy reject-all and refuse options for cookie banners, including equal prominence, deceptive UX, consent evidence, withdrawal, and national-law caveats.
Strictly Necessary Cookies under the EU ePrivacy Directive
FAQ answer on when EU ePrivacy Article 5(3) allows cookies without consent, with grounded examples, analytics caveats, evidence records, and national-law cautions.
What should CMP consent logs retain under the EU ePrivacy Directive?
FAQ answer on CMP consent logs for EU ePrivacy cookie consent: retained fields, consent validity signals, banner versioning, refusal and withdrawal events, proof limits, and national-law caveats.