Latest / Marketing Automation with Fexingo: HubSpot, Marketo, and Automated Customer Journeys / Why Your Automation Needs a Customer Data Platform Integration
Transcript
- Lucas: If you're running marketing automation on HubSpot or Marketo and you're not getting the results you expected, the problem might not be your sequences or your copy. It might be that the data feeding your automation is sitting in the wrong database. Luna: You're talking about the Customer Data Platform debate — whether you actually need a CDP layered underneath your automation platform. Lucas: Exactly. And a lot of marketers I talk to assume their CRM or their marketing automation tool is already acting as a CDP. But they're fundamentally different things. A CRM is built for tracking interactions and managing relationships. A marketing automation platform is built for sending triggered communications. Neither is designed to be the single source of truth for every customer profile across every system. Luna: So what actually qualifies as a CDP? Because I've seen vendors rebrand their existing tools as one. Lucas: True CDPs ingest data from multiple sources — web behavior, purchase history, support tickets, offline events — and stitch them into a persistent, unified profile. Then they make that profile available to other systems in near real time. The key word is 'persistent.' A marketing automation platform typically holds data for the duration of a campaign or a lifecycle stage. A CDP keeps the history. Luna: Right, so the automation platform knows the lead clicked the email yesterday. The CDP knows the lead clicked the email yesterday, called support two weeks ago about a billing issue, and bought a similar product on Amazon last month. Lucas: That's exactly the kind of context that changes how you automate. Let me give you a real example. I spoke with the marketing director at a mid-size e-commerce company — about fifty million in annual revenue, using Marketo as their automation layer. They had this classic problem: their abandoned cart flow was sending a discount offer to people who had already purchased the item through a different channel. Embarrassing and expensive. Luna: I've seen that. The customer buys on Amazon or in-store, but the automation doesn't know about it because that data lives in the ERP, not in Marketo. Lucas: Precisely. So they integrated a CDP — I won't name the vendor because there are a dozen good ones — and they unified purchase data from their e-commerce platform, their POS system, and their Amazon seller account. Within three months, their abandoned cart email revenue went up thirty-four percent, and their discount spend dropped by twenty-two percent because they stopped sending offers to customers who had already converted. Luna: That's a meaningful lift. But I wonder: how many businesses actually need a separate CDP? Could they get similar results by just cleaning up their CRM and syncing more data sources into Marketo directly? Lucas: It depends on scale and complexity. If you have a single data source — say, just website interactions and email — you might be fine with your automation platform's native database. But once you have three or more source systems, especially if some are offline, the integration points become a nightmare. You end up with what I call 'data spaghetti' — point to point connections that break every time a vendor updates their API. Luna: Data spaghetti. I like that. So the CDP becomes the central hub that all those connections feed into, and then it sends a clean, unified feed to Marketo or HubSpot. Lucas: Yes. And that matters more than ever because personalization expectations have gone up. A customer who gets an email referencing something they did on your site last week expects you to know who they are. If your automation is acting on stale or partial data, the personalization feels generic or, worse, wrong. Luna: Let's talk about the hidden cost of not having a CDP. I've read that data silos can cost enterprises millions in wasted ad spend alone. Lucas: Absolutely. One example: a company runs a Facebook retargeting campaign for people who visited a product page. But their automation tool also sends an email with a discount for the same product. The customer gets both, clicks the email, buys, but Facebook still counts the conversion. So the advertiser pays for two touches when one would have sufficed. A CDP can deduplicate those audiences and enforce frequency caps across channels. Luna: So it's not just about better email performance — it's about reducing overall customer acquisition cost. Lucas: Right. And there's another angle: compliance. With privacy regulations tightening, you need a reliable way to manage consent across systems. If a customer opts out on your website, do you propagate that to your email platform, your ad platform, your call center tool? A CDP can act as the central consent repository. Luna: That's a strong argument for larger organizations. But for a small business with a few thousand contacts, the complexity and cost of a CDP might outweigh the benefits. Lucas: Fair point. For a smaller operation, I'd recommend first making sure your CRM data is clean and that you're using custom fields and lists properly. You can get a surprising amount of mileage out of a well-structured HubSpot or ActiveCampaign setup. But if you're scaling past ten thousand contacts and have multiple data sources, start evaluating CDPs early. The cost of retrofitting later is much higher. Luna: I read a report from Gartner that said by 2027, sixty percent of marketing automation buyers will require a CDP as part of their stack. We're almost there. Lucas: It's already happening. And the CDP landscape is consolidating. Major CRM and automation vendors are either building their own CDP capabilities or acquiring them. Salesforce has their own CDP. Adobe has Real-Time CDP. HubSpot recently added more robust data unification features. So the line is blurring. Luna: If someone's listening and thinking, 'Maybe I should look into a CDP,' what's the first step? Lucas: Audit your data sources. Make a list of every system that holds customer data — email platform, e-commerce, POS, support ticketing, loyalty program, offline events. Then count how many integrations you'd need to build if you wanted to unify those profiles. If it's more than two or three, and you're regularly sending cross-channel campaigns, you have a strong use case. Luna: And then the classic question: build vs. buy? Lucas: Ninety percent of the time, buy. Building a CDP internally is a multi-year data engineering project. Even the largest companies often use a vendor. The key is to choose one that integrates well with your existing marketing automation platform and supports the data sources that matter most to you. Luna: I want to circle back to something you mentioned earlier — the idea that your automation platform's performance is capped by the quality of its data. That's a sobering thought for anyone who's invested heavily in building complex workflows. Lucas: It is. But it's also an opportunity. The low-hanging fruit in marketing automation right now isn't more sophisticated logic — it's better data flowing into the logic you already have. A CDP integration can make your existing workflows suddenly smarter without you rewriting a single email. Luna: And if these conversations about data and automation have sparked something you've actually used in your own work, that's exactly why we keep making them. A handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that literally funds the time we spend digging into topics like this. Lucas: It does. And we're genuinely grateful for that — it means we can keep these episodes ad-free and focused entirely on what's useful. Now, back to the data question: once you do integrate a CDP, one of the first things you'll notice is how much more accurate your lead scoring becomes. Because the CDP surfaces behavioral signals from across the customer journey, not just email clicks. Luna: That's a good segue for a future episode. We could do a deep dive on how CDP data changes lead scoring models. Lucas: I'll put that on the list. For now, the takeaway is simple: before you add more triggers, more sequences, more complexity, check your data foundation. If it's shaky, a CDP might be the most impactful investment you make this year. Luna: And if you want to share your own data integration wins or horror stories, you know where to find us. Lucas: We'll read the best ones on a future episode.