Customer Insights – Journeys Consent Management: Compliance Profiles, Purposes, Topics, and Preference Centers

Every marketing team wants to send relevant communications to the right audience. The challenge is making sure those communications align with the preferences customers have already shared.

As marketing operations grow, managing consent becomes more complicated. New campaigns are launched, subscription options expand, and different teams may need to communicate with the same audience. Without a clear approach, it can become difficult to understand who should receive what and why.

Customer Insights – Journeys provides a flexible framework for managing communication consent at scale.

In this guide, we’ll explain how consent is managed in Customer Insights – Journeys, including compliance profiles, purposes, topics, preference centers, enforcement models, and multi-brand considerations. 

How Consent Is Structured in Customer Insights – Journeys

Customer Insights – Journeys uses several connected components to manage how consent is captured, stored, and enforced. Each plays a different role in determining who can receive communications and which preferences customers can control.

At a high level, the consent structure includes:

• Compliance Profile: Establishes the overall consent framework for your communications.
• Purpose: Defines why you’re communicating with someone.
• Enforcement Model: Determines how consent requirements are applied for each purpose.
• Topics: Provides more specific communication choices beneath a purpose.
• Contact Point Consent: Stores consent for a specific communication destination, such as an email address or phone number.
• Preference Center: Gives customers a place to review and update their communication preferences.

Together, these components create the foundation for managing consent in Customer Insights – Journeys. The key to good governance is understanding how they relate before deciding how your organization should configure them.

Compliance Profiles: The Foundation of Consent Management

Think of a compliance profile as the container for your consent structure in Customer Insights – Journeys. Every marketing message is associated with a compliance profile, which defines how consent is managed. It also contains key settings such as your company address and associated purposes and topics.

An organization may create separate compliance profiles for:

• Different brands
• Different geographic regions
• Different lines of business
• Different regulatory requirements

Each compliance profile can have its own preference center, branding, company information, and consent settings.

Purposes: Why You’re Communicating

Purposes define the primary reason you’re communicating with a customer. They answer the question: “Why is this person receiving this communication?”

Customer Insights – Journeys includes three standard purpose types by default:

1. Commercial: Promotional communications (e.g., product announcements, newsletters).
2. Transactional: Expected communications (e.g., order confirmations, service notifications).
3. Tracking: Tracking interactions and behavior (e.g., link clicks, email opens).

Purposes also provide flexibility for organizations with multiple brands, regions, or lines of business. A purpose can be shared across multiple compliance profiles, allowing organizations to manage consent consistently while offering different preference center experiences.

Customer Insights – Journeys Enforcement Models Explained

Enforcement models determine whether messages can be sent when consent information is missing. These settings are configured at the purpose level, meaning different purposes can enforce consent in different ways.

There are three enforcement models:

1. Restrictive: Requires explicit consent before commercial communications can be sent. If consent doesn’t exist, Customer Insights – Journeys treats the recipient as opted out.
2. Non-Restrictive: Assumes communication is permitted until a recipient opts out. If no consent record exists, messages can still be sent.
3. Disabled: Doesn’t evaluate consent before sending communications.

Choosing the right enforcement model affects both customer experience and compliance risk. The best option depends on your organization’s communication strategy, regulatory requirements, and approach to consent management. Because these decisions can have legal implications, organizations should consult their legal and compliance teams when defining enforcement models.

Topics: What You’re Communicating About

If purposes define why you’re communicating, topics define what you’re communicating specifically.

Topics sit beneath a purpose and give subscribers more control over the types of content they want to receive. Each topic belongs to a single purpose, allowing organizations to offer more granular preferences without creating additional purposes.

Let’s look at an example.

Purpose: Commercial Communications

Topics:

• Product Announcements
• Events and Webinars
• Industry Insights

A subscriber might be interested in events and webinars but not product announcements. Topics allow them to tailor their preferences without opting out of all commercial communications.

A good rule of thumb is this: if a customer would reasonably expect the topic to exist a year from now, it’s probably a good candidate. If it’s tied to a specific campaign, event, or short-term initiative, it probably isn’t.

For example, “Events and Webinars” is a sustainable topic. “2027 Spring Customer Success Webinar Series” is not.

Contact Point Consent: The Destination of Your Communication

Contact point consent is often the most misunderstood part of the Customer Insights – Journeys consent model.

Many marketers assume consent is stored on a contact or lead record. In reality, Customer Insights – Journeys stores consent at the contact point, meaning the actual destination where communications are delivered, such as an email address or phone number.

