Personalization patterns

Personalization is a digital marketing tactic where priority audiences are intercepted through targeting. Those audiences can be account-, demographic-, behavioral-, lifecycle-, or intent-based. Our goal is to provide visitors with the best next action when browsing our websites as well as meet their specific needs and progress them through the customer lifecycle.

For more information about how personalization works, the team, and our vision for the future, read the source deck.

Dialog

Dialog

Sticky banner

Sticky banner

Sticky card

Sticky card

Announcement

Announcement

Card

In-page card

Tabs

Active tab

Alert

In-page alert


Before jumping into personalization, have answers to these questions ready first.

  • What audience are you trying to target?
  • How large is the audience?
    • Reference the Go/No go estimator to calculate and determine the viability of your project.
  • What do you want that audience to do?
  • What would success look like for this audience?
  • What type of experience(s) do you want to use?
  • Are any tests or personalizations already running on the page you are working on?

A Dialog displays content in a container which sits on top of the page and darkens any content underneath. This is a priority 1 implementation as it prevents a user from completing a task or interacting with the rest of the page until they close the dialog.

Design

A dialog can be used both on desktop and mobile.

Dialog

How to use

  • Use sparingly as it interrupts the workflow of a user, requires immediate attention from a user, and distracts a user from completing their current task.
  • A best practice is to trigger a dialog only when a user interacts with the appropriate element, never on its own. For instance, show a dialog if a user selects something and then needs to complete a more important task. If that is not ideal or possible, show it once a user has completed their task.
  • Refrain from presenting a dialog while a user is likely to be in the middle of an important task.
  • Per our design system, every dialog should include a close button. It should also close when a user clicks outside of the dialog and when the Escape (esc) key is pressed.
  • Messaging within a dialog should be simple, do not include multiple steps or long forms.
  • A dialog can be used on mobile, but a user might have a hard time closing it on a small screen.

The audience

A dialog can be used for the following types of content (among others).

  • Product announcements
  • Notifications related to any previous user actions
  • An experience that ideally does not direct a user away from their task or the page

A Sticky banner displays a secondary offer without interrupting the experience of a user. It sticks to the bottom of the screen and overlays existing content.

Design

  • If a sticky banner links to a set of assets (like in Pathfactory), a placeholder image can be displayed describing what the user gets.
  • If a sticky banner links to specific assets, a resource icon can be displayed instead of the Pathfactory image.
  • The headline should not wrap, 35 - 40 characters or fewer is acceptable.
  • The body text should not wrap beyond more than two lines; 85 - 110 characters or fewer, depending on how the first line wraps, is acceptable.
  • A user should be able to permanently close a sticky banner and that same sticky banner should not reappear when they return.
Sticky banner

How to use

  • A sticky banner slides up from the bottom of the page. We often require a user to scroll past the fold before revealing a sticky banner to avoid interfering with the primary hero message.
  • Decide on which pages will display a sticky banner. We typically do not show a sticky banner on landing pages like the Solutions pages and Thought Leadership article pages.
  • Design a sticky banner to explicitly tell a user what they will receive if they make a selection. For example, include an image that visually describes the resource and write content to be specific to the resource.
  • The Drift chatbot icon appears on top of everything, so avoid creating a design that spans the entire width of a sticky banner to avoid a conflict.

The audience

  • A sticky banner can be displayed to a user who has shown interest in a product or topic, but have not converted yet.
  • We recommend the audience be large enough so that a click-through rate of under 10% is sufficient to meet goals.
  • Expect a fairly high close rate, based on initial trials, in the 40% range.

A Sticky card is a single page or cross-page offer that persists on the side of the screen.

Design

