Responsys- Building Multibrand/Language

Building Multi Brand and Language Setup in Responsys

One guest. Many brands. Hundreds of hotels. Dozens of countries and languages. How do I manage all this!

This is the everyday reality of marketing for a global hotel group - managing multiple brands, operating across markets, and meeting guest expectations for the right message in the right language, every time.

At the same time, consolidation is accelerating. Platforms must scale globally and adapt quickly - often within days - without adding complexity or slowing the business down.

What is the problem?

The challenge isn’t channels or campaigns.

The real challenge is structure.

Marketing platforms are built for:

One brand
One market / language
One simplified customer view

When applied to global hospitality, that model breaks.

Hotel groups are forced into:

Duplicated guest profiles per brand or country
Fragmented data models across systems
Separate campaigns per language and market (Nightmare!)
Increasing governance overhead as scale grows

What starts as “local flexibility” quickly becomes operational debt.

Solution

This is where Oracle Responsys takes a fundamentally different approach.

Responsys is built to absorb complexity, not avoid it.

Instead of forcing all data into a single structure, Responsys uses a layered and extensible data model (See this article).

A central profile list
At the center of the data model sits a central Profile List — the single source of truth for the guest. It represents one stable identity across brands, hotels, and markets, ensuring that every interaction is tied back to the same person.

This foundation holds the core attributes needed for consistent, global communication. Most importantly, it includes the guest’s preferred language, allowing communications to default automatically to the correct written language. It can also include time zone data, ensuring messages are delivered at the appropriate local time.

Typical fields found in the Profile List include:

Email address (primary key)
Customer ID / CRM ID
First name / Last name
Country of residence
Preferred language (used to identify written language in communication)
Time zone (used to decide when to push communication)

More dynamic or relationship-based attributes — such as loyalty status or membership information — are stored separately in Profile Extension Tables (PETs), keeping the core profile clean, stable, and scalable.

Profile Extension Tables (PETs)
In this particular setup, PETs are not required.

However, in most enterprise hospitality implementations, Profile Extension Tables (PETs) are typically used to store structured, relationship-based, or time-variant data that does not belong in the core profile.

Common examples include:

Loyalty & Membership details (tier level, points balance, enrollment history)
Next Stay information (upcoming reservation details for pre-arrival communication)
Last Stay data (most recent property, stay date, spend indicators)

PETs allow you to extend the guest profile without overloading the central Profile List, keeping the identity layer clean and structured while still enabling rich personalization and effective lifecycle marketing.

More on advanced PET strategies in a future article.

Supplemental tables to capture everything else needed
This is where multi-brand and multi-language magic happens. These tables are NOT about the guest - They model the world around the guest.

They are used to define all the context required to scale communication across brands, hotels, and markets, including:

Brand-specific assets such as logos, colors, fonts, and layout rules. These are typically applied through stylesheet-driven personalization, ensuring that each brand’s design system is reflected automatically.
Hotel-level information like descriptions, imagery, and contact details, - often maintained as language-specific datasets. This information is pulled dynamically into campaigns like pre-stay, confirmation, in-stay, and post-stay journeys.
Localized language content to ensure all general elements are fully translated and compliant — including headers, footers, navigation links, and required legal text that must remain consistent across markets.
Dynamic content elements that eliminate the need to edit campaigns directly. By storing content components in data tables, variations are automatically inserted based on language, brand, market, or segmentation attributes — keeping campaigns clean and reusable.

All of this context lives in data — rather than in duplicated campaigns or cloned templates — enabling global scale without operational overhead.

Advantages in a Structured Approach

A structured architecture does more than organize data — it enables scale without chaos.

When guest identity, brand context, language logic, and dynamic content are modeled correctly, the benefits are clear:

Scalability without duplication Campaigns are built once and reused across brands, hotels, and markets — powered by data, not cloned templates.
Consistent brand governance Visual identity, legal elements, and compliance rules are enforced automatically through structured data and dynamic logic.
Faster time to market Adding a new brand, hotel, language, or market becomes a data exercise — not a campaign rebuild.
Reduced operational overhead No need for separate workflows per country or language. Fewer errors. Less manual maintenance.
Improved personalization at scale Language, brand, segmentation, and lifecycle triggers work together through deterministic logic.
Future-ready flexibility Integration with systems like OPERA Cloud via OHIP enables real-time updates without breaking the model.

In a structured approach, complexity doesn’t multiply as you grow.

It becomes manageable. Predictable. Scalable.

Bringing It All Together

The result is a single platform where one guest, many brands, many hotels, and many markets can be managed coherently—without fragmentation, duplication, or loss of control.

Let’s bring it all together: with the right structure in place, even complex challenges become manageable.

If you're facing multi-brand or multi-language complexity, let’s schedule a call and walk through a practical solution.

Written by: Henrik Jochumsen