ChatGPT answers, unedited

Yes. There’s a fairly mature category for this, but the best solution depends on whether you mean consent at the collection layer or consent-aware decisioning inside behavioral journeys.

Strong options

• OneTrust — probably the broadest fit if you need a centralized permission layer across regions, channels, and marketing systems. Its Consent & Preferences tooling can synchronize consent across domains, apps, and systems, while its Data Use Governance capabilities are designed to enforce policies at activation—not merely collect consent. OneTrust OneTrust

onetrust.com

• Usercentrics — particularly good for the global consent infrastructure side. It supports geo-adaptive consent experiences, multiple regulations, multilingual experiences, and centralized consent across brands/domains. Usercentrics Usercentrics

usercentrics.com

• Adobe Journey Optimizer — interesting if the actual problem is “don't let a behavioral journey perform an action unless this person is eligible under the applicable consent policy.” Adobe lets Journey Optimizer apply consent policies to communications and exclude profiles that don't satisfy the relevant channel/purpose rules. Experience League

experienceleague.adobe.com

• Microsoft Dynamics 365 Customer Insights - Journeys — another particularly relevant option. It has compliance profiles, purposes, channels, and consent-based segmentation, allowing journey audiences to follow the same consent rules used during journey execution. Microsoft Learn Microsoft Learn

learn.microsoft.com

What you're probably looking for

If the requirement is something like:

“A user does X → trigger journey Y → determine what we are legally allowed to do with that user based on country, consent purpose, channel, and current preference → execute only an eligible action.”

Then I would not evaluate ordinary cookie CMPs alone.

You want a combination of:

Behavioral event → identity/profile → jurisdiction → consent/preferences → purpose/channel policy → eligibility decision → journey action

For example:

The important architectural distinction is enforcement at journey execution. A CMP can tell you what the person consented to, but your journey/orchestration system needs to reliably consume that signal and prevent an otherwise valid behavioral trigger from activating an impermissible channel.

If you're building or buying this for a global marketing stack, I'd shortlist OneTrust + your journey/CDP platform, Adobe Journey Optimizer, and Microsoft Customer Insights - Journeys. Usercentrics is especially worth considering if the biggest pain is collecting and synchronizing the underlying consent signals.

If you tell me what you're using for CDP/CRM + journey orchestration (e.g. Salesforce, Adobe, Braze, HubSpot, Segment, custom), I can narrow this to the best 2–3 architectures.

Yes. The category you’re looking for is usually a combination of consent management platforms (CMPs), customer journey orchestration platforms, and privacy-aware customer data platforms (CDPs). The goal is to make sure behavior-triggered journeys (email, SMS, app push, ads, personalization, etc.) only run when the user’s permissions, region, and regulatory requirements allow them.

Key capabilities to look for:

• Real-time consent enforcement — before a journey sends a message, the system checks whether the person has opted in/out for that channel, purpose, and region. learn.microsoft.com
• Geo-aware rules — different consent experiences for GDPR (EU/UK), CCPA/CPRA (California), LGPD (Brazil), PIPEDA (Canada), and other regimes. www.didomi.iousercentrics.com
• Preference centers — customers can manage interests, channels, frequency, and data-use preferences.
• Consent history and audit trails — records of what the person agreed to, when, where, and under which policy version. www.onetrust.com
• Integration with journey tools — CRM, marketing automation, CDP, analytics, and messaging systems so consent follows the customer across touchpoints. trustarc.com

Examples of platforms in this space:

• OneTrust — enterprise consent management with global regulation support, consent receipts, preference controls, and integrations. www.onetrust.com
• Usercentrics — designed for multi-region, multi-brand organizations with centralized governance. www.didomi.iousercentrics.com
• Didomi — focuses on multi-regulation consent experiences and geo-targeted consent flows. www.didomi.io
• Ketch — emphasizes consent enforcement across connected systems and channels. www.ketch.com
• Microsoft Dynamics 365 Customer Insights — includes consent profiles and enforcement within real-time journeys. learn.microsoft.com