A sticky card can include a title, headline, body text, and call to action, but not all of these elements are required in the same sticky card. It can function in a couple of different ways depending on the primary goal of the page.

  • Less interruptive
    • On pages where the primary goal is to support reading and learning, a sticky card will slide in from right to left after the visitor has scrolled past 1,000 pixels. It will remain in a fixed position so it follows a user down the page.
    • On mobile, a sticky card will appear inline on the page. For example, there is an example of a less interruptive sticky card on article pages.
  • More interruptive
    • On pages where the primary goal is to present a user with a personalized offer, a sticky card will slide in from right to left once the visitor has scrolled past the hero.
    • On mobile, a sticky card will be shown as an overlay which is the same as on desktop. For example, show a sticky card on pages after a user has taken an action indicating they have an interest in a certain subject in order to present a resource they may be interested in.
Sticky card

How to use

  • A sticky card should promote a resource or event and the only acceptable elements are a title, headline, body text, and call to action.
  • A sticky card can be used on a single page or across a set of pages.
  • A sticky card is useful on pages that do not have a call to action in the hero or near the top of the page because it can be used to call attention to a personalized resource.

The audience

  • A sticky card can be displayed to a user who has shown interest in a product or topic, but have not converted yet.

An Announcement is a priority 1 personalization and should be used sparingly. It includes a skinny banner at the very top of a website above the navigation.

Design

An announcement can be used to display an important message at the top of a website, but is not limited to one page at a time. An announcement can either have a themed background image or solid color background. For colored backgrounds, we suggest using alert styles.

Announcement

How to use

  • If a logo is associated with an announcement, it should have a max width of 80px.
  • Headline or body text should be 60 characters or fewer.
  • Call to action text should be 20 characters or fewer.
  • Provide a link to the announcement if applicable.

The audience

Alert styles can be used for the following kinds of announcement content.

  • Important cross-website announcements - For top-tier press releases, company announcements, and important product launches, use a red or yellow background.
  • Single-page announcements - For global updates or important in-page content, use a green or blue background.

An In-page card is an existing card(s) within a page for personalization or targeting.

Warning
Only cards on the redhat.com home page are templated in Adobe Target. For a different card experience on other pages, new design and development work may be required.

Design

There are several versions of in-page offer cards depending on what kind of asset you need to promote.

  • Resource offer
  • Event/webinar offer
  • Page offer
  • Product card
Card

How to use

  • Find an existing card(s) within your page or set of pages you want to personalize.
  • Define the offer you are trying to promote (announcement, event, press release, webinar, etc.).
  • To automate the process of what you show a user, Adobe has pre-built technology to automatically personalize based on the attributes of a user or an algorithm based on content type. Please work with the Digital Systems Web Team if you are interested in this direction.

The audience

An in-page card should be relevant to the context of the page a user is currently on.


The Active tab is a simple experience applicable to any page that contains tabs. It aims to customize the visitor experience by highlighting a tab based on the interests of a user.

Design

Active tab uses the existing tab component design and only customizes the active tab within the tab set (no custom design work is needed).

Tabs

How to use

  • Choose your target audience.
  • Choose a tab that best aligns to that audience in order to provide a targeted experience to them.
  • Request the active tab experience be set for that audience and describe what goals you hope to accomplish by doing so.

The audience

An active tab design can be used for the following types of content.

  • Persona-based targeting
  • Lifecycle-based targeting
  • Product affinity targeting
  • Topic affinity targeting

An Inline alert is a single or multiple page offer that appears inline with page content.

Design

An inline-alert only includes text, but no images. It can also include a single or two links that direct a user to other pages.

Alert

If a user closes an inline alert, consider if or when it should be displayed again for the same user. It could be suppressed for a week, month, or forever depending on the goal of the project. The alert component in Adobe XD has two styles, normal and alternate, and either can be used.

How to use

  • Use when the goal is to show an inline message pertinent to the surrounding content.

The audience

An inline alert can be displayed to any appropriate audience group.


Custom patterns are not pre-established targeting opportunities. If you are interested in creating a custom targeting experience, please reach out to the design system team or via this form with the details of your request and they will help you to establish the framework for the new design.

© 2021-2024 Red Hat, Inc. Deploys by Netlify