Latest / Marketing Automation with Fexingo: HubSpot, Marketo, and Automated Customer Journeys / How Marketing Automation Misses Customer Life Events
Transcript
- Lucas: You know what I've been thinking about a lot lately? Customer life events. Not the small stuff like browsing a category — I mean the big ones. Marriage, new baby, job change, retirement. The moments that completely reshape someone's financial picture, their spending patterns, their priorities. Luna: And yet most marketing automation systems treat those people like they're the same person they were the day before. I've seen it happen in my own inbox — I got a 'welcome to our family plan' email from my insurance company two years after my daughter was born. Lucas: Exactly. And that's not just a minor annoyance — it's a revenue leak. I was looking at a case from a national insurance carrier. They had a customer who'd been with them for twelve years, always paid on time, never filed a claim. But they had no idea that customer had retired six months ago. So they kept sending him 'job-based' product offers and discounts for group plans that no longer applied. Luna: Oof. And what happened? Did he churn? Lucas: He did. He switched to a competitor that sent him a single postcard: 'We see you're retired — here's a policy that fits your new lifestyle.' That one message was worth about three thousand dollars in lifetime value. And the original carrier had all the data they needed to figure it out — they just weren't using it. Luna: So what's the blocker? Is it a data problem, a process problem, or a technology problem? Lucas: All three, honestly. But the biggest one I see is that most marketing automation platforms — whether it's HubSpot, Marketo, or a homegrown tool — are built to react to actions the user takes on your owned properties. Someone fills out a form, clicks a link, opens an email. But life events rarely happen inside your ecosystem. They happen in the real world, or in other data systems. Luna: Right. So you have to pull that data in from somewhere else. Credit bureaus, property records, maybe even social media signals if you're sophisticated. But that's expensive and messy. Lucas: It is. But let's talk about a simpler fix that many companies leave on the table: the proactive survey. I'm not talking about a generic 'how are we doing' survey. I mean a targeted, low-friction check-in triggered by time or behavior. For example, if someone has been a customer for five years and hasn't updated their profile, send them a quick two-question email: 'Has your job changed? Has your family size changed?' Luna: Does that actually work? I've always heard that response rates on those things are abysmal. Lucas: Depends on the timing. One company I worked with tested sending that survey six months after the typical life event window — so for a new parent, they'd send it about eighteen months after the birth, when the customer is out of the newborn fog and might actually respond. They got a twenty percent response rate, and fifteen percent of those respondents updated their profile. That's not huge, but it's a lot better than zero. Luna: Wow. So it's about finding the moment when the customer is ready to engage, not just when you want to ask. Lucas: Exactly. Another approach is to use transactional data as a proxy. For example, if a customer who always bought pet food suddenly stops for three months, that could signal a pet loss — which is a life event. You could trigger a sensitive, helpful email, maybe with a charitable donation option. That builds loyalty even if it doesn't drive an immediate sale. Luna: That's smart. But I'm thinking about the technology side. Most marketing automation platforms have these 'lifecycle stage' fields — Lead, MQL, SQL, Customer. But they don't have a 'life event' field. Should they? Lucas: I think they should. And some are starting to. But the real issue is that those fields have to be populated, and most integrations are one-directional. The CRM might know about a job change from a LinkedIn integration, but that data never flows into the marketing automation system. Or it flows in as a generic 'field update' that doesn't trigger a journey. Luna: So the fix is partly technical and partly about mapping out those event-based journeys in advance. You have to decide: when we learn that someone got married, what happens next? Lucas: Right. And that's where the automation platform shines — if you've done the work. Imagine a trigger: 'Contact field LifeEvent changes to Married.' Then send a congratulatory email, offer a joint account product, and move them into a wedding registry nurture track. All automatically. But the trigger only works if the data reaches the platform. Luna: So what's the first step for a company that wants to start capturing life events? I imagine most of them don't have a data science team building predictive models. Lucas: Start with the low-hanging fruit. Look at your existing customer data — do you have a 'date of birth' field? If you do, you can trigger a birthday email. That's a life event, even if it's a small one. Then expand to things like policy renewal dates, which often correlate with life changes. And then add one proactive survey per year. Just one. Don't overwhelm them. Luna: And I'd add: make sure the survey is actually useful to the customer. Tell them why you're asking. Like, 'We want to make sure your coverage fits your life. Has anything changed?' That's respectful, not creepy. Lucas: Totally. And if they answer, use that data immediately. Send a tailored recommendation within 24 hours. If they say they had a baby, don't wait a week to offer a family plan. Strike while the life event is top of mind. Luna: One thing I wonder about: privacy. Some people might not want to share life events with a brand. How do you handle that? Lucas: You have to earn the right to ask. If you've been sending useful content for years, the relationship is there. But also, you need to make it clear that sharing is optional and that you'll respect their preference. And never, ever use inferred life events in a way that feels invasive — like targeting someone with divorce-related products based on a change in address. That's a fast track to bad PR. Luna: Right. So the playbook is: gather what you can ethically, ask respectfully, and act immediately. That's the core of a life event driven marketing automation strategy. Lucas: And if you do it right, you not only retain customers — you deepen the relationship. Because you're showing that you see them as a person, not just a profile. Which brings me to a quick thought — if these kinds of marketing conversations have sparked something you've actually used or adapted, and you've found value in keeping this show ad-free and focused on practical ideas, listeners have a way to support that directly. Luna: Yeah. It's just at buy me a coffee dot com slash fexingo. No pressure, no perks — just a way to keep the lights on and the episodes coming. And if you're not in a position to do that, honestly, just sharing an episode with a colleague helps more than you'd think. Lucas: Exactly. Now back to life events — I want to talk about one more angle. The predictive side. Some companies are using machine learning to predict life events before they happen. For example, a change in spending patterns might indicate a baby is on the way — buying baby gear from retailers. Or an uptick in real estate searches could mean a move is coming. Luna: That's powerful but also a minefield. If you get it wrong, you could send a baby welcome kit to someone who isn't expecting. Or worse, to someone who had a loss. Lucas: That's the risk. So the smart play is to use predictive signals not as triggers, but as timing indicators. You don't send the baby offer based on the purchase of baby wipes. You wait until you have a more reliable signal — like a birth announcement on social media or a change in insurance coverage. The prediction tells you when to ask, not what to assume. Luna: That's a good rule. 'Predict to time, not to assume.' I'm going to steal that. Lucas: Please do. So in practice, that means building a model that scores each customer on the likelihood of a life event happening in the next 90 days. Then you use that score to prioritize which customers get the proactive survey. You're not triggering a journey; you're just deciding who to ask first. Luna: That keeps the human in the loop. The customer still has to confirm the event. That feels respectful. Lucas: It does. And it's also more effective — because the customer who confirms is more likely to engage with the follow-up. They've opted into the conversation. Luna: So for a company that's just starting out, what's the one metric they should track to see if they're improving? Lucas: I'd say 'life event capture rate' — the percentage of customers for whom you have a confirmed recent life event on file. Start by measuring it today. Then set a goal to increase it by five percent over the next quarter. Even small moves — like adding a field on the checkout page that says 'Is this for a new baby?' — can move that needle. Luna: And that ties directly to revenue. Because if you know about a life event, you can serve the right product at the right time. That's marketing automation at its best. Lucas: Exactly. It's not about blasting more emails. It's about being relevant in the moments that matter.