Latest / Marketing Automation with Fexingo: HubSpot, Marketo, and Automated Customer Journeys / Why Marketing Automation Ignores Customer Charity Donations
Transcript
- Lucas: So I got an email last week from a charity I've given to maybe twice. Subject line: 'Urgent: Help us reach our goal before midnight.' And I thought — okay, maybe it's year-end. But it's July. And I just donated three months ago. Luna: Right, the classic 'treat every donor like a first-time stranger' approach. I bet they didn't even check your donation history. Lucas: Exactly. And that's the thing — marketing automation platforms like HubSpot and Marketo are brilliant at triggering follow-ups based on purchase recency. But when it comes to charitable giving, the system treats it like any other transaction. It doesn't understand that a donation is often tied to identity, not just a one-off click. Luna: Which is ironic, because nonprofits were early adopters of CRM for donor management. But the automation layer seems to have regressed. Lucas: Look, I think a big reason is that most marketing automation is built for e-commerce — purchase frequency, cart abandonment, product recommendations. Charity doesn't fit that model. A donor might give once a year on Giving Tuesday, then vanish. If your system only looks at recency, that donor gets flagged as 'cold' after 90 days and starts getting desperate appeals. Luna: And that's exactly when you lose them. I've seen studies that say donor retention drops by half after the first year if you treat giving like a transaction. Lucas: Yeah, and that's a real shame because the data is right there. You just need to tell the system that charity is a different behavioral category. Quick honest thing — a handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making this many of these episodes. No ads, just listener support. It keeps us free to dig into these gaps. Luna: And it's exactly the kind of thing that makes a show like this sustainable. So thank you to those who do. Lucas: Anyway, back to the charity gap. The fix is surprisingly simple. You add a custom field in your CRM called 'donor since' or 'last gift date' — but not as a timestamp, as a lifecycle stage. So you have a segment called 'annual giver' or 'disaster responder'. Luna: So instead of blasting everyone with the same 'Urgent' email, you can map triggers to their typical giving pattern. If someone only gives during December, you don't email them in July. Lucas: Right. And even better, you can set up a workflow that recognizes a donation as a 'value signal' — not just a transaction. So after someone gives, instead of a generic thank-you, you send them a survey asking 'What cause matters most to you?' Then you use that to segment. Luna: That builds trust. And trust is the whole point. If you spam a donor who just gave for disaster relief with a plea for general operations, they feel manipulated. Lucas: Exactly. And this isn't just about nonprofits. Think about any brand that has a charity arm or does cause marketing. Patagonia, for example. If you buy a jacket from their 'Gifts for the Earth' collection, and then two weeks later you get a generic email about winter clearance, it undermines the connection. Luna: So what's the concrete takeaway for a marketer listening right now? What's the one thing they should change by end of week? Lucas: Create a 'charity donor' segment in your automation platform. Even if you're not a nonprofit, if you have any cause-related products or campaigns, separate those customers. Then build a nurture flow that acknowledges their giving — with timing that respects when they usually give, not when your system wants to push. Luna: And maybe add a 'donor since' field that's visible to the customer. Show them you remember. That's the kind of personalization that actually matters. Lucas: Yeah. And if you're using HubSpot, you can set a property like 'charity interest' and use it in list membership. It's a two-hour setup that could save you from looking like that charity that emailed me in July. Luna: I'd add one more thing: test the timing. If your data shows a donor gives every December, suppress them from all November fundraising emails until December 1st. Then hit them with a single, well-timed ask. Lucas: That's smart. And it respects the customer's own calendar. The thing is, marketing automation is great at volume but terrible at context. Charity is a context-heavy behavior. You give because of something personal — a family member's illness, a natural disaster, a religious holiday. Luna: And if the automation doesn't capture that context, it's just noise. Lucas: Right. So here's a quick checklist for any marketer: one, identify all customers who have ever donated or bought a cause-linked product. Two, assign a lifecycle stage based on giving frequency — 'first-time donor', 'repeat donor', 'annual donor'. Three, create a workflow that suppresses general appeals for 90 days after a gift, and instead sends a personalized impact update. Luna: And for the annual donors, send them a 'sneak peek' of your giving campaign a week before their usual month. Make them feel like insiders. Lucas: That's exactly right. And this works beyond charity too. Think about any behavior that's identity-driven: volunteering, attending a religious service, joining a community board. If your automation only sees transactions, you miss the person. Luna: So next time you're building a workflow, ask: is this person giving me money, or are they telling me who they are? Lucas: That's a great way to put it. And on that note, I think we've given listeners enough to go fix their charity automations. Thanks for the conversation, Luna. Luna: Always a pleasure.