Deliverability Case Study: "Brute Force Marketing"
This track is a satire, and the joke is structural: the narrator is the brand, the addressee is the customer, and the register is pursuit. "Du läufst, wir laufen nach" (You run, we run after you) is not courtship — it is a chase, and the sender is the one doing the chasing. Nothing is confessed here, because the narrator sees no crime. He describes the operation in the Neue Deutsche Härte register of Rammstein — deadpan, imperative, untroubled — and the genre fits, because that is how a program which believes it owns your attention sounds.
The target is a common belief: that an opt-in is a possession. One tick box, and the brand behaves as though it has acquired a person — unlimited frequency, no obligation to be relevant, and an exit that exists but is not advertised. The narrator never lies, never breaks in, and never pretends to be confused. He knows the customer only wanted the shoes; he says so, and takes the single yes as a title deed anyway, because the numbers require it. That is the satire: real programs do this while calling it permission-based marketing, and this one says it out loud. Nothing in the song describes an illegal operation or a purchased list. Every send is permission-based on paper, and the program is still destroying itself.
An opt-in is a scope — granted conditionally, revocable at any moment, describing a kind of mail and a rate of it. Here is how the narrator converts one into the other, line by line.
Verse 1: Incentivised Consent at Checkout
"Zehn Prozent auf Laufschuhe / Ein Häkchen vor dem Kauf"
(Ten percent off running shoes / A checkbox before the purchase)
- The Deliverability Context: The relationship begins with a discount traded for a tick box during a transaction — the weakest form of permission in circulation. The subscriber is mid-purchase, focused on the cart, and the consent is bundled with something they actually want. The GDPR requires consent to be freely given, specific, informed and unambiguous (Art. 4(11)), and the request for it to be clearly distinguishable from the rest of the transaction (Art. 7(2)). A box beside the payment button rarely clears that bar in spirit, even when it clears it on paper.
- The German Angle: German law offers a narrow route for exactly this situation. UWG § 7 Abs. 3 permits email marketing to an existing customer without explicit opt-in — but only for similar goods or services, only while the customer has not objected, and only if the right to object was pointed out at collection and again in every single message. The song's sender inherits the route and honours none of the conditions.
- The Fix: Ask for marketing consent in its own step, with the frequency and the content type stated in the label, and keep a record of the wording shown. A subscription bought with ten percent off tends to expire, in practice, the moment the shoes arrive.
Pre-Chorus: Consent Has a Scope, Not Just a Value
"Du sagtest Ja / Nicht wann, nicht wie oft / Wir geben jetzt / Den Takt vor"
(You said yes / Not when, not how often / We set the pace now)
- The Deliverability Context: This is the thesis of the record, stated by the narrator himself: the subscriber agreed to the what, and the brand helped itself to the when and the how often. "Wir geben jetzt den Takt vor" (We set the pace now) is not an oversight being revealed — it is a seizure being announced. Senders treat consent as a boolean; mailbox providers evaluate behaviour. Gmail and Yahoo never see the checkbox. They see complaint rate, unsubscribe rate and engagement, which are the closest available proxy for whether this volume of mail was wanted. A subscriber who agreed to order updates and receives daily promotions reports it as spam, and that report counts exactly the same as one from a scraped address.
- The Fix: Put the frequency in the opt-in and honour it. Additional volume is earned through a preference centre, not assumed because the quarter is short.
Verse 2: Data Is Not Relevance
"Wir kennen deine Schuhgröße / Nicht, wohin du gehen willst"
(We know your shoe size / Not where you want to go)
- The Deliverability Context: The sharpest line in the song, precisely because the narrator is not deluded: he states the gap between data and intent accurately, then keeps sending. Real programs make the same error unknowingly — they hold size, purchase history and browsing data, and mistake the profile for understanding. Personalisation tokens stitched onto a broadcast ("Für dich gemacht" — Made for you) do not make a send relevant; they make an irrelevant send feel invasive. Someone who has just bought running shoes is, for a while, the least likely person on the list to buy running shoes.
- The Fix: Segment on behaviour and lifecycle stage rather than stored fields. After a purchase the useful sends are order status, care instructions and genuine complements — socks, insoles — timed to the product's replacement cycle rather than the promo calendar.
Verse 2: Frequency Without a Cap
"Die Woche hat sieben Tage / Wir fanden Platz für acht"
(The week has seven days / We found room for eight)
- The Deliverability Context: Eight sends in a seven-day week is the song's black joke, and it is the mechanism by which a permissioned list turns toxic. Over-mailing rarely produces a dramatic block; it produces a slow bleed of complaints. Gmail's bulk sender requirements cap the user-reported spam rate at 0.30%, with 0.10% as the level to stay under, and that rate is reported back to senders in Postmaster Tools. Eight exposures a week multiply a complaint probability that would be harmless at one.
- The Fix: Enforce a per-recipient frequency cap at program level, above individual campaign owners, so that no single team can spend the shared reputation budget.
Chorus: Silence Is an Answer
"DU SCHWEIGST / WIR SIND NOCH DA ... EINMAL JA / IMMER WIR"
(You go silent / We are still here ... One yes / Always us)
- The Deliverability Context: The narrator does not misread the silence — "Wir sind noch da" (We are still here) is addressed to someone he knows has stopped answering. He treats the silence as irrelevant, which is worse than misreading it. Gmail weighs per-recipient engagement heavily: mail that is never opened and never clicked gradually stops reaching that recipient's inbox, and a large silent cohort drags placement down for the engaged remainder of the list.
- A Note on Measurement: Do not settle this argument with open rate. Apple's Mail Privacy Protection pre-fetches images for the users who enabled it, which inflates opens enough that a silent subscriber can look active indefinitely. Clicks, purchases, site sessions and replies are the signals that survive.
- A Correction on Spam Traps: A silent subscriber is not automatically a spam trap. Recycled traps are made from addresses the provider has deactivated, and those addresses reject mail for a period before they are turned into traps — so the danger in a year of mailing someone who stopped reading is not the silence itself, but continuing to send after the address begins to bounce.
- The Fix: A sunset policy. Flag inactivity at 90–120 days with no click or purchase, run one short re-engagement sequence, and suppress everyone who does not respond. "Einmal Ja, immer wir" (One yes, always us) is not a permission model; it is a countdown.
Bridge: The Unsubscribe Link That Hides
"Der Link steht unten / Du findest ihn schon / Bis du ihn drückst / Laufen wir"
(The link is down at the bottom / You'll find it eventually / Until you press it / We keep running)
- The Deliverability Context: The narrator is technically compliant and behaving terribly, and he knows the difference — "du findest ihn schon" (you'll find it eventually) is a wager, not an oversight. The link exists, buried where friction does the work for him. Every unsubscribe a sender makes difficult comes back as a spam complaint instead, and the exchange rate is terrible: an unsubscribe costs one address, a complaint costs reputation across the whole list. Since February 2024, bulk senders to Gmail and Yahoo must also support one-click unsubscribe per RFC 8058 (
List-Unsubscribe plus List-Unsubscribe-Post: List-Unsubscribe=One-Click) and process the request within two days. The GDPR requires withdrawal of consent to be as easy as giving it (Art. 7(3)); in the US, CAN-SPAM allows ten business days and forbids making the opt-out conditional on paying a fee or handing over anything beyond an email address.
- The Fix: Ship the RFC 8058 headers on every marketing message, keep the visible link legible in the footer, never route it through a login wall or a multi-step survey, and suppress on receipt rather than on the next list sync.
Outro: The Whole Record in Two Lines
"Du sagtest Ja. / Wir hörten: immer."
(You said yes. / We heard: forever.)
The mishearing is deliberate, and the narrator reports it with satisfaction. That is the only place the satire departs from reality: in the song the program announces what it did, while in production this failure mode announces nothing. No bounce spike, no
blocklist entry, no incident to escalate — just a program that took one yes as ownership and kept running until the engaged part of the list quietly stopped seeing the mail.
Opt-in is not possession. It is not a free pass to push whatever the forecast requires, at whatever rate closes the gap, to whoever has not yet found the link at the bottom. It is a claim about what one person currently wants, granted on terms, revocable without explanation, and it expires on its own whether or not the sender chooses to notice.
The narrator of the song owns what he is doing. Real programs arrive at the same behaviour without anyone ever deciding on it, which is why the song has to put the words in someone's mouth. It happens incrementally, and every step is signed off by someone reasonable: a checkbox gets added to checkout because it converts, a second weekly send gets approved because the quarter is behind, an unsubscribe link gets moved below the fold because it was "too prominent". Each decision is defensible alone. Together they produce a program that mails eight times a week to people who stopped reading a year ago, and files the whole thing under permission-based marketing.
The correction is one idea applied consistently: an opt-in is borrowed attention with terms attached, not an asset the brand now owns.
Collect Consent With a Scope Attached
A subscription record that stores only true is not documentation. It cannot tell you what you are allowed to send.
- Unbundle the opt-in from the transaction. Marketing consent asked for beside the payment button is consent to finish buying. Give it its own step and its own wording, clearly distinguishable from the rest of the form as the GDPR requires.
- State frequency and content type in the label. "Weekly new arrivals" is a scope. "Yes, keep me updated" is a blank cheque that subscribers revoke as a spam complaint.
- Record what was shown. Timestamp, source and the exact consent text. If you cannot reproduce what someone agreed to, you cannot show that it covers what you are sending now.
- Know which legal basis you are using. Explicit opt-in and the existing-customer route (UWG § 7 Abs. 3 in Germany, the ePrivacy soft opt-in elsewhere in the EU, the opt-out regime under CAN-SPAM in the US) carry different obligations. The customer route is limited to similar products and requires an objection notice in every message.
Cap Frequency at the Program Level
Cadence tends to be set by whoever shouts loudest internally, and it is spent from a shared reputation budget.
- Enforce a global per-recipient cap above individual campaign owners. Caps applied per campaign are not caps.
- Count exposure, not sends. Before adding a send, work out the monthly total your most-targeted segment will receive — that number, not the campaign count, is what produces complaints.
- Offer a real preference centre with frequency and topic options. A subscriber who chooses "monthly" is worth more than one retained by hiding the exit.
- Treat complaint rate as the leading indicator. Gmail's ceiling is 0.30% with 0.10% as the working target. Rising complaints usually mean too much mail before they mean bad content.
Segment on Intent, Not on Attributes
Knowing a customer's size is not knowing what they want, and personalisation tokens on a broadcast make an irrelevant message feel worse rather than better.
- Use lifecycle stage as the primary axis. Someone who bought yesterday needs order status and care content; someone who bought eleven months ago may genuinely need a replacement. The same promotion serves neither.
- Trigger on behaviour. Browse abandonment, replenishment intervals and category interest produce mail that arrives because the subscriber did something.
- Suppress the obvious mismatch. Excluding recent purchasers from promotions on the item they just bought costs nothing and removes a reliable source of annoyance.
Let Silence End the Relationship
Non-response is not consent that survived. It is consent that expired without anyone recording it.
- Define inactivity with signals that survive privacy features. Clicks, purchases, site sessions and replies. Mail Privacy Protection inflates opens enough that an open-based definition keeps dead addresses alive indefinitely.
- Set the window at 90–120 days. Flag, run one short re-engagement sequence with a clear "stay subscribed" action, then suppress. Do not run the sequence twice.
- Suppress rather than delete, so the address stays on a permanent do-not-mail list and cannot be re-imported by a future campaign.
- Act on bounces immediately. An address that starts rejecting mail has been abandoned, and providers turn some abandoned addresses into recycled spam traps. Continuing to send after the first hard bounce is what converts a silent subscriber into a blocklist problem.
Make Leaving Easier Than Complaining
Every unsubscribe you make difficult returns as a spam complaint, and the exchange rate is terrible.
- Implement one-click unsubscribe per RFC 8058.
List-Unsubscribe with an HTTPS endpoint and List-Unsubscribe-Post: List-Unsubscribe=One-Click, on every marketing message. Required by Gmail and Yahoo for bulk senders since February 2024.
- Process within two days, which is the mailbox provider requirement and far shorter than the ten business days CAN-SPAM allows.
- Never gate the opt-out behind a login, a survey or a form with required fields. Under the GDPR, withdrawal must be as easy as consent was to give.
- Keep the visible link legible. Readable size and real contrast, in the footer where people look for it. A hidden link does not retain a subscriber; it converts them into a reputation problem.
Conclusion
The sender in this song never buys a list, never forges a header and never sends a message that would fail authentication. It fails anyway, because it treats a single yes as permanent and a silent subscriber as a subscriber. Permission describes what someone wants right now, and it decays — the only question is whether you retire it deliberately or wait for the complaint rate to retire it for you.
Your Consent Scope Checklist:
- Move the marketing opt-in out of the checkout flow, with frequency and content type stated in the label.
- Record the timestamp, source and exact consent text, and know which legal basis each subscriber sits under.
- Enforce a per-recipient frequency cap that individual campaign teams cannot override.
- Exclude recent purchasers from promotions on what they just bought, and trigger on behaviour rather than stored attributes.
- Define engagement by clicks, purchases and site activity — never by opens alone.
- Flag inactivity at 90–120 days, run one re-engagement attempt, then suppress permanently.
- Suppress hard bounces on the first rejection, before an abandoned address becomes a recycled trap.
- Ship RFC 8058 one-click unsubscribe headers on every marketing send, honour requests within two days, and keep the visible link unconditional.
Educational content. Email deliverability evolves rapidly. Platform rules (Gmail, Yahoo, etc.), engagement signals, and ESP behaviours change frequently, and real-world issues often involve conflicting signals, data quality problems, and failure modes that general best practices can’t anticipate. Content on this site is provided for informational purposes only and does not replace a thorough analysis by a qualified deliverability professional.
Terms of Use