0.3percent
You sent it to fourteen hundred people. Five pressed one button.
The market note went out to fourteen hundred people and nobody complained. Five of them pressed the other button. The next month's note reached fewer people, for reasons nothing in your software will ever show you. What marketing automation really decides on your behalf. The ceiling Google and Yahoo both publish. And why you cannot work out your own.
The market note went out on a Tuesday morning to fourteen hundred people. It was a decent piece of work. Median price in three towns. What had actually closed against what had been asked. And two sentences at the bottom in your own voice, about the inspection that had fallen through on Elm.
Nobody complained. Five people pressed one button. Pressing a button is a different thing from complaining. It is different because it takes under a second, it makes no conversation, and you never hear about it.
The following month's note went to the same fourteen hundred people. Your software reported that it had been sent to fourteen hundred people. That is what your software can see. Some number smaller than fourteen hundred received it. A smaller number than that ever saw it in the place where a person actually reads things.
You did not find out. There is nothing to find out with. This article is about the gap between what you sent and what was read. Almost nothing written about marketing automation is about that gap at all.
In short
- The federal statute that governs commercial email does not require anybody's permission to send it. It requires that the message says what it is. It must carry a physical address. And it must offer an exit that keeps working for at least thirty days. Permission is not the law's demand. It is the mailbox providers' demand, and they are stricter.
- Google and Yahoo both publish the same ceiling for how often people may report you: three tenths of one percent. On Google's page it sits in the requirements for all senders rather than in the bulk section. So a one person office is inside it. On a list of a thousand, three complaints is the whole allowance.
- The number you cannot work out is your own. Yahoo states that the rate is calculated in their system on mail delivered to the inbox. That is a denominator no sender can see. What you can do is send less, to fewer people, more carefully. That is the entire craft.
Three things this is not
The neighbours own most of this street.
Not the busywork
A chain can fire when a form is submitted, so that nobody has to copy a name into a second system. That is a real and valuable thing, and it is a different product. That question is about work. It is answered by whether a step a person used to do now happens without them. Nothing in this article will save you an hour.
Not the old list
Going back to people who contacted you years ago and went quiet is its own project with its own rules. Those rules have dates in them. That question is about permission that may have gone stale. This one assumes the permission is current. It asks the harder thing: what you send those people, how often, and whether it reaches them.
Not the ask
Asking for a review at the right moment is a single message with a single job. It has a bright legal line running through the middle of it. That question is about one moment. This one is about the two hundred moments in between. There is no event to react to, and you are deciding whether to be in someone's morning at all.
What marketing automation actually is, once you take the busywork out of it
Three articles on this site sit next door to this one. Between them they have taken most of the obvious ground. That is useful, because what is left is the part that actually decides whether any of this works.
Marketing automation, put plainly, is a standing instruction about people you are not currently talking to. Not a task that runs itself. Not a message you decide to send. It is a rule you wrote once about who should hear from you, what they should hear, and when. It then runs for years without anyone looking at it.
That is worth saying slowly, because it changes what the risks are. A workflow that copies a name into a second system either works or does not. You find out on the day. A rule about who deserves a message from you keeps running while the people it describes change. You find out never.
What a campaign decides for you
Four decisions, and you only ever edit the second.
Who it goes to
The audience is a query, and a query written once runs forever against a database that keeps changing. The person who bought last spring is still matching the buyer segment, because nobody wrote the rule that takes them out of it. When a campaign embarrasses someone, it is far more often because of who it reached than because of what it said. And the audience is the half nobody opens again.
What it says
The only part anybody edits, and the part that carries the least risk when it is wrong. A dull message to the right person on the right morning is forgettable. A brilliant message to someone who bought through you in March reads as evidence that you do not know who they are. Being forgotten is a far cheaper outcome than that.
When it arrives
Behaviour triggers move this from a calendar to a reaction. That is a real improvement, and it is also where the strangeness comes from. Someone looks at three listings on a Sunday evening. What arrives on Monday tells them exactly how closely they are being watched. How long to wait is a design decision, and it is a decision whether or not anyone makes it on purpose.
Whether it arrives at all
This is the one nobody chooses. It is decided by a company you have no contract with. They use a rule they publish and a number they will not show you. It is the reason the other three matter more than they look. Every one of them is an input into a reputation you cannot inspect. The effects arrive weeks later on a different send.
The fourth card is the whole article. The first three are decisions you make. The fourth is a decision made about you, by an organisation that will not tell you the result. It is made on the basis of the first three.
The law that governs your email does not require permission
Start with the legal position. Most people have it backwards, and the correction is truly useful.
Almost everyone assumes American email marketing law works like a consent regime. They assume you may not email someone unless they agreed. That is the European position. It is not the American one. The CAN-SPAM Act at 15 U.S.C. 7704 sets conditions on the message rather than on the relationship. There is no clause anywhere in it requiring prior permission to send a commercial message.
What it does require is worth knowing exactly. Three of the four requirements are things a normal marketing tool does not do for you on its own.
The message must contain "a functioning return electronic mail address or other Internet-based mechanism, clearly and conspicuously displayed". A recipient can use it to ask not to receive future messages. That mechanism must remain "capable of receiving such messages or communications for no less than 30 days after the transmission of the original message". So an unsubscribe link that dies when a campaign is archived is not a technicality. It is the thing the statute names.
Once someone uses it, section 7704(a)(4) gives you a deadline. It becomes unlawful for the sender to send them a further commercial message in the scope of that request "more than 10 business days after the receipt of such request". Ten business days is roughly a fortnight. It is generous by the standards of anything else in this area. That is exactly why people trip over it. A fortnight is long enough for a sequence someone is already inside to fire once more.
And section 7704(a)(5) requires three things in the message itself. One is "clear and conspicuous identification that the message is an advertisement or solicitation". One is clear notice of the opportunity to decline further messages. One is "a valid physical postal address of the sender". A real street address, in the footer, of a real place.
There is a rule underneath the statute that is more practical than the statute. It is the one to check your own tools against. Under 16 CFR 316.5, neither a sender nor anyone acting for them "may require that any recipient pay any fee, provide any information other than the recipient's electronic mail address and opt-out preferences, or take any other steps except sending a reply electronic mail message or visiting a single Internet Web page" in order to opt out or to have that opt out honoured.
Read that against the last preference centre you were sent to. A single web page. No login. No survey about why you are leaving. No account.
Whether your market note is an advertisement is decided by its subject line
There is one more piece of the rule that matters in particular to the way real estate agents write. It is not the part anyone quotes.
The duties above attach to a "commercial electronic mail message". The natural instinct is to think a market update is not one. It contains data. It is useful. It is not selling anything. But the FTC's rule at 16 CFR 316.3 sets out how the primary purpose of a mixed message is decided. The test is not what you intended.
Where a message carries both promotional content and other content, the primary purpose is deemed commercial in either of two cases. The first is if "a recipient reasonably interpreting the subject line of the electronic mail message would likely conclude that the message contains the commercial advertisement or promotion of a commercial product or service". The second is if the transactional or relationship content does not appear "in whole or in substantial part, at the beginning of the body of the message".
The subject line. A stranger's reading of it. That is the test.
So a truly useful market note with a subject line about the market is one thing. The same note with a subject line about booking a valuation is another. The difference is decided by someone who has never met you. What follows from that is simple, and it is not a burden. Put the physical address and the unsubscribe in everything. Stop trying to work out which of your emails count.

