Latest / Marketing Automation with Fexingo: HubSpot, Marketo, and Automated Customer Journeys / How Automation Misses Customer Grocery Swaps
Transcript
- Lucas: Luna, I want to talk about something hiding in plain sight in marketing automation: the grocery swap. Luna: Grocery swap? You mean when someone switches from one meal-kit service to another? Lucas: Exactly. But it's bigger than that. Think about how many households now rely on some form of grocery delivery subscription. I'm looking at a Statista survey from early 2025 — 42 percent of U.S. households use at least one. And the average customer switches providers every eight months. Luna: Eight months. That's fast. And I bet most automation platforms just flag it as a 'subscription cancelled' event and move on. Lucas: That's the problem. They treat it as churn. But it's often a signal — a really rich one. When someone switches from HelloFresh to Sunbasket, or from a keto meal plan to a Mediterranean one, that tells you something about their life. Maybe they're trying to eat healthier, maybe their doctor put them on a new diet, maybe their budget changed. Luna: Right, so you're saying the automation should be looking at what they swapped to, not just that they swapped. Lucas: Precisely. And the data is there. Grocery receipts — even the digital ones — contain brand choices, portion sizes, dietary tags. But most marketing automation platforms don't ingest that data at a granular level. They see a cancellation trigger, send a 'come back' email, and move on. Luna: That's a huge missed opportunity. I mean, if you know someone switched from keto to Mediterranean, you could recommend products that fit that new lifestyle. But the system has to actually be wired to care. Lucas: Let me give you a concrete example. There's a DTC protein-bar brand — I won't name them — that lost about 30 percent of its repeat buyers over a six-month period. They couldn't figure out why. Their automation was solid: replenishment emails, loyalty discounts, post-purchase surveys. But the churn kept climbing. Luna: What was the root cause? Lucas: They eventually ran a manual analysis of a sample of those churned customers. Turned out, a big chunk had switched from a keto diet to a Mediterranean diet. Their protein bars were keto-optimized — high fat, low carb. Once customers moved to a Mediterranean plan, those bars no longer fit their macros. But the brand's automation never picked up on that dietary shift. Luna: So the customers didn't churn because they disliked the product. They churned because the product no longer fit their life. Lucas: Exactly. And if the automation had been watching the grocery-swap signal — say, a customer cancels their keto meal-kit subscription and starts a Mediterranean one — the brand could have triggered a different sequence. Maybe a recommendation for a different product line, or a survey about new nutritional needs. Luna: How feasible is that integration? Because I know pulling in real-time grocery data isn't trivial. Lucas: It's not trivial, but it's getting easier. Meal-kit services and grocery-delivery apps have APIs. You can subscribe to webhooks for subscription changes. The harder part is mapping that data to a customer profile in your automation platform. Most HubSpot or Marketo instances don't have a field called 'dietary preference' that updates dynamically. Luna: So there's a data-schema problem. The platform could handle it if you set it up, but most marketers don't think to build that field. Lucas: Right. And the cost of building that integration is real. But compare it to the cost of losing 30 percent of your repeat buyers. Suddenly the integration pays for itself. Luna: I wonder how many other signals like this we're ignoring. Pet adoption, moving events, job changes — we've talked about those before. But grocery swaps feel almost too mundane to notice. Lucas: That's the thing. It's mundane in isolation, but it's a leading indicator. When someone changes their grocery subscription, they're often changing their behavior before they change their brand loyalties. If you catch that early, you can adapt your messaging, your product recommendations, even your pricing. Luna: So what would the ideal trigger look like? Walk me through a hypothetical. Lucas: Okay. Say a customer named Jen has been getting a keto meal kit for six months. One week, she cancels and signs up for a Mediterranean plan. Your automation platform gets a webhook from the meal-kit service — say, a 'subscription changed' event with the new plan name. Luna: And then what? The platform needs to know what 'Mediterranean' means. Lucas: You'd have a lookup table. 'Mediterranean' maps to a tag like 'dietary_mediterranean'. That tag then triggers a sequence: maybe a 'welcome to your new plan' email from the meal-kit service, but also an update to Jen's profile in your CRM. If you sell complementary products — like olive oil, whole grains, or lean protein — you can send a targeted offer. Luna: And if you're the protein-bar brand from earlier, you'd know not to send the keto-bar replenishment email. You'd send something else. Maybe a new product line. Lucas: Exactly. The key is that the automation is listening for the life change, not just the purchase change. And grocery swaps are a proxy for a lot of life changes: health diagnoses, new year's resolutions, budget shifts, relationship changes. Luna: It's almost like a canary in the coal mine. If you see the grocery swap, you know something bigger is happening. Lucas: Right. And the beauty is, you don't need to know exactly what the bigger thing is. You just need to know that something changed, and that your previous assumptions about the customer might be stale. Luna: So what's the first step for a marketer listening to this? Should they start by mapping out the grocery subscriptions their customers might have? Lucas: Start with the data you already have. If you're a DTC brand, look at your churned customers. Manually sample a few dozen. See if you can find any pattern in their subscription changes. You might be surprised. Then, look at which grocery or meal-kit services have APIs. A lot of the big ones do. Start with one integration. Luna: And if you use HubSpot or Marketo, you can create custom properties for dietary preference or subscription type. It's not hard once you know what to look for. Lucas: Exactly. And honestly, this is the kind of thing that separates good automation from great automation. Good automation sends the right email at the right time. Great automation knows when the customer has changed what they need. Luna: I'm curious — are there any platforms that do this well already? Lucas: Not that I've seen at scale. A few bespoke setups at large retailers, but nothing off-the-shelf. That's the opportunity. The first platform to build a 'life event' module that ingests grocery data will have a real edge. Luna: So it's a green field. And it's not just groceries — it's any recurring subscription that signals a change in lifestyle. Lucas: Right. Meal kits, grocery delivery, even pet food subscriptions. When someone changes a pet food subscription — maybe from puppy to adult formula — that tells you the dog is growing. That's a life event. But most automation just sees a product change. Luna: We keep circling back to the same point: automation is great at reacting to actions, but terrible at inferring context. Lucas: That's the fundamental gap. And I think part of the reason is that marketers are overwhelmed with data. They have so many signals coming in that they stick to the easy ones: email opens, clicks, purchases. The harder signals — like grocery swaps — require more work upfront. Luna: But the payoff is huge. That protein-bar brand could have saved 30 percent of its repeat buyers. That's a direct revenue impact. Lucas: Absolutely. And it's not just about retention. It's about relevance. If you can show a customer you understand that they've changed their diet, you build trust. That's hard to quantify, but it's real. Luna: And that's what we're trying to do here, right? Have conversations that spark something you can actually use. If you've found value in these episodes, and you want to support the show being ad-free — no sponsors, no interruptions — there's a link: buy me a coffee dot com slash fexingo. It's a simple way to keep this independent. Lucas: Yeah, we deliberately don't run ads. That's a choice. And listener support is what makes it possible. So if you've gotten something out of this, that link is there. No pressure, just an option. Luna: Alright, back to grocery swaps. Lucas, you mentioned that the protein-bar brand's analysis was manual. How long did it take them to figure out the pattern? Lucas: About three months from when they noticed the churn spike to when they identified the dietary shift. That's three months of lost revenue and confused customers. With automation, they could have caught it in days. Luna: So the cost of not having the integration is not just the churn, but the delay in understanding the churn. Lucas: Exactly. And the delay compounds. Every week you don't know why customers are leaving, you're sending the wrong messages to the wrong people. You might even be accelerating churn. Luna: How so? Lucas: If you send a 'we miss you' email with a discount on keto bars to someone who just switched to Mediterranean, they feel misunderstood. That can push them further away. It's a negative reinforcement loop. Luna: Right. So the automation actually makes things worse if it's not context-aware. Lucas: Precisely. And that's why I think grocery swaps are such a powerful signal. They're a leading indicator of context change. If you can detect that, you can adjust your entire communication strategy. Luna: So what's the next frontier? Are we going to see platforms start to offer 'life event' modules? Lucas: I think so. The technology is there. It's really about prioritization. Marketers need to demand it. If enough people start asking their CRM vendor for this kind of integration, the vendors will build it. Luna: Maybe we should start a list of 'signals that matter' for our listeners. Grocery swaps, job changes, pet age changes, moving events — we've covered a few. Lucas: That's a good idea. And I'd add one more: changes in recurring charity donations. If someone starts donating to a health-related charity, that might signal a personal diagnosis. That's a huge context shift. Luna: But pulling that data is even harder than grocery data. Privacy concerns are real. Lucas: True. But you can ask. A simple survey like 'Has anything changed in your life recently?' can work wonders. The key is to ask in a way that feels helpful, not nosy. Luna: And then use that data to trigger the right automation. That's the loop. Lucas: Exactly. Start with the data you can get, build the triggers, and iterate. That's how you move from good automation to great automation. Luna: Alright, I'm going to look at my own automation setup this week and see if I'm ignoring any grocery swaps. Lucas: I think you'll be surprised what you find. Thanks for the conversation, Luna. Luna: Thanks, Lucas.