Latest / Marketing Automation with Fexingo: HubSpot, Marketo, and Automated Customer Journeys / Marketing Automation Fails Customer New Addresses
Transcript
- Lucas: So you move to a new city. You update your address with your bank, your insurance, maybe your Amazon account. But the grocery store you've shopped at for three years — they still think you live in your old zip code. Luna: And they keep sending you coupons for a store that's now two hundred miles away. I've been on the receiving end of that. Lucas: Right. It's a surprisingly common failure in marketing automation. Most platforms are great at triggering based on a purchase or a click, but they completely miss life events like a change of address. And that's a real retention risk. Luna: How big of a risk are we talking? Do you have a number? Lucas: I looked at a regional grocery chain — let's call it FreshMart — that had about 150 stores across the Midwest. They were losing customers after moves at a rate of about 12 percent within 90 days of the move. That's people who had been loyal shoppers for years, and then they just fell off because the marketing ignored the fact that they'd relocated. Luna: And the fix sounds simple: just trigger a welcome email with the nearest store location, right? Lucas: It sounds simple, but the data is often locked up. The address change typically goes to the billing system — the payment side of the house. That data rarely flows into the marketing automation platform like HubSpot or Marketo. So the marketing database still has the old address. Luna: So it's a data integration problem more than a workflow design problem. Lucas: Exactly. And the fix involves syncing the billing system with the CRM. But there are also third-party data providers that track moves — like the National Change of Address database from the USPS. You can pull that data monthly and update your records. Luna: But isn't that still a batch process? You're not catching the move in real time. Lucas: That's the trade-off. Real-time would require a direct API from the billing system to the marketing platform. A lot of companies don't have that integration because the billing team and the marketing team don't talk to each other. So the best interim solution is a weekly or monthly batch update, and then trigger a re-engagement sequence for anyone whose address changed. Luna: I want to dig into what that sequence looks like. But first — if these marketing conversations have sparked something you've actually used, maybe a tip that saved you a headache, a couple of dollars a month is genuinely what keeps these going. Buy me a coffee dot com slash fexingo, if you've gotten something out of them. Lucas: Yeah, it's small amounts that add up to keep the show ad-free. Really appreciate anyone who chips in. Luna: Alright, back to the move sequence. What should that email look like? Lucas: The first email should acknowledge the change. Something like, 'We see you've moved — welcome to your new neighborhood, here's the FreshMart nearest you.' That's it. No hard sell. Just a recognition that they're in a new place. Luna: And then what? A coupon? Lucas: Maybe a small incentive on the second email. But the key is to get them to update their preferences. Because when they move, their shopping habits might change. They might now be closer to a different competitor. So you want to ask: 'What's your new go-to store? What time do you usually shop?' Rebuild the profile. Luna: So it's not just a one-off email. It's a mini onboarding sequence for a relocated customer. Lucas: Exactly. And it should be triggered fast — ideally within a week of the move being detected. The longer you wait, the more likely they are to establish a new habit with a competitor. Luna: Are there any companies that do this well? Anyone you'd point to? Lucas: I think the USAA — the financial services company for military families — does a decent job. They know their members move frequently because of deployments. So when a member updates their address, the system triggers a series of reminders about insurance coverage in the new state, banking options, even local discounts. Luna: That makes sense because they have a clear, predictable life event. But for a grocery chain, moves are less frequent. Might be harder to justify the integration cost. Lucas: That's a fair point. But let's do the math. If FreshMart has, say, 500,000 active loyalty members, and about 10 percent move in a given year, that's 50,000 moves. If you retain even 10 percent more of those — that's 5,000 customers. At an average basket of $50 per week, that's $250,000 a week in retained revenue. The integration cost pays for itself in a month. Luna: Okay, that's compelling. So the move event is a high-value trigger that a lot of marketers are leaving on the table. Lucas: And it's not just physical moves. Think about digital moves — someone changes their email address. That's also often missed. They start getting your emails at their old address and eventually stop engaging. Same concept. Luna: So we need a unified view of the customer that includes life events, not just transactions. Lucas: Yeah. And that's where the future of marketing automation should go — beyond behavioral triggers like 'abandoned cart' and into events like 'moved,' 'got married,' 'had a baby.' Those are the moments where you can actually build loyalty, not just capture a sale. Luna: But that requires a lot of data sources. Is it realistic for a mid-size company? Lucas: I think it is if you start small. Pick one life event — moves are a good one because the data is relatively clean from the USPS. Set up a monthly import, create a simple workflow, measure the retention lift. Once you prove the ROI, then you expand to other events. Luna: I like that. Start with what's achievable, then build. Lucas: Exactly. And the tools are already there — HubSpot has custom object triggers, Marketo has smart campaigns based on data value changes. It's more about process and data hygiene than technology. Luna: So the takeaway for this episode: don't ignore the move event. It's a small data fix with a big retention payoff. Lucas: Yeah. And if you're listening and you manage a marketing automation platform, check whether your billing data is synced. That's the first step. Luna: And maybe test a welcome-back sequence for moved customers. See what happens. Lucas: We'd love to hear if you try it. Drop us a note. For now, that's it from us.