Latest / Marketing Automation with Fexingo: HubSpot, Marketo, and Automated Customer Journeys / Why Marketing Automation Ignores Customer Birthdays and Anniversaries
Transcript
- Lucas: So I was looking at my inbox this morning — seven emails, all from brands I've bought from exactly once. And guess what? Not a single one acknowledged that it's my birthday tomorrow. Luna: Wait, your birthday's tomorrow? Happy early birthday! But yeah, it's wild how many companies have our birth dates — from loyalty sign-ups, from account creation — and they just… don't use them. Lucas: Exactly. And that's what I want to dig into today: personal milestones. Birthdays, anniversaries, the date you first subscribed — these are golden triggers for a marketing automation system. They're predictable, they're low-friction, and they give you a legitimate reason to reach out. Yet so many brands ignore them entirely. Luna: I wonder if it's a data quality issue? Like, maybe they have the date but it's buried in a legacy CRM field that the automation platform doesn't pull from. Lucas: That's definitely part of it. But I think the bigger issue is a mindset problem. A lot of marketing automation is built around behavior — 'you viewed this product, so we'll send you a reminder' — not around identity. Milestones are about who the person is, not what they just did. And that requires a different kind of data strategy. Luna: Let's get concrete. Can you name a brand that did this well? Or one that completely whiffed it? Lucas: Let me give you both. The whiff first: a mid-sized UK retail bank. They ran a campaign to reactivate dormant accounts — accounts that hadn't seen a transaction in over six months. They had all the data: birth dates, account opening dates, even the date of last contact. But the automation workflow they built triggered a generic 'we miss you' email on day 180 of inactivity. No personalization. Luna: Ouch. So you've been a customer for five years, your birthday is next week, and they send you the same email they send to everyone? Lucas: Exactly. And the result? A 12% lower reactivation rate compared to a test segment that got a birthday-themed message with a small incentive — like a one-time fee waiver. The bank had the data. They just didn't tie it into the automation logic. Luna: Twelve percent is huge. That's the difference between a campaign that breaks even and one that actually drives revenue. So what's the fix? Lucas: First, you need a clean, unified customer profile. That means deduplicating your CRM and syncing it with your marketing automation platform — HubSpot, Marketo, whatever you're using. Then you create a custom date field that the workflow can reference. In HubSpot, for example, you'd use a 'date property' like 'birthday' or 'account anniversary' and set a workflow to trigger on the exact date. Luna: But what about privacy? If you're in Europe, GDPR says you need explicit consent to use that data for marketing. A birthday email could be seen as processing personal data. Lucas: That's a really good point. And it's why a lot of companies are cautious. The key is to use what's called zero-party data — data the customer voluntarily shares with you. So when someone signs up for your newsletter, you ask: 'What's your birthday? We'll send you a special offer.' That's explicit consent. It's not scraped or inferred. Luna: Right. And a lot of progressive profiling tools let you collect that data over time. You don't have to ask everything on day one. Lucas: Exactly. You can prompt for a birthday on the second or third email, when the customer is more engaged. The response rate on those prompts is surprisingly high — one study I saw put it at around 34%, because people like being remembered. Luna: So the technical side is solvable. But the cultural side — actually caring enough to build the workflow — that's harder. Lucas: Right. And it's not just birthdays. Think about subscription anniversaries. If someone signed up for your SaaS product on March 15th, sending a 'happy one-year anniversary' email with a feature tip or a customer story can reduce churn by reminding them why they joined. I've seen it work in B2B contexts, too. Luna: That's smart. It's a moment of recognition. And if you combine it with a small gesture — like a discount or a free month — it feels personal, not transactional. Lucas: Exactly. And that's the core argument: automation doesn't have to be cold. The best automated journeys feel like a thoughtful human sent them. Milestones are the easiest way to inject that warmth. Luna: You know, speaking of thoughtful gestures — we hear from listeners who say these episodes help them think differently about their own marketing. And we keep the show ad-free on purpose. If you find value in what we do, supporting us at buy me a coffee dot com slash fexingo really helps keep it that way. Lucas: Yeah, it's a small ask, but it makes a big difference. No pressure — just a link for anyone who wants to chip in. Okay, back to milestones. Another angle I want to explore is the 'negative' milestone — the date a customer downgraded or canceled. Luna: Oh, that's interesting. Like a win-back campaign that acknowledges the loss, not just the date? Lucas: Exactly. If you know the exact date someone canceled, you can set a workflow to trigger 30 days later with a 'we miss you' message that references how long they were a customer. 'You were with us for two years — here's what's new.' That's way more effective than a generic 'come back' email. Luna: I can see that. It shows you remember the relationship, not just the transaction. But doesn't that require storing the cancellation date as a property? Lucas: It does. And most platforms have that data in the backend, but it's often not exposed as a workflow-eligible field. You might need to set up a custom property that gets written at cancellation via an API call or a Zapier-style integration. It's more work, but the payoff is real. Luna: Let's talk about the tools. HubSpot has a 'date property' that you can use in workflows. Marketo has trigger campaigns based on date fields. But there's a gotcha: time zones. Lucas: That's a huge gotcha. If you set a workflow to trigger on 'birthday' and the property is just a date without time zone context, the email might fire at midnight UTC, which means someone in California gets it at 5 PM the day before their birthday. That's not great. Luna: So you need to either store the time zone as a separate field or use a platform that handles time zone logic natively. Salesforce Marketing Cloud, for instance, has a 'send time optimization' feature that adjusts for the recipient's time zone. Lucas: Right. Or you can set the workflow to trigger at a specific hour based on the customer's time zone, but that adds complexity. The simpler hack is to send the email at a neutral time — like 10 AM in the customer's most likely time zone — and accept that some people will get it a few hours off. Luna: Better than nothing. But let's go back to the bigger picture. Why do you think so many companies still ignore milestones? Is it inertia, or is it fear of seeming creepy? Lucas: I think it's a mix. Inertia is real — once a workflow is built, marketers don't revisit it. And the creepiness factor is valid. If you send a birthday email to someone who never told you their birthday — you inferred it from a public profile — that can feel invasive. That's why zero-party data is so important. Luna: So the best practice is: ask, don't assume. Lucas: Exactly. And when you do ask, make it a value exchange. 'Share your birthday and get 15% off your next purchase.' That's fair. People are happy to trade data for value. Luna: I want to talk about one more type of milestone: the customer's anniversary with your company. Not their birth date, but the date they became a customer. Lucas: Yeah, that's a powerful one. It signals loyalty. And it's even easier to collect because you already have it — the date of first purchase or sign-up. The challenge is making it a visible field in your automation platform. Luna: Right. And you can tier it — year one, year three, year five. Different messages for different stages. A one-year anniversary might be a 'thank you' with a beginner tip, while a five-year anniversary could be a VIP invite. Lucas: That's exactly how a lot of subscription boxes do it. I've seen Birchbox send a 'happy anniversary' email with a curated set of samples based on what the customer liked in their first month. That kind of personalization is only possible if you track the date and have the purchase history linked. Luna: So the technology exists, but the will to implement it is missing. What would you say to a marketer listening who wants to start tomorrow? Lucas: Pick one milestone. Just one. Start with the date of first purchase. Export that data into your marketing platform, create a workflow that sends a 'one-year anniversary' email with a simple thank-you. See what happens. Measure the open rate, the click rate, and compare it to your average promotional email. I bet it outperforms. Luna: And then you can build from there. Birthdays, subscription anniversaries, maybe even the date they last upgraded. Lucas: Right. The point is, automation is at its best when it feels human. And remembering someone's special day — that's about as human as it gets.