Newsletter strategist Dylan Redekop recently wrote about the "context box," his term for the line in a marketing or newsletter email explaining why you are receiving a particular message. (By the way, I think he coined something useful here, so I'm totally going to steal that.)
If you're not familiar, it's that bit of text that an email sender often includes, looking something like this: "You're receiving this because you signed up for the XYZ newsletter." "You're getting this email because you've made a purchase on the ABC website."
The intent behind the context box is a noble one: stave off spam complaints. By reminding recipients how they ended up on your list, you stop them from hitting the "This is Spam" button out of confusion or amnesia. Since negative votes damage your sending reputation and can get you voted off of inbox island and into the swamp of the spam folder, showing this as a proof of permission feels like good deliverability insurance. Dylan's pro-context box, and I generally am, too.
But, even before I saw his post, I already had a bit of a rant brewing. Because too many senders are doing this badly.
Case in point: I recently received an email with a blanket, cover-your-ass context box that read: "You're receiving this email because you signed up online, made a donation, attended an event, or received care from us." I'm not big on name-and-shame, so I'm not outing the sender.
But I will say that what this sender did here is lazy and unhelpful. It tells me nothing about my actual connection to them and basically expects me to do the detective work. Worse, throwing every possible opt-in path into a single disclaimer signals that the sender doesn't actually know where their data came from, and sometimes exposes to the world that some of your permission practices might not be all that great. (And ultimately, I don't think they were, in my case. I never checked a box to opt-in to this.)
If you're going to use a context box, it needs to serve the recipient, not just your legal team. If you can't do it with good, explicit data, don't do it at all.
Before adding one to your template, make sure it checks these five boxes:
Be Specific. Don't list fifteen generic opt-in routes. Show (only) the actual source that applies to that specific recipient. Don't hand them a phone book and tell them to figure it out.
Be Accurate. If your context box doesn't match reality, recipients will assume you lied or bought their data. Your spam complaint rate will go up, not down.
Be Permission-Based. Reminding a recipient that you bought their address in a "totally legal way" will absolutely not make recipients love you. Legally compliant spam is still spam to the person hitting the report button, which they can do, completely legally, even if your email broke no laws.
Be Verified. If you don't use double opt-in (DOI), remember that sign-up forms get forged, pranked, and mail-bombed. Telling an angry recipient "You signed up on our site" when a bot or an enemy did it for them only fuels the fire.
Be Useful. The goal is to jog the recipient's memory simply, easily. If the source information is cryptic or generic, it offers zero value, and zero protection for your inbox placement.
A good context box uses accurate and explicit data to build trust. A bad context box is just visual noise that exposes lazy data management. If you can't make it specific and accurate, skip the disclaimer entirely and focus on sending content people actually remember signing up for.
Newsletter strategist Dylan Redekop recently wrote about the "context box," his term for the line in a marketing or newsletter email explaining why you are receiving a particular message. (By the way, I think he coined something useful here, so I'm totally going to steal that.)
If you're not familiar, it's that bit of text that an email sender often includes, looking something like this: "You're receiving this because you signed up for the XYZ newsletter." "You're getting this email because you've made a purchase on the ABC website."
The intent behind the context box is a noble one: stave off spam complaints. By reminding recipients how they ended up on your list, you stop them from hitting the "This is Spam" button out of confusion or amnesia. Since negative votes damage your sending reputation and can get you voted off of inbox island and into the swamp of the spam folder, showing this as a proof of permission feels like good deliverability insurance. Dylan's pro-context box, and I generally am, too.
But, even before I saw his post, I already had a bit of a rant brewing. Because too many senders are doing this badly.
Case in point: I recently received an email with a blanket, cover-your-ass context box that read: "You're receiving this email because you signed up online, made a donation, attended an event, or received care from us." I'm not big on name-and-shame, so I'm not outing the sender.
But I will say that what this sender did here is lazy and unhelpful. It tells me nothing about my actual connection to them and basically expects me to do the detective work. Worse, throwing every possible opt-in path into a single disclaimer signals that the sender doesn't actually know where their data came from, and sometimes exposes to the world that some of your permission practices might not be all that great. (And ultimately, I don't think they were, in my case. I never checked a box to opt-in to this.)
If you're going to use a context box, it needs to serve the recipient, not just your legal team. If you can't do it with good, explicit data, don't do it at all.
Before adding one to your template, make sure it checks these five boxes:
- Be Specific. Don't list fifteen generic opt-in routes. Show (only) the actual source that applies to that specific recipient. Don't hand them a phone book and tell them to figure it out.
- Be Accurate. If your context box doesn't match reality, recipients will assume you lied or bought their data. Your spam complaint rate will go up, not down.
- Be Permission-Based. Reminding a recipient that you bought their address in a "totally legal way" will absolutely not make recipients love you. Legally compliant spam is still spam to the person hitting the report button, which they can do, completely legally, even if your email broke no laws.
- Be Verified. If you don't use double opt-in (DOI), remember that sign-up forms get forged, pranked, and mail-bombed. Telling an angry recipient "You signed up on our site" when a bot or an enemy did it for them only fuels the fire.
- Be Useful. The goal is to jog the recipient's memory simply, easily. If the source information is cryptic or generic, it offers zero value, and zero protection for your inbox placement.
A good context box uses accurate and explicit data to build trust. A bad context box is just visual noise that exposes lazy data management. If you can't make it specific and accurate, skip the disclaimer entirely and focus on sending content people actually remember signing up for.Comments
Post a Comment
Comments policy: Al is always right. Kidding, mostly. Be polite, please and thank you.