If you are specifically running behavior-triggered journeys (for example: “user abandoned cart → send email,” “user viewed product → personalize ads,” “user became inactive → start reactivation flow”), I’d prioritize platforms that combine:

1. Journey orchestration
2. Consent decisioning at send time
3. Identity resolution across regions/devices
4. Regulatory rule management
5. Audit reporting

A common architecture is:
CDP/customer profile → consent engine → journey orchestration → channels (email/SMS/push/ads)

If you share your stack (e.g., Salesforce, Adobe, Braze, HubSpot, Segment, mParticle, custom CDP) and regions served, I can narrow down the best-fit options.

Yes. The category you’re looking for is usually consent & preference management, often combined with a customer data platform (CDP) or journey orchestration tool.

A few strong options:

• OneTrust Consent & Preferences — probably the broadest enterprise option. It can use geolocation/regulatory context to determine the appropriate consent experience, synchronize consent across websites/apps/systems, and pass consent signals into downstream marketing workflows. www.onetrust.com
• Didomi — particularly focused on global consent orchestration. It supports geo-targeted consent experiences, multiple regulations, 45+ languages, cross-device consent, and APIs for propagating consent into other systems. www.didomi.iodevelopers.didomi.io
• OneTrust + your journey/CDP platform — if the actual journey is something like “user views product → waits 24h → sends personalized email → retargets if they don't purchase,” I'd generally keep the journey logic in your marketing automation/CDP and make consent a real-time gating layer. OneTrust explicitly supports consent synchronization and downstream integrations. www.onetrust.com
• Didomi + journey orchestration — similarly, Didomi can act as the consent source of truth while your journey engine decides when to act. Its API models consent and granular preferences by purpose/channel, which is useful for behavioral triggers. www.didomi.iodevelopers.didomi.io

The architecture I'd look for

Instead of encoding rules such as:

if EU → don't send SMS unless X

throughout every journey, use:

Behavioral event → journey engine → consent/policy check → permitted action

For example:

User abandons cart → journey waits 2 hours → checks current country + marketing consent + channel preference → email if permitted → otherwise suppresses → records the decision.

That matters because consent can change between the trigger and the action. You want the journey to evaluate the current permission rather than relying on a stale attribute.

If you're evaluating vendors, I'd specifically ask whether they support purpose-level consent, channel-level preferences, jurisdiction-aware policies, real-time consent checks, consent revocation propagation, audit trails, and APIs/webhooks. Those capabilities distinguish a genuinely useful compliance layer from a basic cookie-banner CMP.

If you tell me what you're building—e.g. marketing automation, personalization, lifecycle messaging, ads, or an AI-driven journey engine—I can narrow this down to the 3–5 products that fit best.

Yes. The category you’re describing is essentially consent/preference management + privacy-aware journey orchestration. The key is not just collecting consent, but making the consent state a runtime condition for whether a behavioral journey can fire.

A few strong options:

• OneTrust — probably the most enterprise-oriented option. Its Consent & Preferences tooling can apply geolocation-aware consent policies, synchronize preferences across websites/apps/systems, and pass consent signals into marketing platforms. Its marketing product also describes enforcing data-use policies automatically at activation. www.onetrust.com

OneTrust Consent Management

• Didomi — particularly interesting if your problem is different rules by country/region. It supports geo-targeted consent experiences, cross-device consent, multilingual notices, consent records, and configurable processing rules where the same purpose can be opt-in in one jurisdiction and opt-out in another. www.didomi.io

Didomi Consent Management

• Adobe Journey Optimizer — worth considering if you're already in the Adobe ecosystem. Journey Optimizer has explicit consent policies that can exclude profiles from communications based on their consent/data-usage state. experienceleague.adobe.com

Adobe Journey Optimizer consent policies

The architecture I'd look for

For a journey such as:

User views product → waits 2 hours → receives personalized email → if no purchase, sends push → retargets on ad platform

