/ /

Introduction to landing pages

Updated 4 days ago

Overview

lp intro.pngLanding pages give organizations a more flexible way to design and deliver tailored entry experiences for different audiences. Instead of relying on one shared Home dashboard for everyone, App managers and Landing page managers can create multiple landing pages for different roles, regions, business units, subsidiaries, or use cases. Each audience sees the experience that is most relevant to them.

Who this is for: App managers, admins, and Landing page managers.

Why Landing pages

Every Simpplr customer used to share a single Home dashboard. As organizations grew into multi-segment, multi-region, and multi-subsidiary structures, that one dashboard became a crowded catch-all. Regional communications, HR tasks, IT actions, and company-wide announcements all competed for the same real estate, and the most important updates often got buried.

Customers with segments worked around this by maintaining separate segment-level home experiences, but segment-based personalization has clear limits:

  • Coarse targeting, with only one segment per user

  • Harder to govern at scale

  • Locked to a rigid layout

Landing pages address these limits by turning the Home experience from a single shared dashboard into a flexible, audience-aware experience platform.

What Landing pages are

Landing pages are configurable experience pages designed for specific audiences. They make home experiences more relevant, easier to govern, and more adaptable for complex organizations.

In simple terms: Landing pages turn a one-size-fits-all Home experience into a flexible, audience-aware experience model.

With Landing pages, organizations can:

  • Create multiple pages for different audiences

  • Target experiences precisely, down to the page, section, or tile

  • Organize content in flexible, visually rich layouts

  • Delegate page ownership to designated managers

  • Provide the right entry point for each employee group

What you can do with Landing pages

Create multiple targeted landing experiences

Instead of one shared home, App managers can create multiple landing pages tailored to different audiences, business functions, regions, or user needs. Each page becomes a purpose-built entry point for a specific group.

Target audiences at three levels

Landing pages are built on audience-based access control (ABAC), which lets you target content at three levels:

  • Page level: Show or hide a whole page based on audience.

  • Section level: Show or hide a section within a page based on audience.

  • Tile level: Show or hide individual tiles based on audience.

This delivers highly personalized experiences without forcing you to build a separate page for every small difference between groups.

Design pages with a modern visual editor

The Landing page editor gives content managers full design control:

  • Drag-and-drop composition to arrange sections and tiles

  • Configurable section layouts, with the ability to resize and reposition tiles

  • Responsive previews across device sizes

  • Autosave, so work is not lost

  • Rich styling controls, including spacing, padding, and section- or tile-level styling

Editors can build pages that feel branded and engaging, rather than working within a rigid shared layout.

Extend the same design capabilities to Site landing pages

The same flexible layout and design capabilities are also available for Site landing pages, so you can create consistent, customizable site experiences. Sites continue to use a single landing page model as before, but that single page now benefits from the new editor and design controls.

Route users automatically based on audience

End users are routed to the most relevant landing page automatically, based on the audiences they belong to and the priority order set for pages. Users can also:

  • Navigate across the pages available to them

  • Personalize designated sections when an editor has enabled personalization

Delegate ownership with the Landing page manager role

A new Landing page manager role supports delegated ownership. Rather than relying on a small central team to manage every experience, App managers can assign Landing page managers to own and maintain specific pages. This spreads governance work and puts pages in the hands of the teams closest to each audience.

Manage landing pages in one place

A dedicated Manage landing pages screen gives App managers and Landing page managers a single place to:

  • Manage landing pages

  • Enable pages in the navigation

  • Manage the order of pages in the navigation

Your existing Home dashboard becomes your first landing page

When your instance moves to Landing pages, your existing Home dashboard is seamlessly migrated into the new framework as your first landing page. Nothing is lost, and everyone continues to have a working home experience from day one. From there, you can start creating additional audience-specific pages as needed.

Landing pages vs a shared Home dashboard

Area

Shared Home dashboard

Landing pages

Experience model

One shared experience for everyone

Multiple targeted experiences for different audiences

Flexibility

More rigid

More adaptable and visual

Personal relevance

Limited

Higher, based on audience targeting

Governance

Centralized and harder to scale

Supports delegated ownership

Targeting granularity

Segment level only

Page, section, and tile level

Scalability for complex orgs

Limited

Better suited for multi-region or multi-audience organizations

Where Landing pages help most

Landing pages are especially useful when different employee groups need clearly different starting experiences. Common examples:

  • A regional team needs a page with local updates, quick links, and region-specific resources.

  • A frontline audience needs a simple page focused on tasks and actions instead of corporate content.

  • A corporate audience needs a broader page with strategy, company news, and business-wide updates.

  • A business unit needs its own curated experience without affecting the default experience for everyone else.

What Landing pages help you do

  • Build audience-specific home experiences

  • Create cleaner entry points for different types of users

  • Separate global content from local or role-specific content

  • Reduce reliance on broad segment-based workarounds

  • Support more personalized and scalable experiences

What to keep in mind

Landing pages are designed to improve flexibility and targeting, but they should be planned carefully. Too many overlapping pages or unclear audience rules can make governance harder instead of easier.

  • Use Landing pages when there is a clear audience need, not for every possible variation.

  • Define page ownership up front, before pages start multiplying.

  • Keep audience targeting rules as simple as possible.

  • Design the default and audience-specific experiences intentionally.

  • Review the migration from your existing Home dashboard carefully for continuity.

Important: Overlapping audience rules can create ambiguity about which page a user sees. Set page priorities intentionally and test routing before rollout

Recommended approach

  1. Start with a clear default landing experience.

  2. Identify audiences that truly need a distinct page.

  3. Define ownership for each page, including which App manager or Landing page manager is responsible.

  4. Create simple, focused layouts for each audience.

  5. Set page priorities and audience rules.

  6. Review routing and audience rules before rollout.

  7. Test the experience from the perspective of a real user in each target audience.

Frequently asked questions

Q: Do Landing pages replace the Home dashboard?

Ans: Yes. Landing pages are designed to address the limitations of a single shared Home dashboard by introducing a more flexible experience model. Your existing Home dashboard is migrated into the new framework as your first landing page, so users continue to have a working home experience from day one.

Q: Who is Landing pages designed for?

Ans: The feature is intended for App managers and admins who manage employee experience design and governance. A new Landing page manager role also supports delegated ownership, so specific pages can be maintained by the teams closest to each audience.

Q: Which organizations benefit most from Landing pages?

Ans: Landing pages are especially useful for organizations that need different experiences for regions, business units, job functions, subsidiaries, or frontline and corporate audiences.

Q: Are Landing pages only for the Home experience?

Ans: No. The same flexible layout and design capabilities also extend to site landing experiences, while preserving the existing single landing page model for sites.

Q: How does audience-based access control work?

Ans: Audience-based access control (ABAC) lets you target content at the page, section, or tile level. You can show a whole page to one audience, or vary sections and tiles within a single page based on who is viewing it.

Q: Can end users personalize their landing page?

Ans: Users can navigate across the pages available to them and personalize designated sections when the editor has enabled personalization for those sections.

Q: Who can manage landing pages?

Ans: App managers and Landing page managers can manage landing pages from the dedicated Manage landing pages screen, where they can manage pages, enable pages in the navigation, and set the navigation order.

Was this article helpful?
Subscribe to receive updates on this article