People can have different preferences for different contact points. A customer may want marketing emails at their work address but not their personal address. Another customer may opt into email communications but not SMS messages. Contact point consent allows Customer Insights – Journeys to manage these preferences independently.

The governance takeaway: consent lives with the email address or phone number receiving the communication, not the entity record.

Preference Centers: Where Subscribers Manage Consent

A preference center gives subscribers a place to review and update the types of communications they receive, and which contact point receives it.

This is where your governance decisions become visible to customers.

Every purpose and topic you create has the potential to appear on a preference center. That’s why it’s important to design consent options with the customer experience in mind. If subscription categories overlap or topic lists become too large, customers may struggle to understand their choices.

It’s important to note that preference centers don’t automatically update legacy fields such as DoNotEmail, DoNotBulkEmail, or DoNotTrack.

Offer only the choices your organization can consistently interpret, honor, and maintain over time. The goal is to give customers meaningful control while keeping your consent model understandable and sustainable.

Preference centers also support multi-brand consent, so you can manage consent independently for each line of business.

Multi-Brand Governance: When to Use Compliance Profiles and Business Units

For a single-brand organization, one compliance profile may be enough to manage consent across your marketing operations. For multi-brand organizations, the structure depends on how independently each brand or line of business needs to operate.

The key question is: Do your brands or lines of business need data isolation?

When Compliance Profiles Are Enough

If brands can share contacts, leads, and marketing operations, separate compliance profiles may provide enough separation. Each brand can maintain its own purposes, topics, branded preference center, and email experience without separating the underlying customer data.

This approach also allows a common marketing team to create segments and journeys for individual brands or across brands. Communication purposes can even be shared across compliance profiles when you want customers to manage broader preferences across the organization.

For example, two brands may share many of the same customers and want opportunities to cross-sell. Separate compliance profiles allow each brand to maintain its own consent experience while still working from shared customer data.

When You Need Business Units

Business units become important when brands or divisions shouldn’t share data.

Their primary function is controlling access to records based on the user and record owner. This makes business units appropriate when separate divisions have their own products, customers, segments, or strict data-access requirements.

In this model, each business unit can have its own compliance profile and independently manage its compliance settings, segments, journeys, emails, and other marketing activities.

Complex organizations can also combine both approaches. For example, business units can separate operations that require strict data isolation, while multiple compliance profiles within a business unit support brands that can share data but need distinct consent experiences.

The governance takeaway:

• Business units define data access boundaries.
• Compliance profiles define consent and preference experiences.

Having multiple brands doesn’t automatically mean you need business units. Start with the boundaries you need to enforce, then choose the simplest structure that supports them.

Other Customer Insights – Journeys Governance Controls

Consent architecture is a key part of Customer Insights – Journeys governance, but it’s not the only control available. The platform also includes settings and safeguards that help organizations manage when, how, and to whom communications are sent.

Some additional controls to consider include:

• One-Click Unsubscribe: Allows customers to unsubscribe from emails without leaving their email application.
• Quiet Times: Defines periods when messages shouldn’t be sent to customers.
• Frequency Caps: Limits the number of messages customers receive within a defined period.
• Suppression Lists: Prevents messages from being sent to harmful recipient addresses, such as hard bounced email addresses.
• Matching Rules: Determines how form submissions match and update existing lead and contact records.
• Double Opt-in: Requires subscribers to confirm their subscription by clicking a link sent to their registered email address.

Every organization will configure these controls in different ways. What’s important is understanding each one and making intentional decisions about how they support a compliant communication strategy.

Build a Customer Insights – Journeys Environment You Can Govern

Customer Insights – Journeys gives organizations flexibility in how they manage consent, customer preferences, and communications. But flexibility doesn’t mean every available setting needs to be used.

Good governance starts with understanding how the technical pieces work together and configuring them intentionally. Keep your consent structure as simple as possible. Use purposes and topics to create meaningful choices. Configure enforcement models based on your business requirements. Introduce additional compliance profiles or business units only when there’s a clear need.

Then look beyond consent. Controls like quiet times, frequency caps, and matching rules can help govern how Customer Insights – Journeys operates across the customer experience.

The goal isn’t to build the most sophisticated configuration. It’s to build one your customers can understand and your team can confidently manage as your marketing operations evolve.

Don’t navigate Customer Insights – Journeys alone. Contact the marketing automation experts at C5 Insight.