Latest / Marketing Automation with Fexingo: HubSpot, Marketo, and Automated Customer Journeys / Why Marketing Automation Ignores Customer Newsletter Unsubscribes
Transcript
- Lucas: So you unsubscribe from a brand's newsletter — click the link, confirm, all good. But then three days later, you get another email from the same brand, same list, same offer. And then a text message. Luna: It's infuriating. And it happens way more than it should. Lucas: According to a 2025 Data & Marketing Association study, 42% of marketers still don't sync unsubscribe data across email, SMS, and push channels within 24 hours. That's nearly half. Luna: So the customer says 'stop' and the system just doesn't listen. That's not just annoying — that's a compliance risk, right? Lucas: Exactly. Under GDPR, you're supposed to honor an opt-out without undue delay. In the U.S., can spam requires you to honor unsubscribe requests within ten business days. But if your automation tools aren't talking to each other, you could be violating that. Luna: And it's not just legal. It's a trust killer. I unsubscribe because your emails aren't relevant, and then you prove me right by sending more. Lucas: Right. Now, the interesting part is why this happens. It's usually not malice. It's technical debt. Companies have separate systems — one for email, one for SMS, one for push notifications — and the customer data platform doesn't sync in real time. Luna: So the database says 'unsubscribed' in the email tool, but the SMS tool never got the memo. Lucas: Exactly. And the marketing automation platform, whether it's HubSpot, Marketo, or something custom, triggers a journey based on a behavior — say, someone who bought a product six months ago and hasn't opened an email since. That journey might include a text message offer, and the system checks the email suppression list but not the SMS suppression list. Luna: Because they're different lists. Different tables, different fields. Lucas: Bingo. Now, there's a solution that a lot of teams overlook. Instead of treating an unsubscribe as a dead end, treat it as a data point. You can create a trigger in your automation: when a customer unsubscribes from any channel, suppress them across all channels immediately. Luna: That sounds simple, but I bet the implementation gets messy. Lucas: It does, because you need a unified customer profile. But here's the thing — modern platforms can do it if you configure the right webhook or API call. HubSpot has an 'opt-out' property that you can sync with custom code. Marketo has a 'global unsubscribe' field that can be updated via API. Luna: So the issue is more about process than technology. Teams don't prioritize the integration. Lucas: Correct. And there's a cost to that. I spoke with a mid-sized retailer last quarter — they were seeing about 12% of their email list unsubscribe every year, but 4% of those people were still getting SMS messages for weeks after. Their complaint rate went up, and they actually got flagged by their SMS provider. Luna: That's a reputation hit with the carrier, not just the customer. Lucas: Exactly. They fixed it by building a simple middleware script that checked the unsubscribe timestamp in their email tool before sending any SMS. Within three months, their spam complaints dropped 38%. Luna: So honoring an unsubscribe actually improved deliverability for the people who did want to hear from them. Lucas: That's the counterintuitive part. By removing the people who don't want your messages, your engagement metrics go up, your sender reputation improves, and your automation becomes more efficient. Luna: Let's talk about the unsubscribe itself — the moment someone clicks that link. Most brands just delete the email address or mark it inactive. But some are using that moment to ask why. Lucas: Yeah, the 'why are you leaving' survey. But you have to be careful. If you ask for feedback before confirming the unsubscribe, that's a dark pattern. You have to confirm first, then ask. Luna: And even then, what do you do with that data? If someone says 'too many emails', do you reduce frequency instead of removing them? Lucas: Some brands do offer a 'frequency reduction' option. That's a legitimate preference center feature. But if someone explicitly unsubscribes, you should honor that. Don't try to re-engage them with a different message unless they've opted back in. Luna: I've seen brands that unsubscribed me from one list but kept me on three others because they were technically separate. Lucas: That's the classic 'unsubscribe from this list only' pattern. It's legal under can spam as long as you identify the list, but it's terrible for customer experience. The better approach is a global unsubscribe that covers all marketing communications. Luna: And then there's the automation trigger itself. If a customer unsubscribes, should that end all ongoing journeys? Or just future ones? Lucas: It should end active journeys too. If someone is in a 5-email onboarding sequence and they unsubscribe after email 2, you shouldn't send emails 3, 4, and 5. The automation should check suppression lists at every step, not just at entry. Luna: That's a common mistake — journeys that don't recheck eligibility before each send. Lucas: Right. And it's easy to fix. Most platforms have a 're-evaluate eligibility' setting. Turn it on. It takes five minutes and saves you from sending unwanted messages. Luna: Let me bring up a specific example. A financial services company I know had a triggered email for customers who left a loan application incomplete. If someone unsubscribed from marketing, they still got that email because it was classified as 'transactional'. Lucas: Transactional messages are exempt from can spam, but you need to be honest about what counts as transactional. An abandoned loan application reminder could be considered service-related. But a promotional offer on a new credit card is not. Luna: They blurred the line. And customers complained. Lucas: So the lesson is: have a clear policy on what's transactional and what's marketing, and make sure your automation respects that boundary. If someone unsubscribes from marketing, don't use a transactional loophole to keep sending offers. Luna: It's about respecting the intent behind the click. Lucas: Exactly. Now, there's one more layer. Many companies use machine learning to predict churn. They look at email opens, clicks, website visits. But an unsubscribe is a much stronger signal than any of those. Luna: It's a direct statement of intent. Not a probabilistic guess. Lucas: Right. So if your model sees an unsubscribe, it should increase the churn probability to near 100% — at least for that channel. And it should trigger a review of the customer's overall engagement. Luna: But we haven't talked about the positive side. Can an unsubscribe ever be good for the relationship? Lucas: Sure. If someone unsubscribes from a weekly newsletter but stays subscribed to transactional messages, that's healthy. They're telling you what they want. And if you honor that, you might keep them as a customer longer. Luna: So the key is listening to the signal, not ignoring it. Lucas: Precisely. And that brings us back to the automation. If these conversations have sparked something you've actually used in your own marketing, or if you're thinking about cleaning up your suppression logic, honestly, if today was worth a coffee to you, that's the link: buy me a coffee dot com slash fexingo. Luna: Yeah, it helps us keep this show ad-free and focused on practical stuff like this. Lucas: So back to that unsubscribe trigger — the next time you set up a journey, ask yourself: what happens when the customer says no? If you don't have an answer, you've got a blind spot. Luna: And that blind spot is costing you trust, compliance, and maybe even your sender reputation. Lucas: It's a small fix — a few lines of code, a checkbox in your platform — but it makes a huge difference in how your customers feel about your brand. Luna: And how your automation performs. Lucas: Next time, we'll look at another ignored signal: what happens when customers stop engaging but don't unsubscribe. The silent churn. Thanks for listening.