Most organisations don’t struggle with consent because they ignore the rules. Forms are compliant, opt-ins are recorded, and unsubscribe links exist. On paper, consent looks sound.
Yet customers still receive emails they thought they’d stopped, promotions for things they’ve already purchased, or follow ups that ignore what just happened. This is where consent usually breaks down, not at capture, but in execution.
Consent is captured once. Experience unfolds many times.
Consent is typically collected at a single moment, a form fill, a checkout, an event registration. Customer journeys don’t behave that way. They unfold over time, across channels and systems, and often across more than one identifier for the same person.
When consent is treated as a static flag rather than a signal that needs to be respected everywhere, gaps start to appear. From the organisation’s point of view, the rules were followed. From the customer’s point of view, their choice was ignored.
Customers don’t experience systems. They experience outcomes.
Customers don’t know which platform sent which message or where a consent flag is stored. They experience one brand. That’s why moments like an email after an opt out, or a campaign that ignores a recent purchase, feel jarring.
Shared email addresses make this worse. One person unsubscribes, another record continues to receive messages, and the customer assumes the unsubscribe didn’t work. Even when everything is technically compliant, those experiences undermine confidence. Customers don’t analyse consent models. They react to what shows up.
Where real world journeys expose weak consent design
The most common failures are rarely edge cases. Event spreadsheets processed weeks later. Multiple systems sending messages without a shared view of identity. Household or role based email addresses treated as separate people.
In each situation, consent isn’t wrong. It’s fragmented or delayed. One system reflects an opt out immediately. Another updates later. A third never receives the signal at all. The result is a message that should not have been sent.
That isn’t a policy problem. It’s an execution problem. And it shows up in ways that are immediately visible to customers and costly to the organisation.
Why this matters commercially
When consent breaks down in execution, the impact shows up quietly. Engagement declines. Deliverability weakens. Performance becomes harder to predict.
Teams often respond by adjusting creative, cadence or segmentation, but those changes don’t stick if the underlying signals are misaligned. What customers experience as “you didn’t listen” becomes, internally, a slow erosion of trust and effectiveness.
The cost isn’t just spam complaints or unsubscribes. It’s the technical effort spent investigating “system failures” that turn out to be integration gaps. It’s customer service time spent explaining why someone received a message after opting out. It’s reputational damage that compounds over time.
Designing consent for how customers actually behave
Consent that holds up in real customer journeys is designed with movement in mind. It assumes customers will switch channels, share contact details and change behaviour. It assumes identity won’t always be clean or singular. It also assumes opt outs need to propagate everywhere, without delay.
Teams that get this right prioritise consistency over complexity. When signals conflict, they err on the side of caution. The focus shifts from maximising volume to preventing the wrong message from being sent.
This starts with an audit. Understand where consent data lives, where rules differ between systems, and critically, what causes those differences. Is one system used to collect consent but never to update it? Does consent from an event get processed weeks after collection? Are phone numbers and email addresses treated as independent channels when they belong to the same person?
From there, establish a single source of truth. When a system needs to send a message, it should be able to confirm whether a contact is subscribed right now and what that subscription actually covers. That answer needs to be authoritative, current and accessible across all sending systems.
When in doubt, default to the most conservative interpretation. If consent status conflicts across systems, treat the contact as unsubscribed. It’s easier to rebuild permission from a position of trust than to repair a relationship after repeatedly ignoring someone’s stated preferences.
Where unified data makes the difference
This is where Data 360 plays a practical role. By helping unify identity and keep customer profiles current across systems, it reduces the risk of small but visible mistakes that customers notice immediately. Not to do more, but to get fewer things wrong.
When consent signals are fragmented, even a technically correct implementation can produce customer experiences that feel wrong. Unified data doesn’t just support compliance. It supports execution that makes consent fade into the background, which is exactly where it belongs.
Most consent problems live in the gap between capture and execution
Consent is given in one moment, but experienced across many. When systems, timing and identity don’t line up, that gap becomes visible to customers very quickly, not just as a legal failure, but as something that simply doesn’t make sense.
Closing that gap isn’t about tightening policy. It’s about making sure what you send reflects what’s already happened. When that holds, consent becomes quiet, consistent and largely invisible.
If you’re seeing signs that consent is technically sound but operationally fragile, it’s often worth stepping back and reviewing how consent actually flows through your journeys. We regularly help teams assess where execution drifts from intent and what to fix first. If you’d like to talk it through, we’re here.