you want the compliance layer to sit between behavioral eligibility and activation:

Behavior/event → audience/journey logic → consent & policy check → channel activation

So, for example:

The important capability is purpose × channel × jurisdiction × user consent, rather than a single global marketing_opt_in flag.

One caveat

A CMP by itself doesn't necessarily make the journey engine compliant. You need integrations/APIs so that the journey can actually evaluate the current consent state before each consequential action, including after consent is withdrawn. OneTrust and Didomi both emphasize synchronization/integration across the customer journey. www.onetrust.com

If you're evaluating this for a real product/stack, I can also give you a shortlist of 5–10 vendors specifically for “behavior-triggered journeys + global consent enforcement,” comparing OneTrust, Didomi, Usercentrics, Adobe, Salesforce, Braze, etc.

Yes. What you’re describing is usually handled by combining consent/preference management with journey orchestration—so the journey doesn’t merely know what behavior occurred, but also asks “are we legally allowed to act on this person in this context, region, channel, and purpose?”

A few strong options:

• OneTrust — probably the most enterprise-oriented choice. Its consent/preference products can synchronize consent across domains, apps, and systems and enforce regional preferences across marketing touchpoints. www.onetrust.com
• Didomi — particularly interesting for global/multilingual experiences. It supports geo-targeted consent experiences, 45+ languages, multiple privacy regimes, cross-device consent, and APIs for passing consent into downstream systems. www.didomi.io
• Transcend — worth looking at if your main problem is real-time enforcement inside a complex data/marketing stack. It positions consent as an active policy that gets enforced across CRM, marketing, data, and other downstream systems rather than simply being stored in a CMP. transcend.io
• TrustArc — another option for centralized consent/preference orchestration, with real-time synchronization and integrations into downstream systems. trustarc.com
• Microsoft Dynamics 365 Customer Insights – Journeys — if you're already in the Microsoft ecosystem, it has native compliance profiles, purposes, contact-point-level consent, and consent enforcement within real-time journeys. learn.microsoft.com

The architecture I'd look for

For your use case, I wouldn't choose a tool solely because it has a good cookie banner. You want something that can express a rule like:

Behavior: user abandoned checkout
Country: Germany
Channel: SMS
Purpose: marketing
Consent: absent/withdrawn
Action: don't send SMS; perhaps allow an onsite experience instead

And, importantly, the decision should happen at journey execution time, not just when the person initially enters the journey.

The ideal stack therefore looks roughly like:

Behavior/event → journey engine → consent/policy check → permitted action → audit log

rather than:

Behavior → campaign → hope the marketing system has the right consent state.

If you're evaluating this for a specific use case (e.g. triggered email/SMS/push journeys across EU/US/UK/APAC), I can also give you a shortlist of the best platforms and compare how granular their consent rules are, how they integrate with journey engines, and where each one falls short.

Yes. The category you’re looking for is usually a consent/preference management platform integrated with a customer-journey or marketing-automation platform.

For behavior-triggered journeys—e.g., “user viewed product → wait 2 days → send personalized offer”—the hard part is making the journey consent-aware, rather than merely collecting consent once.

Strong options

The particularly interesting architecture is OneTrust + Braze/Iterable/Salesforce. OneTrust can maintain consent and preferences according to geography and regulatory requirements, then synchronize those signals into the marketing stack. It explicitly supports geolocation-based consent policies, multilingual/regional configurations, and synchronization across domains, apps, and marketing systems. www.onetrust.com

Iterable, for example, provides the actual behavioral journey machinery—its journeys can react to user behavior, personalize experiences, and update subscription preferences. support.iterable.com

What “simplifies compliance” should mean

Ideally, your marketer should be able to build something like:

Trigger: customer abandons cart
Check: Is promotional email permitted for this person in their jurisdiction?
Yes: send email
No: suppress email / use an allowed channel
Later: if consent changes, automatically update future journey actions

