Latest / Marketing Automation with Fexingo: HubSpot, Marketo, and Automated Customer Journeys / Why Marketing Automation Ignores Customer Life Insurance Events
Transcript
- Lucas: So a customer buys a life insurance policy. That is one of the most signal-rich events a person can generate in their financial life. And most marketing automation platforms treat it exactly like they would treat a purchase of a blender. Luna: Wait — a blender? You're comparing a life insurance policy to a kitchen appliance? Lucas: I am, and it's not even hyperbole. I talked to a data analyst at a mid-size insurer a few weeks ago. Their marketing cloud had a workflow tied to 'new policy purchase.' The trigger fired, the customer got a confirmation email, and then — because the product category was 'insurance' — the system started pushing home security offers. For six months. Luna: Home security? That's at least loosely related to protecting your home. But it's still a leap. Lucas: The customer was a 34-year-old single renter in a downtown apartment. The home security offers made no sense. What actually happened is that the person had just bought a term life policy after getting married and buying a house. The insurance purchase was the tail of a much bigger story. The marketing automation saw the policy, but it missed the marriage and the home purchase. Luna: So the problem is that the automation sees a product event, not a life event. It sees 'policy effective date' instead of 'new homeowner + newlywed = dependent spouse.' Lucas: Exactly. And the frustrating part is that the data exists. Credit bureaus, property records, even the life insurance application itself — it asks about marital status, dependents, mortgage amount. That information is collected. But it rarely flows into the marketing automation platform. It gets stored in the underwriting system and never talks to the CRM. Luna: That's a classic data silo problem. But is it really that simple? I mean, there are privacy reasons you might not want underwriting data feeding marketing workflows. Lucas: That's the pushback I always hear, and it's legitimate. But let's be precise about what the regulations actually say. GDPR and CCPA give consumers rights over data collection and usage. They don't automatically prohibit using data you already have — as long as you have a lawful basis and the consumer hasn't opted out. The issue is more that companies are scared to build the bridge. Luna: Or they don't know how to build it without triggering compliance alarms. I've seen marketing teams just blanket-decline any request to connect underwriting data to the marketing cloud because they don't want to have to document the use case. Lucas: Right. And the result is that the customer who just bought a life insurance policy gets treated as someone who is 'in-market for protection products' rather than someone who just bought a house and had a baby. Luna: Okay, so give me a concrete example of what a smarter workflow would look like. Let's say you do connect the data. What's the trigger and what's the action? Lucas: Let's use a specific hypothetical. Customer named Sarah, age 32. She applies for a 20-year term life policy with a death benefit of $500,000. The underwriting system captures that she listed a new address, a marital status change to 'married,' and a dependent child age 1. The policy is issued. Now instead of sending a generic 'welcome to the family' email, the marketing automation should recognise a bundle of life events: new home, new marriage, new parent. The appropriate action might be an invitation to review umbrella liability coverage, or a guide to estate planning for young families. Not a home security ad. Luna: But that requires the marketing platform to understand that a life insurance policy is a proxy for several other events. The system typically doesn't 'read' application fields — it just sees a policy record. Lucas: That's the technical crux. Most marketing automation platforms are designed around product-object triggers, not event-bundle triggers. A workflow fires when a deal stage changes in the CRM, or when a form is submitted. But a life insurance policy is not just one thing — it's a cluster of signals. To catch it, you'd need a custom object that represents the life event, and then have the policy creation trigger an update to that object. Luna: Which is architecturally possible. I've seen HubSpot custom objects used for exactly this kind of thing. But it requires someone to design the data model and map the fields. Most marketing teams don't even know the underwriting fields exist. Lucas: And that's the gap. The data exists. The platform can handle it. But the organizational silo between actuarial and marketing is so deep that no one builds the bridge. Luna: So what's the consequence for the customer? Besides getting irrelevant ads. Lucas: The consequence is that the brand looks like it doesn't understand you. You just entrusted them with the financial security of your family, and they send you a push notification about a toaster. It erodes trust. And in insurance, trust is the product. Luna: That's a good line. And it makes me wonder — are there any insurers that get this right? Or is it all still pretty broken? Lucas: A few are trying. I've seen some early experiments using CDPs — customer data platforms — to stitch together policy data with external life event signals like property records or birth announcements. But it's early. Most are still in the 'we know we should do this' phase. Luna: Speaking of things that are worth doing — if this episode made you think about your own marketing workflows, or if it just made you nod along, that's the kind of thing that keeps the lights on around here. If it was worth a coffee to you, there's a link — buy me a coffee dot com slash fexingo. No pressure, just if it landed. Lucas: Yeah, honestly, listener support is the reason we can keep doing these deep dives without sponsors. So thanks for that. Luna: Anyway — back to the insurance gap. Lucas, you mentioned credit health data earlier. How does that fit in? Lucas: Credit health is another layer. A life insurance policy often triggers a credit pull during underwriting. That credit report contains a ton of life event data: new credit lines for home purchases, changes in available credit, new addresses. All of that could feed a marketing automation system to infer a life event. But again, it's almost never used that way. Luna: Because of regulatory fear, or technical inertia? Lucas: Both. But also because the marketing team doesn't know the credit data exists, and the legal team doesn't want to know. It's easier to just not connect the dots. Luna: So the recommendation for a marketer listening today would be: go talk to your underwriting team. Find out what data they collect at application. Ask if you can get a feed of life-event signals — not the health details, just the event triggers like new address, new dependent, new marital status. Lucas: Exactly. Start with a narrow use case. Maybe just the new homeowner trigger. Build a workflow that sends a relevant offer — like a home inventory app or a recommendation to update beneficiaries. Measure whether engagement rates go up. Then expand. Luna: What's the biggest barrier you think? The data, the culture, or the technology? Lucas: Culture, by far. The technology exists. Data can be connected. But marketing and underwriting operate in completely different worlds. Underwriting thinks about risk. Marketing thinks about revenue. They don't speak the same language, and there's no incentive to learn. Luna: So the fix is organizational, not technical. That's actually encouraging — because you can change org charts a lot faster than you can rebuild a data warehouse. Lucas: Right. And the payoff is huge. You get a customer who feels seen. That's the holy grail of marketing automation — making the customer feel like you actually know them.