This is part 2 of a two-part guide to designing a multi-audience corporate website on Drupal. Part 1 covers audience research, navigation strategy, and content structure. Part 2 covers user journeys, smart contact forms, and content personalization.
A solid information architecture gets each audience to the right section. The next job is making what they find there feel like it was written for them, and routing them to the right action without a maze of forms.
Content personalization in Drupal means tailoring pages and paths to distinct audience segments without building a full customer data platform. Part 1 covered the foundation of a multi-audience website: identifying your audience segments, choosing a navigation strategy, and structuring content with a shared content model and an audience taxonomy. That work gets the right visitor to the right area. This post is about what happens next: designing the journey for each audience, building content personalization that stays pragmatic, and creating contact forms smart enough to route several user types correctly.
The aim throughout is pragmatic. You don't need a customer data platform or a machine-learning pipeline to serve three audiences well. You need clear journeys, well-built forms, and personalization applied only where the data justifies it. This post is written for Drupal architects, UX designers, and content strategists, and the Edenred examples reflect a planned form-and-journey redesign rather than a shipped build.
In this article:
- What does the ideal journey look like for each audience?
- How do you build a smart contact form for multiple audiences?
- How do you personalize content without complexity?
- How do you measure success per audience?
What does the ideal journey look like for each audience?
Personalization is meaningless until you know where each audience is trying to go. Before tailoring a single paragraph, map the ideal journey for every segment, from entry point to the one action that matters most for that group.
Take Edenred's three audiences. Each has a distinct path:
- Business client: learn about products, then compare options, then request a quote, ending at a contact or quote form. This is a research-and-evaluation journey, often spanning multiple visits.
- Cardholder: find support, manage an account, and access resources. This is a self-service journey, usually short and task-focused, where speed to answer matters more than persuasion.
- Merchant: review partnership information, submit an application, and reach onboarding materials. This is a qualification-and-conversion journey with a clear application step.
For each journey, define two things explicitly. First, the entry points: where does this audience actually arrive? A business buyer may land on the homepage or a product page from a search or an email campaign; a cardholder usually arrives via Google or a direct link looking for support; a merchant may come from a partnership page or referral. Entry points determine where you must repeat audience cues, because not everyone starts at the homepage.
Second, the conversion point: the single desired action for that group. Quote request for the business buyer, successful self-service for the cardholder, application submission for the merchant. When every page in a journey is built to nudge toward that one action, personalization decisions become obvious, because you are always asking "does this move this audience toward their conversion point?"
Mapping journeys this way also reveals where journeys diverge and where they share steps, which directly informs both your form design and how much personalization each path actually needs.
Read also: multi-audience website, part 1: information architecture and navigation in Drupal and component mindset: teaching clients to think in components.
How do you build a smart contact form for multiple audiences?
Contact is where multi-audience sites most often break. A single generic form forces three different users into one set of fields, while three completely separate forms scattered across the site create navigation problems and duplicated maintenance. The goal is a form that routes each user type correctly without making anyone learn your internal categories.
The proven UX pattern is a self-identification step at the top: an "I am a..." selector with plain-language options ("I want to buy cards for my company," "I'm a cardholder and need help," "I want to accept Edenred cards"). The wording matters enormously. Label the options by what the user is trying to do, not by your internal segment names, because a visitor knows their goal but may not know whether they're a "merchant" or a "partner."
From that selection, the form adapts. Drupal's Webform module supports exactly this with conditional logic: fields appear or hide based on the audience choice, so a business buyer sees company size and product interest, a cardholder sees account and issue type, and a merchant sees business details and locations. Webform handles conditional fields, multi-step flows, and advanced validation directly in its admin interface, without custom code, and can route each submission to the right team via conditional email handlers.
Two practical guidelines:
- Avoid making users understand your org chart. Every label, option, and help text should reflect the user's perspective and vocabulary, never your internal structure. The moment a user has to guess which category they fall into, you've added friction at the highest-stakes point of the journey.
- Know when to split. A single conditional form is usually best because it keeps one entry point and one maintenance surface. But if the three journeys diverge so completely that the shared form becomes a tangle of conditions, separate forms per audience, reached through clear navigation, are the cleaner choice. Let the complexity of the conditional logic, not dogma, make the call.
How do you personalize content without complexity?
Personalization has a reputation for being expensive and over-engineered. For most multi-audience sites it doesn't need to be. The pragmatic principle: start with good information architecture, and add personalization only where real data shows it pays off. Work up the ladder of complexity only as far as the evidence justifies.
A clarification on scope: this post is about personalizing the public site for anonymous or self-identified visitors, where you tailor content to broad audience segments before anyone logs in. Once a user authenticates, you can personalize far more precisely against their own account data - pricing, targets, orders - which is a different problem with different access-control requirements. We cover that authenticated, per-user case in our guide to building a Drupal extranet.
Audience-specific landing pages. The simplest and often most effective form of personalization is dedicated landing pages per audience, each with tailored messaging and a call to action pointed at that group's conversion point. No special technology required, just the shared content model and audience-aware reusable components from Part 1. This alone delivers most of the benefit of personalization for most sites.
Paragraph-level personalization. One step up, keep a shared page structure but swap or highlight specific components per audience: the same product page that surfaces volume pricing for business buyers and support links for cardholders. Because the page is built from paragraphs, you can vary individual sections by audience without duplicating the whole page.
Session or cookie-based memory. When a visitor self-identifies, once through navigation, a form, or an "I am a..." choice, remember it for the session and adjust subsequent pages: emphasize their section in navigation, surface their resources, default their forms. This is light, privacy-friendly personalization that meaningfully smooths a repeat journey.
Advanced, data-driven personalization. Drupal has modules for rule-based and behavioral personalization, and tooling such as Fields and Views can segment content by buyer persona and funnel stage. Reach for these only when you have the traffic and analytics to support the added complexity. Going "full CDP" before the data demands it is how personalization projects stall.
The discipline is to climb only as high as your evidence reaches. Most multi-audience sites get the majority of the value from the first two rungs.
Read also: Drupal extranet: how to build a secure portal for clients, partners, and sales teams and 9 functions a modern CMS should have to increase marketing team productivity.
How do you measure success per audience?
A multi-audience site can look healthy in aggregate while quietly failing one group. The only way to know is to measure each audience separately, against its own goals, and iterate on what the numbers show.
Set audience-specific goals. Define a distinct conversion goal per segment in your analytics: quote requests for business buyers, successful support self-service for cardholders, application submissions for merchants. A single site-wide conversion metric hides exactly the per-audience problems you need to find.
Track self-identification accuracy. Where users choose an audience, in navigation or in the "I am a..." form step, measure whether they pick correctly. High rates of switching paths, abandoning after a choice, or submitting through the wrong route signal that your labels speak your language instead of the user's.
Compare conversion rates across segments. Watch each audience's conversion rate independently over time. A lagging segment points to a journey, content, or form problem specific to that group, which a blended number would mask.
Analyze navigation patterns. Look at whether each audience reaches its key content efficiently or wanders. Long, looping paths to a cardholder's support article or a merchant's application form reveal information-architecture gaps that Part 1's testing methods, card sorting and tree testing, can then help you fix.
Iterate on audience-specific data. Feed everything back into refinement. Adjust labels, journeys, form logic, and personalization based on how each group actually behaves, not on assumptions. Serving multiple audiences well is a continuous loop of measure, learn, and adjust, run per segment rather than for the site as a whole.
Building a multi-audience experience on Drupal?
This two-part series reflects our approach to a multinational benefits company whose Drupal site must serve business buyers, individual cardholders, and merchant partners at once, where a redesign of journeys, contact forms, and personalization is part of the planned roadmap. The throughline is pragmatism: clear per-audience journeys, smart Webform-based routing, and personalization applied only where the data earns it.
If your site serves several audiences and conversions are uneven across them, the answer usually lies in journeys, forms, and targeted personalization rather than a bigger marketing platform. Our team specializes in building multi-audience Drupal experiences that route each user to the right action without unnecessary complexity. Visit our Drupal development services to discuss your own setup.