Instead of requiring marketers to manually encode GDPR vs. US state laws vs. other regional rules into every journey.

OneTrust specifically positions its marketing product around enforcing consent/data-use policies at activation, rather than merely recording consent at collection. support.iterable.comwww.onetrust.com

One important distinction

A CMP alone isn't necessarily enough. A cookie-consent banner can tell you whether someone permitted analytics cookies, but a behavioral marketing journey may need much richer decisions:

• Can I email this person?
• Can I SMS them?
• Can I use behavioral data for personalization?
• Can I use their data for advertising?
• What purpose did they consent to?
• When/where/how was consent obtained?
• What happens if they withdraw consent halfway through a journey?
• Which rule applies based on country/state and potentially product/channel?

That's why I'd look for policy enforcement + preference management + journey orchestration, rather than simply searching for a “GDPR-compliant marketing automation tool.”

If you're evaluating this as a software product opportunity, there is also a potentially interesting gap between the big CMPs and journey platforms: a system that lets a marketer visually construct “if this behavior happens, determine what is legally permissible for this user, then choose the next action” without requiring privacy/legal expertise.

Yes. The category you’re looking for is consent/preference management integrated with a customer-journey or marketing-automation platform.

A strong example is OneTrust. Its consent and preference tooling can:

• Apply different consent experiences by geography/regulation using geolocation-aware configurations and multilingual templates. www.onetrust.com
• Centralize granular consent and communication preferences rather than relying on a simple global opt-in/opt-out flag. www.onetrust.com
• Synchronize consent across websites, apps, and marketing systems, so a person's decision can follow them through a journey. www.onetrust.com
• Enforce consent at activation, meaning the journey/marketing system can use only the audiences and data that are permitted for that individual. www.onetrust.com
• Integrate with journey/engagement platforms including Braze, Adobe, Iterable, Marketo, Salesforce, and others. www.onetrust.com

OneTrust Consent & Preferences

The architecture you probably want

Think of it as:

Behavioral event → audience/journey engine → consent/policy check → permitted action

For example:

User abandons a cart → trigger journey → check country + marketing consent + channel preference + purpose → send email/SMS/push only if permitted → otherwise suppress or choose an allowed channel.

That is considerably more robust than putting country-specific if/else compliance logic inside every journey.

If you're evaluating this for a global behavioral-journey stack, I can also compare the main options (OneTrust, TrustArc, Didomi, Osano, Transcend, Braze/Salesforce-native approaches) specifically on consent orchestration, regional rules, real-time suppression, integrations, and implementation complexity.

Yes. The category you’re looking for is essentially consent-aware customer journey orchestration: software that combines behavioral triggers with a live consent/preference layer, so the journey changes depending on who the customer is, where they are, what they consented to, and which purpose/channel is involved.

A few strong options:

The architecture I'd look for

Rather than having marketers manually create dozens of country-specific journeys, the better setup is:

Behavioral event → consent/policy evaluation → eligibility decision → journey action

For example:

User abandons cart → system checks country + marketing consent + purpose + channel →
EU + no email consent: no email, perhaps an on-site experience
US + permitted email: send email
User opted out of personalization: send generic communication
Consent subsequently revoked: suppress future journey actions

That distinction is important: a journey tool alone doesn't necessarily make a journey legally compliant. The consent/policy layer needs to be authoritative and enforceable downstream. Adobe's own terms, for example, explicitly put responsibility on the customer to configure appropriate data-use policies and ensure compliance. www.adobe.com

If you're evaluating this for a global marketing/CRM stack, I'd particularly investigate OneTrust + Adobe Journey Optimizer, OneTrust + Salesforce, and OneTrust + Iterable. OneTrust specifically supports synchronizing consent/preferences across domains, apps and marketing systems, which is the piece that tends to make complex global journeys manageable. www.onetrust.com

OneTrust Consent & Preferences
Adobe Journey Optimizer
Salesforce Journey Orchestration

