Latest / Marketing Automation with Fexingo: HubSpot, Marketo, and Automated Customer Journeys / How Marketing Automation Forgets Your Political Donation
Transcript
- Lucas: So Luna, quick question. You give twenty-five dollars to a political campaign in March. That's it. One small donation. What do you think happens the next time that campaign sends an email? Luna: I'd like to think they'd treat me like a supporter. Maybe acknowledge I gave. But honestly, I suspect I just get the same 'We need your help' email as everyone else. Lucas: Right. And that's the puzzle I want to dig into today. The marketing automation behind most donation funnels is built around a single event — the gift. But it almost never updates the donor's status in a way that changes their experience. Luna: So the system treats a one-time giver the same as a stranger. That's a missed opportunity, isn't it? Lucas: Exactly. And it's not just politics. Any nonprofit, any cause, any membership organization that takes a donation — the same pattern holds. The automation records the transaction, but it doesn't update the relationship. Lucas: I think the core issue is that most marketing automation platforms default to event-based triggers. You click a link, you open an email, you submit a form — those are events. And they're easy to wire up. But they don't tell you who someone is, they only tell you what they did once. Luna: So what should it be instead? State-based logic? Lucas: Yeah, that's the phrase I'd use. Instead of just firing an email when someone donates, you update their lifecycle stage. They move from 'prospect' to 'first-time donor.' And that single change should alter every subsequent communication. Luna: But in practice, it doesn't happen. Why? Lucas: Inertia, mostly. And also because setting up those lifecycle stages takes a bit of upfront thinking. You have to define what 'donor' means — is it anyone who gives once, or only those who give twice? And you have to map out the different paths someone can take. Luna: It sounds like the kind of thing that gets pushed aside when you're just trying to get a campaign out the door. Lucas: Right, and that's exactly the trap. The short-term win of sending one email beats the long-term value of building a proper model. So the donation gets logged, the thank-you goes out, and then everyone moves on to the next push. Luna: So what's the concrete fix? If I'm a small nonprofit and I want to do this better, where do I start? Lucas: Before I answer that, I want to mention something. This podcast has always been ad-free, and that's a choice we make deliberately. If these conversations have given you a useful idea that you've actually taken to work — or even just a way to think about your own marketing — and you'd like to support that, the link is buy me a coffee dot com slash fexingo. No pressure, but it genuinely helps keep this going. Luna: And it's nice to know there's no sponsor trying to sell you a CRM while we're talking about CRMs. Lucas: Ha, exactly. Okay, back to the fix. The first step is to stop thinking about the donation as the end of a journey. Think of it as the start of a relationship. Lucas: So you create a lifecycle stage called 'first-time donor.' And you set up the automation so that when the donation event fires — the payment goes through — the system also updates that stage. Then you have a separate set of emails for that stage, and they don't ask for money again immediately. They say thank you, they show the impact, they invite the person to get more involved. Luna: But what about someone who gives a second time? Does the stage update again? Lucas: It should. That's the 'repeat donor' stage. And from there, you can start to build a whole ladder — from first-time to repeat to monthly to major donor. Each stage has its own cadence and its own messaging. Luna: So the automation is really about managing a progression, not just firing off emails. Lucas: Exactly. And the interesting thing is, most platforms support this natively. HubSpot, Marketo, even the simpler tools — they all have lifecycle stage or lead status fields. The problem isn't the software, it's the mental model. Lucas: People default to the event because it's easier to conceive. 'If someone donates, send this email.' But the state-based approach is more human. It mirrors how you'd naturally treat a friend who just gave you a gift — you wouldn't immediately ask for another one. Luna: Right. And that's a failure of empathy in the data model, isn't it? The automation doesn't have a sense of the person's journey. Lucas: That's a perfect way to put it. Empathy in the data model. The system treats every email address the same, because that's what the data shows — a list of emails. But the actual people have different relationships to the cause, and the automation should reflect that. Luna: I actually saw a nonprofit do this well once. They had a campaign where they segmented based on whether you'd attended an event, donated before, or volunteered. And the emails were totally different. The volunteers got stories from the field, the donors got impact reports, and the event attendees got invitations to the next thing. Lucas: That's a great example. And notice they didn't just use one behavioral event. They looked at the whole history — any donation, any event attendance, any volunteer shift. That's the richer state. Lucas: So if you're setting this up, the first thing to do is audit your current data. Do you have a field that says 'donor status'? If not, create one. Then map out your funnel — from first touch to major gift — and assign a stage to each milestone. Luna: How long does that take? Lucas: Honestly, an afternoon. The harder part is getting the team to agree on the definitions. Is a donor someone who gives any amount, or does it have to be above a threshold? And what about someone who gives once and then goes quiet for two years — do they go back to 'lapsed'? Luna: Those are the kind of questions that make or break the whole thing. Lucas: They are. But the payoff is huge. You stop sending the same generic ask to everyone, and you start having actual conversations with people at different stages of their relationship with you. Lucas: And that's not just for nonprofits. Any business that has a repeat purchase cycle — think a gym, a subscription box, a SaaS product — can use the same logic. The behavior is different, but the principle is the same: understand where each customer is in their journey, and tailor the message accordingly. Luna: So the real lesson is to move from event-based to state-based thinking in your automation. Lucas: That's the big takeaway. And it's not a technical challenge, it's a conceptual one. Once you make that shift, you'll stop having these blind spots where a donor feels ignored or a customer feels like you don't know them. Luna: And you'll probably see better retention, too, because people respond to feeling understood. Lucas: Exactly. So next time you're building an automation workflow, ask yourself: what stage is this person in, and what do they need next? Not just, what did they just do?