The companies that actually decide whether your mail arrives
Now the part that actually governs your business, and it is not a law at all.
Between your sending tool and the person you are writing to sits a mailbox provider. Two of them, Google and Yahoo, publish the rules they apply to incoming mail. The rules are in plain English on a public page. That is more than most parties to your business do. They have no agreement with you. You are not their customer. There is no appeal. You can count what share of your own list sits behind those two in an afternoon. It is worth counting before you decide how much of this applies to you.
You have no way to appeal, no support line, and no notice. The whole relationship is one way. It is governed by a document on a help site. The document is not long.
The system
From something happening to somebody reading it.
Six hops, and your software stops at the third. The last three are the ones that decide whether any of the first three mattered. They are done by companies you have no agreement with. The only one of them you can influence is the fourth. Everything written about marketing automation is about the first two hops.
Scroll to follow the chain
- The trigger: Something happened
- The audience: Who still matches
- The send: Your software's last act
- The signature: Who says this is yours
- The judgement: Someone else's rule
- The inbox: Or the other folder
The requirement everybody files under bulk sending, and where it actually sits
Google's page for email sender guidelines splits into two lists. That split is the single most misreported thing in this entire subject. There is a section headed "Requirements for all senders". There is a separate one for senders of "5,000 or more messages per day".
The whole thing is widely called the bulk sender requirements. If that is the phrase you have heard, the natural conclusion is that a small business is exempt from all of it. Go and look at which list the important items are actually in. Under "Requirements for all senders": set up SPF or DKIM authentication for your sending domains, ensure valid forward and reverse DNS records, use a TLS connection, format messages according to RFC 5322, and "keep spam rates reported in Postmaster Tools below 0.3%".
The 0.3 percent is in the all senders list. A one person brokerage sending twice a month is inside it.
The larger list adds the things that truly are about volume. SPF and DKIM together rather than either. A published DMARC policy. Alignment between the domain in your From header and the authenticated domain. And one-click unsubscribe. Yahoo's sender best practices states the same requirements in its own words. It spells out two details Google's page does not: "honor unsubscribes within 2 days", and an unsubscribe process that is obvious, visible and "doesn't require users to log in".
The evidence
How long you have to stop, after somebody asks you to
Two deadlines for the same act, each taken from the document that sets it. 15 U.S.C. 7704(a)(4), linked in the section above, makes a further commercial message unlawful more than ten business days after the request. Yahoo's published sender requirements, linked below, say to honor unsubscribes within two days. Source: Yahoo Sender Best Practices, honor unsubscribes within 2 days.
The two bars are not in the same unit, and the difference runs in the safe direction. Ten business days covers a longer stretch of calendar than ten days does. So the drawn gap is smaller than the real one rather than larger. There is no third bar for Google, and that is a checked absence rather than an omission. Their sender guidelines page carries no figure in days anywhere on it. Read this as which document is actually setting your deadline, not as a scale of penalties. The statute is enforceable and the requirement is not. The requirement is still the one that will change what happens to your mail.
The regulator is not the binding constraint here, and it has not been for some time. One more line from Google's own page is worth sitting with. Notice who is giving it: not a party whose revenue rises with the size of your list. "Consider unsubscribing recipients who don't open or read your messages."
What SPF, DKIM and DMARC assert, in their own words
Those three acronyms are sold as a deliverability package. Every provider will offer to set them up for you, which is worth paying for. What is worth understanding is what each one actually claims. Their own specifications are unusually clear about it. The clarity is not flattering to the way they are marketed.
SPF is RFC 7208, and its abstract says what it is for. Existing protocols "place no restriction on what a sending host can use as the MAIL FROM of a message". SPF is the mechanism by which a domain owner "can explicitly authorize the hosts that are allowed to use their domain names, and a receiving host can check such authorization". It authorises machines. It says nothing about the message.
DKIM is RFC 6376, and it "permits a person, role, or organization that owns the signing domain to claim some responsibility for a message by associating the domain with the message". Claim responsibility. Not vouch for, not certify, not recommend. It is a signature. A signature on a bad letter is still a signature.
DMARC is RFC 7489. It ties the two together and tells a receiver what to do when neither passes. Its abstract contains one sentence that ought to be printed on every deliverability invoice ever issued.
DMARC does not produce or encourage elevated delivery privilege of authenticated email.
That is the specification saying, in its own summary, that doing all of this correctly buys you nothing in the way of better treatment. What it buys is the absence of a penalty. It also lets a receiver tell the difference between you and someone forging your domain.
Which means all three of these are needed and none of them is the work. They establish who is speaking. Whether what you said was wanted is a completely separate judgement, made afterwards, on evidence you supply every time you send.
What one-click unsubscribe actually is, and why it protects you
One-click unsubscribe is the thing in the bulk sender list that sounds like a favour to the recipient. It is worth understanding, because it is not one. It is the mechanism that protects your reputation from the people who want to leave.
It has its own specification, RFC 8058. The reasoning is written down in the introduction rather than left to be worked out. The problem it solves is technical. Anti-spam software often fetches every link in a message's headers on its own. So a plain unsubscribe link in a header could be set off by a machine rather than a person. Senders answered by putting a confirmation page behind it, and "that makes the unsubscription process more complex than a single click".
Then the specification explains why that mattered, and this is the sentence to take away:
Operators of broadcast marketing lists tend to be primarily concerned about deliverability of their mail... Hence, the mailers want to make it as easy as possible for recipients to unsubscribe; if an unsubscription process is too difficult, the recipient's alternative is to report mail from the sender as junk until the mail no longer appears in the recipient's inbox.
That is an internet standards document stating the business case for an easy exit, on the sender's behalf. Every extra step between someone deciding to leave and being gone gives them another option. That option is the button that costs you three tenths of a percent.
There is one detail with a practical result. Section 4 of the same document requires that the message carry a valid DKIM signature covering the unsubscribe headers. Without it, it says, "the mail receiver SHOULD NOT offer a one-click unsubscribe for that message". So the authentication work in the section above is not a separate project from the unsubscribe work. Get the signature wrong and the safest exit route is quietly not offered to your recipients at all.
Three tenths of one percent, and why you cannot work out your own
Here is the number, and here is the reason you cannot check yourself against it.
Both providers publish the same ceiling. Yahoo states it in as many words: "Keep your spam rate below 0.3%". Google puts it in the all senders list. On a list of a thousand people that is three complaints. Not three unsubscribes, which are a healthy sign and cost you nothing. Three people pressing the button that says this should not be here. Five of them, on a list of fourteen hundred, is the market note at the top of this page.
In your numbers
How many people have to press the button before you are over the line?
The list as it actually is, not the segment you intend to build.
Gmail and Yahoo both publish the same figure. Count the domains in your own list rather than guessing at this one. It is an afternoon's work, and it decides how much of this section applies to you.
Count everything, including the ones a sequence fires without anybody deciding.
Complaints in one send that reach the published ceiling
3.4complaints in one send
- People on the listyour 1,400
- 1,400people
- Whose provider publishes a ceilingyour 80%
- 1,120covered messages
- At the published ceiling0.3%, the figure Google and Yahoo both publish
- 3.4complaints in one send
- Across a month of sendingyour 2
- 6.7complaints a month
- Across a year12 months
- 81complaints a year
The headline is the third row rather than the yearly figure. It is there because a single send is the unit a person actually decides about, and because the number is small enough to be startling. Shares of people produce fractions, and half a complaint is not a thing. Read two and a half as between two and three. Three things this deliberately refuses. It will not work out your actual spam rate, and it cannot. Yahoo states the rate is calculated in their system on mail that was delivered to the inbox, which is a denominator no sender can see. So what you have here is a ceiling in your own units rather than a measurement of you. There is no open rate and no click rate anywhere in this chain. The section above shows what an open actually counts, and it is not attention. And there is no row for what a damaged sending reputation costs in money. Nobody has published a figure for that with a method under it. This article is not going to be the first to make one up.
Now the honest part, and it is the reason the calculator above works out a ceiling rather than a rate.
Yahoo states how the figure is derived: "Spam rate is calculated in our system based on mail delivered to the inbox". The same line tells senders to keep that in mind when referring to it. Read it carefully. The denominator, which is the bottom of the fraction, is not what you sent. It is what they delivered to an inbox. Mail that was rejected or filtered before arriving is not in the bottom of that fraction.
That has an uncomfortable result. As your reputation falls, more of your mail is filtered. That shrinks the denominator. A smaller denominator raises the rate worked out from the complaints you still receive. The measurement moves against you at exactly the moment you would want it to hold still. And there is no version of the sums you can do at your own end that reproduces it.
Google publishes yours to you through Postmaster Tools. It is free. It takes about ten minutes to set up if you control your sending domain's DNS. That is the most useful thing in this article in practice. For a sender without an enterprise deliverability contract, it is also the only measurement of their own reputation available to them anywhere. That makes it worth ten minutes, whatever else you take from this.
What an open actually measures
The other half of the reporting problem is the number everybody does look at.
An open is not an event. Nobody tells your software that a message was read. Here is what happens. The message contains a small image hosted on the sender's server. If the recipient's mail client fetches that image, the fetch is recorded and reported to you as an open. That mechanism has two well known failure modes in opposite directions. Clients that block remote images never register an open for a message someone read carefully. Clients that fetch images on their own register one for a message someone deleted from the preview pane.
That much is widely understood. What is less widely understood is what else is in there, and there is a measurement of it.
The evidence
What a corpus of 12,618 commercial emails was carrying besides the message
Three shares of the same corpus of 12,618 commercial emails from 902 senders. A crawler collected them by subscribing to mailing lists on 15,700 websites. They were then opened in a real email client while the network traffic was recorded. Source: Steven Englehardt, Jeffrey Han and Arvind Narayanan, I never signed up for this! Privacy implications of email tracking, Proceedings on Privacy Enhancing Technologies 2018.
The authors state their own limit, and it is the one that matters here. They write: "our corpus of emails is not intended to be representative, and we are unable to draw conclusions about the extent of tracking in the typical user's mailbox." So read this as what commercial mailing lists were doing rather than as what your own provider does. The study is also from 2018. The third bar in particular describes a practice that mailbox providers have since made harder rather than one that has grown. What has not changed is the mechanism, and the mechanism is the reason it is here. None of this is added by the sender. All of it arrives with the tooling. And the researchers' own list of open questions includes whether a sender setting up a campaign is even told that the tracking is there.
Read the chart with the note under it, because the authors are careful about what they are and are not claiming. What survives the caveats is the mechanism rather than the rate. A commercial email is a page, and that page loads resources from other companies. How many of those a sender put there deliberately is exactly what the researchers could not resolve. They listed it as an open question at the end of their own paper. When a sender sets up a campaign with a mailing list manager, is the tracking disclosed to the sender at all.
Be careful about what that does and does not license you to say. The same paper reports that most of the address leaks it found, 62 percent by its own heuristics, were intentional on the sender's part. So this is not a story in which senders are uniformly innocent. What it is is a strong argument for finding out which case you are in. That takes ten minutes rather than a project. Send yourself a campaign. Open it in a browser with the developer tools showing. Read the list of domains the message contacts. It is your list, going to those companies, with your name on it. Right now you probably do not know whether it is three or thirty.