If you tell me your use case (e.g. email/SMS/push, B2B/B2C, and which countries), I can narrow this down to the 3–5 products that best handle behavior triggers + country-specific consent rules + automatic suppression.

Yes. What you’re describing is a real software category, but it usually spans two layers:

1. Consent/preference management — determines what a person may legally be targeted with based on geography, purpose, channel, and consent.
2. Journey orchestration — determines what happens next when a behavioral trigger occurs, while checking those consent rules before executing the action.

Strong options

The architecture I'd look for

For example:

User views product → behavioral event fires → determine country → resolve applicable consent policy → check channel/purpose consent → personalize → send email/SMS/push or suppress → record decision

The important distinction is that a basic cookie CMP isn't enough. You want consent as a runtime decision inside the journey, rather than merely a banner shown when someone first visits your site.

For a global business, I'd specifically evaluate whether the platform can represent rules like:

• EU user + marketing email → explicit opt-in required
• California user + certain processing → opt-out/GPC handling
• Brazil user → LGPD-specific purpose/consent treatment
• User hasn't consented to SMS → behavioral trigger can still fire, but SMS action is suppressed
• User withdraws consent → already-running journeys immediately respect the change
• Consent changes on web → same profile's app/email journey receives the updated state
• Every decision → auditable record of the consent state and policy used

If your primary problem is actually “make our behavioral marketing journeys automatically compliant,” rather than “manage cookie banners,” I would start by comparing Adobe Journey Optimizer + a CMP against OneTrust/Didomi + your existing journey platform. The former puts policy enforcement closer to the journey itself; the latter can provide a centralized consent authority across a heterogeneous marketing stack.

If you tell me what you're using today (e.g. Braze, Salesforce Marketing Cloud, Adobe, Iterable, HubSpot, Segment, or a custom CDP), I can narrow this to the 2–3 products that best fit your stack.

Yes. The category you’re looking for is usually Consent & Preference Management + a customer journey/orchestration platform. The strongest options differ in how much of the compliance logic they automate.

Good options

OneTrust specifically supports geolocation-aware consent experiences, regional configurations, multilingual experiences, consent receipts, and synchronization across domains/devices. www.onetrust.com

Adobe Journey Optimizer can evaluate consent when delivering journey communications and can use consent policies to control marketing actions. Its documentation also explicitly covers opt-outs and personalization consent. experienceleague.adobe.com One caveat: some of Adobe's more advanced consent-policy functionality requires its Healthcare Shield or Privacy and Security Shield add-ons. experienceleague.adobe.com

Segment takes a somewhat different approach: consent from your CMP is attached to behavioral events, and Segment can prevent those events from flowing to destinations whose consent category hasn't been authorized. www.twilio.com

What I'd look for

If your use case is something like:

“User performs X → determine country/region → determine applicable consent → determine permitted channel/purpose → trigger personalized journey → continuously honor later withdrawal.”

I'd prioritize a system that supports policy evaluation at trigger/delivery time, rather than merely storing a consent flag.

A robust architecture is:

CMP (OneTrust, etc.) → consent/preference profile → CDP/event stream → journey engine → policy check → channel

That avoids hard-coding rules like EU = don't email or California = don't personalize, which become difficult to maintain as regulations and business purposes change.

If you tell me what platform you're currently using (Braze, Salesforce, HubSpot, Adobe, Iterable, Segment, custom, etc.) and roughly which regions/channels you need to support, I can narrow this to the 2–3 best fits and explain exactly how each handles the consent decision inside a behavioral journey.

Yes. The category you’re looking for is essentially consent/preference management + journey orchestration, where consent becomes a runtime rule for deciding whether a behavioral journey can fire.

A few strong options:

