Latest / Marketing Automation with Fexingo: HubSpot, Marketo, and Automated Customer Journeys / Why Marketing Automation Misses Customer Time Zone Shifts
Transcript
- Lucas: Let's talk about time zones in marketing automation. Specifically, what happens when your customer physically moves to a different time zone — and your workflow never finds out. Luna: I feel like that's a surprisingly common blind spot. Most platforms ask for a time zone once during sign-up and then just... hold onto it forever. Lucas: Exactly. And the data is pretty stark. According to the US Census Bureau's geographic mobility data, roughly 9 percent of Americans change their primary time zone in a given year. That's about 30 million people. For a B2C company with a million subscribers, that could be 90,000 contacts whose send-time optimisation is actively wrong. Luna: And what does 'actively wrong' look like in practice? Someone who moved from New York to Los Angeles still getting their 10 AM Eastern email at 7 AM Pacific? Lucas: Or worse — the reverse. Someone who moved from LA to New York getting their 10 AM Pacific send at 1 PM Eastern, when their inbox is already overflowing. One travel retailer I looked at — I'll call them JetSet — actually ran the numbers. They found that customers who had relocated within the past six months had a 23 percent higher unsubscribe rate than their stable-region customers. Luna: Because they were getting emails at the wrong time, feeling spammed, and just killing the relationship. Lucas: Right. And JetSet's marketing team initially blamed the content. They thought the emails themselves were off. But when they sliced the data by time zone match versus mismatch, the pattern was undeniable. Mismatched users had open rates 12 percentage points lower. Luna: So what did they do? Did they add a 'moving?' trigger to their onboarding flow? Lucas: They did something simpler and more clever. They added a single re-authentication step. When a user logs in from a new IP that maps to a different time zone, the system triggers a lightweight preference check — not 'did you move?' but 'we noticed you're in a new location. Want us to adjust your email timing?' Luna: That's elegant because it respects privacy. You're not tracking location constantly; you're using an event that already happens — login — to surface a permission-based update. Lucas: And the results were significant. JetSet saw a 17 percent lift in click-through rates for the re-authenticated segment within 30 days. And the opt-out rate dropped back to baseline. Luna: Seventeen percent is huge for a single workflow tweak. But I wonder — how many platforms actually support that kind of logic out of the box? If you're on Marketo or HubSpot, can you build this without custom code? Lucas: It depends. Both platforms have webhook capabilities and custom object fields. You can store the customer's current time zone as a field and update it via an API call triggered by a login event. If you're using a customer data platform like Segment or mParticle, that ip to time zone mapping is often available as a computed trait. Luna: So it's not plug and play, but it's maybe a week of development work. And the ROI is there. Lucas: I'd argue it's even simpler for companies that use a unified marketing platform. If you're all-in on Salesforce Marketing Cloud, for example, you can create a time zone attribute and update it via a triggered send from your mobile app when the user's GPS changes by more than a certain threshold. The point is, the technology exists — the gap is awareness. Luna: And often, the gap is also that marketing teams don't think of time zone as a dynamic field. They treat it like gender or birth date — something that's set once and stays. Lucas: Exactly. Birth date is static. Time zone is a customer life event, just like getting married or switching jobs. And if your automation treats it as immutable, you're sending the wrong message at the wrong hour to a growing slice of your audience. Luna: I know we've covered life events before in this show — credit card expirations, SMS consent windows, location changes. But I think time zone is especially insidious because it degrades performance silently. You don't get an error message. You just see a gradual dip in engagement and you don't know why. Lucas: And the fix is not expensive. For most mid-market companies, the engineering cost is measured in hours, not weeks. The travel retailer I mentioned spent maybe 40 hours total across their dev and marketing teams. Luna: Forty hours for a 17 percent lift in click-throughs. That's an incredible return. But let me play devil's advocate: what about customers who move but don't log in? Or who use a VPN? How do you handle false positives? Lucas: VPNs are a real edge case. JetSet handled it by requiring a confirmed IP change over three separate days before triggering the check. That filters out transient routing. For customers who never log in — well, you can fall back to a broad send-time optimisation based on their original time zone. You're not making things worse; you're just not fixing them for that subset. Luna: Fair. And if the user says 'no' to the prompt, you respect that and leave their time zone as-is. Better to be conservative. Lucas: Exactly. The key is to ask, not assume. And to ask at a moment that feels natural — right after a login, when they're already in a transactional mindset. Luna: I think this is one of those episodes where the takeaway is really straightforward: treat time zone as a dynamic field, build a trigger around IP or GPS changes, and let the customer confirm the update. Small effort, big impact. Lucas: And if you're listening and you're responsible for a marketing automation stack, I'd challenge you to pull a report of customers whose time zone hasn't changed in over two years. Then check your engagement metrics. I think you'll see a pattern. Luna: We should mention that if these marketing conversations have sparked something you've actually used — a workflow tweak, a data check, a trigger you built — it genuinely helps keep this show ad-free and independent. A couple of dollars a month at buy me a coffee dot com slash fexingo makes a real difference for us. Lucas: Yeah, it's small amounts from people who find value here that let us keep digging into these specific, tactical blind spots. No pressure at all — but if you've gotten something out of it, that's where you can help. Luna: Alright, back to time zones. One thing I want to push on: what about business to business marketing? If you're selling to companies, your contacts might work across multiple time zones, or they might travel frequently for work. Lucas: Great point. In B2B, the individual's time zone might matter less than the time zone of their primary office. But even there, you have remote workers who might be in a different zone than their HQ. The same principle applies — you can store a 'preferred working hours' window and use that for send-time optimisation. Luna: And that's a field you can update based on their calendar data, if they give permission. Or based on the time zone of their most frequent logins. Lucas: Exactly. The underlying logic is the same: treat timing as a living signal, not a dead field. And the payoff is better engagement, fewer unsubscribes, and a more respectful customer experience. Luna: I think that's a good note to end on. Next time, we might look at how automation handles customer name changes — another seemingly static field that actually changes more often than you'd think. Lucas: Oh, that's a good one. Name changes are a whole other layer of complexity, especially for women who change surnames after marriage. But that's for next time. Luna: For now, check your time zone fields. See you next episode.