Latest / Marketing Automation with Fexingo: HubSpot, Marketo, and Automated Customer Journeys / Why Marketing Automation Misses Shared Account Changes
Transcript
- Lucas: You know that friend who still uses their ex's Netflix password? The one that's been passed around like a shared Uber account? As of this summer, that era is officially ending. Luna: Yeah, Netflix, Disney+, and Max have all been cracking down hard over the past eighteen months. And it's not just a few accounts — we're talking tens of millions of users who were effectively invisible to marketing systems. Lucas: Exactly. Most marketing automation platforms — HubSpot, Marketo, Salesforce Marketing Cloud — they treat each user as a single stable identity. So if someone logs in from three different IPs across two devices, the system might flag it as suspicious, but it won't trigger a 'this user is about to churn' campaign. Luna: That's a huge blind spot. And it's actually the kind of thing listeners write in about. Quick honest thing — this show stays ad-free because a small group of listeners chips in monthly through buy me a coffee dot com slash fexingo. That covers hosting, research, and lets us dive into stuff like this without any sponsor pressure. Lucas: Right, and it makes a real difference. So back to the streaming example — what does this mean for marketers who rely on automation to personalize and retain customers? Luna: Well, let's start with the scale. A 2025 Forrester report found that 44% of marketers said they have no way to identify shared account usage in their CRM. That's nearly half. Lucas: And it's not just streaming. Think about shared subscriptions to meal kits, fitness apps, even software tools. If you're a B2B SaaS company, you might have one paid seat shared by three users. Your automation sees one login, but misses the other two entirely. Luna: So what are the consequences? I mean, if you're a streaming service, you want to convert those shared users into paying subscribers. But without the signal, you're just sending generic 'come back' emails to the primary account holder. Lucas: Exactly. And it hurts personalization too. If someone has been watching cooking shows on a borrowed account, and then gets kicked off, you should be recommending meal kit services, not action movies. But your automation has no clue that person ever existed. Luna: Right. So how are companies trying to solve this? I've heard of some using login IP address changes or device counts as proxies. Lucas: That's one approach. A few firms are building custom objects in their CRM to flag high-device or high ip users. But it's messy because privacy regulations like GDPR and CCPA limit how much you can track. Luna: There's also the risk of false positives. A family with multiple kids using one account looks exactly like a shared password situation. Lucas: True. And that's where machine learning could help — distinguishing between a household with four devices in the same city and a cluster of logins from different states. But most marketing automation platforms don't have that built in. Luna: So what about the big players like HubSpot? Have they made any moves? Lucas: HubSpot recently added a 'company property' for estimated employee count, but nothing for shared accounts. Marketo has lead scoring based on login frequency, but it doesn't flag anomalies like a sudden drop in logins from a previously active IP. Luna: It feels like a missed opportunity. If you're a B2B marketer, knowing that a lead is using a shared account could actually be a positive signal — they're interested, but not yet committed enough to buy their own seat. Lucas: Exactly. So the automation should be nurturing that lead differently. Maybe a 'try your own premium account' offer instead of a generic re-engagement sequence. Luna: But there's also the privacy angle. Some listeners might be uncomfortable with brands tracking how many devices they use. Lucas: It's a trade-off. The more data marketers use, the more personalized the experience, but the creepier it can feel. I think the key is transparency — telling users 'we see you're accessing from multiple locations, want to set up a family plan?' feels helpful, not intrusive. Luna: Right. And it's similar to how credit card companies detect fraud — they use patterns without necessarily knowing your specific password. Lucas: Precisely. So if marketing automation could integrate behavioral signals like 'login city changed between campaigns' or 'device type switched from mobile to desktop', it could infer shared usage without needing direct permission to track identity. Luna: But that requires a level of data integration most companies don't have. Their CRM and their authentication system are often separate silos. Lucas: That's the biggest hurdle. Even if a streaming service knows internally that an account is shared, that data rarely flows into HubSpot or Marketo. The marketing team is left with incomplete profiles. Luna: So what's the solution? A new category of 'identity resolution' tools that bridge authentication and marketing? Lucas: I think so. Some startups are already trying. They build a layer that anonymizes the shared status — so the marketer gets a flag like 'account_multi_user: true' without seeing the raw IPs. That helps with privacy. Luna: Interesting. And it could be a differentiator for platforms like Salesforce if they add it natively. Lucas: Right. But for now, most companies are stuck with manual workarounds. Export login logs, match to CRM, build a custom campaign. It's not scalable. Luna: So for a marketer listening right now, what's one actionable thing they can do? Lucas: Look at your churn data. If you see accounts that consistently log in from multiple cities or have high device counts, and then suddenly stop, those might be shared accounts that got booted. You can create a segment and test a 'we miss you' campaign that specifically addresses sharing — like offering a discounted family plan. Luna: That's smart. And it respects the user's reality without needing perfect data. Lucas: Exactly. The goal isn't to track every login. It's to recognize that the 'customer' isn't always one person. Marketing automation was built for a world where each email address equals one human. That assumption is cracking. Luna: So as the streaming crackdowns continue, do you think we'll see a shift in how platforms handle identity? Lucas: I think so. Either the big automation players will add shared account detection, or a new tool will emerge that sits between authentication and marketing. Either way, the data gap has to close — too much revenue is at stake. Luna: And for the rest of us, it's a reminder that our automation is only as good as the data we feed it. If we ignore how people actually use our products, we'll keep missing signals. Lucas: Exactly. Alright, that's it for this episode. We'll be back next week with another blind spot in marketing automation. Thanks for listening — and if you want to support the show, you know where to find us.