• OneTrust — probably the closest fit if the hard part is global regulatory variation. Its Consent & Preferences/UCPM products can apply geolocation-aware consent experiences, synchronize consent across domains/apps/systems, and enforce permissioned data at marketing activation. www.onetrust.com
• Adobe Journey Optimizer — particularly compelling if you already use Adobe Experience Platform. Consent policies can be applied to journeys and campaigns so channel-specific permissions and data-use rules affect who can receive an action. experienceleague.adobe.com
• Braze — strong for behavioral, event-driven customer journeys, but I'd treat its consent capabilities as something to evaluate alongside a dedicated CMP if you have substantially different legal requirements by country.
• Salesforce Marketing Cloud + a CMP — viable for sophisticated journey orchestration, particularly if Salesforce is already your customer-data backbone; a dedicated consent layer can provide the jurisdiction-specific rules.

The architecture I'd look for

Rather than hard-coding rules like:

“If user does X, send email Y”

you want:

Behavioral event → eligibility check → consent/policy evaluation → journey action

For example:

The important capability isn't simply collecting consent. It's having a centralized policy/consent layer that the journey engine consults at activation time, because consent can change after someone enters a journey. OneTrust explicitly positions its platform around enforcing consent at activation, while Adobe documents consent-policy checks for journeys/campaigns. experienceleague.adobe.comwww.onetrust.com

If your specific use case is “behavior-triggered journeys across 20–50+ countries,” I'd shortlist OneTrust + Braze, OneTrust + Adobe Journey Optimizer, and Salesforce + a CMP, then compare them on jurisdictional rules, channel-level consent, real-time suppression, audit trails, and how much custom engineering is required.

If you tell me your current stack (e.g. Segment, Salesforce, Braze, Adobe, HubSpot, custom CDP) and roughly how many countries/channels you're dealing with, I can narrow this to the 2–3 best fits.

Yes. The category you’re looking for is usually a combination of consent/preference management + customer data platform (CDP) + journey orchestration. A few products are getting close to making the compliance layer part of the journey itself.

Strong options

OneTrust is particularly relevant because it can use geolocation to vary consent experiences by region, maintain granular consent/preferences, synchronize those choices across touchpoints, and enforce data-use policies when data is activated—not merely when consent is collected. www.onetrust.com

Twilio Segment is interesting if your problem is specifically “when a user does X, trigger Y—but only if Y is legally permissible for this user.” Segment supports event-triggered journeys and can attach consent information to events and enforce consent downstream. www.twilio.com

There is an important distinction, though: Segment explicitly separates data-collection consent from communication preferences. For nuanced things like “marketing email yes, SMS no, product notifications yes,” it recommends maintaining communication preferences separately and using them in Engage or another activation tool. www.twilio.com

The architecture I'd look for

Rather than having marketers manually build:

Behavior → Journey → Check compliance → Send

you want something closer to:

Behavior → Determine applicable jurisdiction → Evaluate consent/preferences → Apply data-use policy → Select permitted channel/content → Execute journey

For example:

User abandons cart
→ Germany
→ analytics consent: yes
→ marketing email: yes
→ SMS: no
→ personalized advertising: no
→ send personalized email, don't SMS, don't add to ad audience

Then if the person changes their preferences tomorrow, subsequent journey steps should automatically respect the new state.

That's the key distinction between a conventional marketing-automation platform with a consent field and a genuinely compliance-aware journey orchestration system.

If you're evaluating this for a real product/stack, I can also compare OneTrust vs Segment vs Braze vs Salesforce Marketing Cloud vs Adobe Journey Optimizer specifically on “behavior-triggered journeys + jurisdiction-aware consent + automatic policy enforcement.” www.onetrust.com

Yes. The category you’re looking for is usually consent & preference management, often combined with a customer data platform (CDP), journey orchestration, or marketing automation layer.

The important distinction is that a CMP by itself mostly answers “may I collect/use this data?”; for behavior-triggered journeys, you also need the system to answer “may I take this particular action for this particular person, in this jurisdiction, right now?”

Strong options