Why the second campaign is harder than the first
There is a mechanism running underneath all of this. It explains why people's experience of marketing automation gets worse rather than better. It is not fatigue, and it is not the copy going stale.
Everything in the sections above builds up in one direction. The judgement a mailbox provider makes about your next message is formed from how people reacted to your last one. So the first send to a list that has never heard from you is the easiest one you will ever do. Every send after it is graded against a record you are writing as you go.
Three results follow, and none of them are obvious from inside a dashboard.
The first is that mistakes are paid for later and somewhere else. A badly aimed send in March does not cost you March. It costs you part of the delivery of the April message, to the people who were pleased to hear from you. Nothing in your reporting will connect the two events.
The second is that adding people to a list is not free even when they never respond. Every address that did not want the message is a source of the evidence that grades you. The ones who never open anything are the ones most likely to press the wrong button in the end.
The third is the one that changes behaviour, and it is why the close of this article is what it is. The cheapest lever available to you is not better writing, a better subject line or a better tool. It is a shorter list. A shorter list of people who want the message improves the one input you actually control. And it improves it on every future send rather than on this one.
What it costs and how long it takes
There is no price on this page. The reason is that the costly part of this one is not software at all.
Three things are being paid for. The sending platform is a subscription priced per contact by whoever you use. It is the smallest number in the project by a distance. Then the set-up: audiences, triggers, delays, suppression rules, and the joins to wherever your contact data actually lives. Then the item nobody quotes. That is getting your sending domain into a state where two things are true. The three records above are correct, and the address in your From line is aligned with them.
That third part is where the time goes when it goes badly. If your domain's DNS is somewhere you control and nobody has set up anything unusual, it is an afternoon. If your mail has in the past gone out from three different tools under two different subdomains set up by people who have left, it becomes a long dig. The honest order is to finish it before writing a single campaign rather than after.
The other real cost is a person. Audiences rot, and they rot quietly. So someone has to own the rules and look at them on a schedule. That is not a big job, and it is nobody's job by default. That is how a segment defined once outlives everyone's memory of what it was for.
Before spending anything, run the audit below. It is free, and it takes an afternoon. It settles the only question that decides the shape of the project. Is your domain already in good order, or has it been quietly piling up settings for six years?
What it does not do, and should not pretend to
It does not create demand. Every mechanism described here assumes someone who already has a reason to hear from you. A cadence does not turn a person who is not moving into a person who is. Pointing one at people who never asked is a different activity with a different set of risks.
It does not get your mail delivered. Authentication removes a reason to reject you. Delivery is a judgement made by someone else, on the basis of how the people you sent to reacted last time. The only lever you have on it is who you send to and how often.
It does not tell you whether anyone read anything. Opens are a proxy with known failure modes in both directions. Clicks are a proxy for interest in one link. Neither is a measurement of attention. A dashboard built out of them can look healthy while the mail is being filtered.
It does not fix a message that should not be sent. Behaviour triggers change when something arrives, not whether it should. A poorly judged email delivered at the perfect moment is a poorly judged email that arrives faster. Getting the timing right does not buy forgiveness for the content.
It does not survive being aimed at everyone. This is the limit that costs the most and the one people resist, because a bigger list looks like a bigger asset. Every send to someone who did not want it is evidence handed to a filtering system. It is scored against your domain. The damage lands on the next message you send to the people who did want it.
Three ways a good build produces nothing
None of them are the software.
A segment nobody ever leaves
Someone defines the buyer audience on the day it is built. Nobody ever writes the rule that removes a person from it. Two years later it contains everyone who has ever filled in anything, including the family whose closing you attended. Every campaign is then aimed at a group that has quietly stopped meaning anything. The reporting will look fine, because the reporting counts sends.
A sender address nobody owns
The mail goes out from a subdomain a contractor set up. It is authenticated by records nobody in the business can read. The reputation attached to it belongs to whoever last configured it. The day it goes wrong there is nobody to ask. This is dull. It takes an afternoon to fix while it is small, and it cannot be fixed in a hurry.
Reporting that measures the sending
Sends, opens, clicks. All three are counts of what your own software did, and the first is entirely under your control. A dashboard built out of them will show a healthy campaign right up to the point where the mail stops arriving. That is because nothing in it is a measurement of the only thing that matters. That is whether a person read something and thought better of you for it.
The honest read
Send us the domain you send marketing email from, and roughly how many people are on the list. We will tell you what your authentication records currently say. We will tell you whether the address in your From line is aligned with them. And we will tell you which of the two published requirements you are already meeting without knowing it.
It is a short reply from a person, and it costs nothing. Everything we would read is published in public DNS. We do not need access to your mailing tool or your list.
How to audit your own sending in an afternoon
Nothing here needs a consultant, and none of it needs access to anything you do not already have.
- Find out what your domain publishes about itself. Your SPF, DKIM and DMARC records are public DNS entries. Anyone can read them, including you. If nobody in your business knows whether they exist, that is the finding. It is the one to fix first, because everything else depends on it.
- Check the From line against them. Both providers require the domain in your From header to be aligned with the domain that authenticated the message. If your mail says it is from you but is signed by your mailing tool's own domain, you are failing a published requirement that you can see.
- Set up Google Postmaster Tools. It is free, and it needs a DNS record. It will show you the one number in this article you cannot get any other way. That is your own spam rate, as Google works it out.
- Send yourself a campaign and try to unsubscribe from it. Time it. Count the pages. If it asks you to log in, asks you why, or takes more than one page, it does not meet the rule at 16 CFR 316.5. It is also quietly turning people who would have left politely into people who press the other button.
- Open the same message with developer tools on. Look at the list of domains it contacts. Decide whether you are comfortable with it. There is no right answer here, and there is certainly a wrong one, which is not knowing.
- Open your largest audience and scroll to the bottom of it. Read the last twenty names. If you recognise someone who bought through you, someone who told you they were staying put, or someone who is now a competitor, your audience rule has no exit condition. It has not had one for a while.
- Count your sends over the last ninety days. Not campaigns. Messages that left the building, including every automated one. Count it before you guess it. It is the input with the largest effect on everything above. It is the one people carry the vaguest idea of.
Common questions, answered honestly
What is real estate marketing automation, in plain terms?
It is a standing instruction about people you are not currently talking to. It is a rule, written once, about who hears from you, what they hear and when. The software part is a scheduler and a mail sender. The part that decides whether it works is the audience rule, because that rule keeps running for years against a database of people whose circumstances keep changing.
Do I need permission to email somebody in the United States?
Not under the federal statute, which is the thing that surprises people. CAN-SPAM sets rules for the message. It must identify itself as an advertisement. It must carry a real postal address. It must offer a working exit that lasts at least thirty days, with the opt out honoured within ten business days. Permission is required in practice for a different reason. Mailbox providers judge you on how the people you email react. Mail to people who did not ask is what generates the reactions that get you filtered.
How is this different from workflow automation?
Workflow automation is about work. A step someone used to do by hand now happens on its own. You find out on the day if it breaks. This is about judgement at scale: who deserves a message, what it says, when it lands. They are usually built with the same tools, and they fail in completely different ways. That is why the workflow article is a separate read rather than a section of this one.
Is this the same as reactivating an old database?
No, and the difference is the consent question. Reactivating a list of people who contacted you years ago and went quiet raises questions about permission that has gone stale. Those rules have dates in them. That article covers them properly. This one assumes current permission. It asks a harder question about what you do with it week after week.
Will automated marketing annoy my leads?
Some of them, and the number that matters is much smaller than the number who are annoyed. Both major providers publish the same ceiling for how often people may report you as spam: three tenths of one percent. On a list of a thousand that is three people. Unsubscribes are not the problem and are a sign of a healthy list. The button next to it is the problem. Sending people things they do not care about is what makes them press it.
Why did my open rate drop?
Possibly because fewer people opened it, and possibly for two reasons that have nothing to do with your writing. An open is recorded when a mail client fetches a tracking image. So clients that block or reroute remote images bend the count in both directions. And the mix of clients on your list changes over time. Separately, if more of your mail is being filtered, fewer people are being given the chance to open it at all. Your spam rate in Postmaster Tools is a better health signal than your open rate. Unlike the open rate, it is measured by the party whose opinion decides whether your mail arrives.
How often should I send?
There is no published number for this that is worth quoting. Any article that gives you one has made it up. What can be defended is the direction. Every send is evidence handed to a filtering system, so the cost of one more message is not zero even when nobody replies. Send to fewer people more carefully, and the frequency question mostly answers itself.
What is the one thing to fix first?
Whatever your sending domain currently publishes about itself. Not the copy, not the cadence, not the segments. If your authentication is wrong, or your From line is not aligned with it, you are failing a requirement that both major providers have published in plain English. And every improvement you make above that layer is being applied to mail that may not arrive.
What to do about it
The uncomfortable idea in this article is that the most effective thing available to you is to send less.
That runs against how this category is sold. A platform priced per contact has no reason to suggest a smaller list. A dashboard built on sends and opens will always reward more of both. But the mechanism is not in dispute. It is published by the people who run it. Whether you can reach the people who want to hear from you depends on how the people who did not want to hear from you reacted. There is no other input you control.
Open the last campaign you sent. Read it as the person third from the bottom of the list, the one who bought through you two years ago and has not heard from you since except in a segment. If it does not survive that, the fix is not a better subject line. It is a smaller list. A smaller list is the one change in this entire subject that costs nothing and works immediately.
There is no price on this page, because the cost tracks four things nobody can guess from an article. How many channels you want joined. Whether your sending domain and its authentication already exist or have to be set up. How much of your contact data can be trusted enough to segment on. And whether anybody in the business will own the audience rules afterwards. The AI assessment is an hour, done with you, and it starts by reading what your domain currently publishes about itself.
Keep reading
The empty fields got filled. So did the ones that were already right. 
August 25, 2026
The empty fields got filled. So did the ones that were already right.
She is in your CRM twice. Only one of them knows she sold. 
August 25, 2026
She is in your CRM twice. Only one of them knows she sold.
They said not right now. That was three years ago. 
July 30, 2026
They said not right now. That was three years ago.

