The email looks good, the subject line is convincing and the platform says “sent.” Sales have barely moved. Before changing the offer, ask whether the right people had a chance to read the message.
A contact list is not the same as an audience that can legally and technically receive a campaign. Acceptance by a recipient’s mail server does not prove inbox placement or reading.
Email marketing needs infrastructure and a relationship that the recipient recognizes.
What each step means
An address may still be in the database after its owner unsubscribes. A message may be rejected or accepted into spam. An email in the inbox may be ignored because it is no longer relevant.
| Step | Useful question |
|---|---|
| Recorded contact | Where did we obtain the address, and what may we use it for? |
| Contact eligible for the campaign | Are the applicable conditions and preferences met? |
| Message accepted | Was it received by the recipient’s infrastructure? |
| Message visible to the reader | Where was it placed and how is it displayed? |
| Relevant action | Did the person take a step relevant to the message’s purpose? |
Not all of these steps can be measured perfectly with a single tool. That is why a good report explains how each metric is defined and its limits.
SPF, DKIM and DMARC, in business language
SPF identifies authorized sending systems for a domain. DKIM adds a verifiable signature. DMARC uses authentication and alignment to support a policy and reporting. These help establish sender identity; they do not guarantee inbox placement.
Gmail requires SPF or DKIM for senders covered by its rules. For those sending more than 5,000 messages a day to Gmail accounts, requirements include SPF, DKIM, DMARC, alignment and one-click unsubscribe for marketing and subscribed messages, alongside a visible unsubscribe link in the body. DNS, TLS and spam complaint rates also matter. Gmail: sender requirements
That threshold is not a blanket exemption for smaller lists, nor do all mailbox providers use identical rules. Check the domains, sending services and requirements relevant to the actual recipients.
Delivery depends on several conditions.
Authentication alone does not guarantee inbox placement.
IDENTITY
Domain, authentication and sending infrastructure.
CONTACT LIST
Origin, eligibility, preferences and valid addresses.
RELEVANCE
A recognizable, useful message that fits the relationship.
Illustrative framework. Application depends on the project’s context and data.
A large list can hide more problems
Imagine a company with 10,000 contacts. For this campaign, 1,500 have unsubscribed and 500 are known invalid addresses, in non-overlapping groups. That leaves 8,000 technically available contacts before checking other conditions and whether the segment is relevant.
If an old list was imported without information on where contacts came from and their preferences, the number shown in the app does not solve the problem. We do not automatically launch to all addresses just to see what happens.
In Romania, commercial email falls under Law 506/2004. A customer relationship is not blanket permission: the exception for similar products or services has conditions, including a clear, simple and free way to object. Check how the rules apply to the particular case. ANSPDCP: explanations of Article 12
A newsletter subscription is not permission for every advertising use of someone’s data. Treat the purposes and systems separately.
A reported open is not a confirmed read
Apple Mail Privacy Protection can load external content in the background, regardless of whether the recipient interacts with the email. This affects how open tracking can be interpreted. Apple: how Mail Privacy Protection works
Clicks can also include automated interactions, such as security scans. Mailchimp documents these effects and its own filters. Filtering helps, but does not justify the assumption that each remaining event is a person who wants to buy. Mailchimp: automated activity and filtering
More reported opens do not automatically mean a subject line is more persuasive. Compare relevant actions, unsubscribes, complaints, delivery failures and business outcomes using consistent periods and definitions.
“Sent” does not mean “read.”
The definitions in the report should be explained before comparison.
SENDING
The system starts sending the email.
ACCEPTANCE
The recipient’s infrastructure receives the message.
REPORTED OPEN
Privacy protections and automatic loading can affect this metric.
RESULT
A verified relevant action, inquiry or purchase.
Illustrative framework. Application depends on the project’s context and data.
Relevance starts before writing
A subscriber who has asked for news about business services may not recognize a consumer product campaign. If the change is not explained and does not respect the relationship, good design will not fix it.
Consider the segment, the expectations set at signup and the message’s benefit. An email can help someone compare options, understand a change or use a product. A discount is only one reason to get in touch.
The sender must be recognizable. A subject line that imitates a personal conversation or hides its commercial purpose may get attention while undermining trust. We assess what the message promises and whether the landing page delivers on that promise.
When the problem is in the system, not in the last campaign
A domain change, a new provider, a large import or several teams sending independently can change delivery conditions. If the newsletter, automations and commercial communications use the same infrastructure without coordination, the evaluation of a single message is incomplete.
Check the email itself too: it should make sense without every image loading, its links should work and the key action should be clear on mobile. Test inboxes help reveal problems; they do not prove identical placement for everyone.
How we approach email at NOT MORE.
Together, we analyze where the list came from, the contact rules, the infrastructure, segmentation and the purpose of each message. Then we choose what is worth repairing and what is worth testing in communication.
We do not judge the channel by open rate alone. We connect the business objective with what the recipient has reason to receive. Strategy, implementation and ongoing checks belong together.
Who prepares the send, and who validates the contact list
NOT MORE. can build the segmentation, messages, sending configuration and agreed checks. Your team supplies information about where contacts came from and validates permitted uses. A designated person handles domain access and technical changes, directly or with us.
After launch, management can include monitoring delivery, errors, unsubscribes and meaningful responses. We specify who intervenes and which adjustments are needed. The list, infrastructure, content and evaluation belong to the same activity.