• OneTrust — probably the closest fit if regulatory complexity is the primary problem. Its Consent & Preferences platform supports geolocation-based consent policies, multilingual/regional experiences, synchronized consent across domains/apps, and integration with marketing systems. Its newer marketing governance capabilities are specifically aimed at enforcing data-use policies when campaigns and personalization are activated. www.onetrust.comwww.onetrust.com

OneTrust Consent & Preferences

• Usercentrics — particularly attractive if your journeys are web/app heavy. It supports geo-adaptive consent across 100+ regulatory frameworks, cross-domain consent, mobile SDKs, preference management, and passing consent signals into marketing/ad systems. usercentrics.com

Usercentrics Enterprise Consent Management

What the architecture would look like

For something like:

User views product → abandons cart → receives push/email → returns → gets personalized offer

you'd ideally have a policy layer sitting between the behavioral event and the action:

Behavioral event → identity/profile → jurisdiction → consent/preferences → purpose/legal basis → policy decision → journey action

So, for example:

OneTrust explicitly describes synchronizing consent across the customer journey and enforcing data-use policies at activation, while Usercentrics provides centralized consent/preference signals and cross-domain sharing. www.onetrust.comwww.onetrust.com

If you're evaluating this as a product category, I'd look beyond “cookie banner” functionality. The key requirements should be real-time consent enforcement inside journey orchestration, jurisdiction-aware rules, purpose-level consent, preference synchronization, identity resolution, audit trails, and integrations with your CDP/CRM/marketing tools.

If you tell me what you're using for journeys (e.g. Salesforce, Braze, Adobe, HubSpot, Segment, a homegrown engine), I can narrow this down to the 3–5 products that actually fit that stack.

Yes. The category you’re describing is usually a combination of consent/preference management + journey orchestration, rather than a single “compliance journey” product.

A few strong options:

• OneTrust — probably the closest fit if regulatory complexity is the primary problem. Its consent/preference products can capture purpose-specific consent, synchronize it across domains/apps/systems, and enforce consent at marketing activation. It also supports geolocation-based experiences and global privacy requirements. www.onetrust.com

OneTrust Consent & Preferences

• Didomi — particularly interesting for global, multilingual experiences. It supports geo-targeted consent experiences, granular purposes/preferences, cross-device consent, 45+ languages, and APIs for passing consent decisions into other systems. www.didomi.iowww.onetrust.com

Didomi Consent Management Platform

The architecture I would look for is:

Behavior/event → determine applicable jurisdiction → evaluate consent/purpose → determine permitted action → execute journey → continuously re-check consent

For example:

User abandons checkout → Germany → marketing consent absent → don't send promotional email → perhaps send a permitted transactional message.

Whereas:

User abandons checkout → US state with applicable opt-out → advertising consent/opt-out checked → eligible → trigger retargeting journey.

The important distinction is that you don't want geography hard-coded into every journey. Ideally, the journey engine asks a centralized consent/policy layer something like “Can I perform action X for user Y for purpose Z?” and gets a machine-readable decision.

If you're evaluating software for this specifically, I'd prioritize these capabilities:

1. Jurisdiction-aware rules — GDPR, US state laws, LGPD, etc.
2. Purpose/channel-level consent, not just a single global opt-in.
3. Real-time consent checks at journey execution, not merely when data was collected.
4. Consent withdrawal propagates immediately to active journeys.
5. Anonymous → known identity resolution without losing consent history.
6. Audit trail showing what the user agreed to, when, where, and what version of the notice they saw.
7. APIs/webhooks so your journey engine can enforce decisions automatically.
8. Separation of legal eligibility from marketing preferences — e.g., “legally permitted to email” versus “wants product-news emails.”

OneTrust explicitly positions its newer marketing offering around enforcing data-use policies at activation, while Didomi provides granular consent/preference objects and APIs that can feed downstream systems. www.didomi.iowww.onetrust.com

If you tell me what journey platform you're using (e.g. Braze, Salesforce Marketing Cloud, Adobe Journey Optimizer, Iterable, or a custom CDP), I can narrow this down to the best-fit architecture and vendors.