Weblayers in scenarios

Weblayers are website banners that appear on your site based on customer behavior, profile data, or campaign logic. You can use them to show targeted messages — promotions, surveys, sign-up forms, or time-sensitive offers — without interrupting the rest of the page experience.

Adding weblayers to scenarios connects them to your broader customer journey. Instead of running weblayer campaigns in isolation, you can trigger them as part of a workflow that already includes email, SMS, and mobile push. A customer who ignores an email can see a related banner the next time they visit your site, all within the same scenario flow.

📘

Note

This feature requires the Web Personalization package. Contact your Customer Success Manager (CSM) to enable it for your project.

Why use weblayers in scenarios

Weblayers in scenarios let you reach customers at the right moment, on the right channel. Here are the most common ways to use them:

  • Follow up on missed emails: Show a related banner to customers who didn't open your email, giving your promotion another chance to be seen.
  • Recover abandoned carts: Display reminders when customers with items in their cart return to your site.
    Create urgency: Use countdown timers for sales and limited-time offers to drive faster action.
  • Grow your audience and data: Collect customer data or encourage newsletter sign-ups by offering incentives through weblayers.
  • Run coordinated campaigns: Keep messaging consistent across email, mobile, and web for events like Black Friday.

Add weblayers to scenarios

  1. Go to Campaigns > Scenarios.
  2. Click New Scenario, then Create New Scenario in the dialog.
  3. Under Actions, click Weblayer to add a weblayer node.
Scenario editor showing the Actions panel with the Weblayer option highlighted, and an arrow pointing to it in the left navigation menu.
  1. Double-click the weblayer node to edit it.
  2. Choose a template:
    • Blank template: Start from scratch.
    • Project templates: Use templates you've already created for your project.
    • Predefined templates: Select from ready-made templates.
📘

Note

Non-personalized weblayers aren't available in scenarios. This option is only available in standalone weblayer campaigns.

  1. Go to the Settings tab to configure your weblayer:
    1. Set your target audience in Entry criteria
    2. Adjust timing and display rules in Display settings
  2. Go to the Design tab to build your content.
  3. Click Save.

Configure your weblayer

In the Settings tab, define your weblayer's audience, display rules, and performance settings. Weblayers in scenarios only target users who reach the weblayer node — they can't expand beyond your scenario's original audience.

Entry criteria

Entry criteria controls who can see your weblayer. You have two filtering options:

  • Consent category: Show the weblayer only to customers who've given specific types of consent. Choose from your existing consent categories or create custom ones based on your privacy requirements.
  • Customer filter: Narrow your audience by adding conditions based on customer behavior, profile data, or funnel progress—for example, customers who abandoned their cart in the last 24 hours or VIP members in a specific location. Click + Add filter condition to build these rules.
Weblayer Settings tab showing the Entry criteria section with a Consent category dropdown and a Customer filter section with an Add filter condition button.

Display settings

Display settings controls when and where your weblayer appears:

  • Show on: Choose which pages display your weblayer — all pages, specific URLs, or pattern matching. Use Add exception to exclude pages where a weblayer would disrupt the experience, like checkout or login.
  • Show on pages with variables: Show different weblayers based on page-level data, such as product category or user behavior tracked through page variables.
  • Target devices: Choose desktop, mobile, or both.
Weblayer Settings tab showing the Display settings section with Show on set to "Any page", a Show on pages with variables option with an Add rule link, and Target devices set to "Any device (desktop and mobile)".

Display control

Display control determines how often users see your weblayer:

  • Always show: Best for critical announcements that need maximum visibility.
  • Once only: Good for welcome messages or one-time offers.
  • Once per visit: Works well for session-based promotions without overwhelming return visitors.
  • Until interaction: Keeps the message visible until the customer engages.

Expiration control

Set when your weblayer stops displaying:

  • After conversion: Hides the weblayer once the customer completes your goal.
  • After specific date/time: ets a hard end date for time-sensitive campaigns.
  • After time period: Creates urgency with a countdown-based expiration.
  • After interaction: Removes the weblayer once the customer clicks or engages.

Conversion goal

Select the event that counts as a conversion — a purchase event for sales campaigns, a custom event like a newsletter signup, or an engagement metric for awareness.

Weblayer Settings tab showing Display control set to "Always show", Expiration control set to "After conversion", and Conversion goal options with Purchase event selected.

Differences from standalone weblayer campaigns

Weblayers in scenarios behave differently from standalone campaigns in a few important ways.

FeatureIn scenariosIn campaigns
CreationScenario editorWeblayers tab
PersonalizationAvailable with consentAvailable with consent
A/B testingUse A/B test node insteadBuilt-in
EvaluationNot available (use custom dashboards)Built-in
Expiration controlAvailableAvailable
VisibilityLinked to the scenario onlyListed in Weblayers tab
Stop/startControlled through the scenarioCan pause individually

Known limitations and workarounds

  • No individual weblayer control: You start or stop the entire scenario, not individual weblayer nodes.
  • No built-in A/B testing: Add an A/B test node to your scenario and connect different weblayer nodes to each branch, then set your percentage split. This lets you test different messages, designs, or targeting strategies within the same workflow.
Scenario canvas showing a Weblayer node labeled "Countdown Box" connected to an A/B test node split into Variant A (33%), Variant B (33%), and Control Group (34%).
  • No Evaluate tab: Set up a custom dashboard to track performance.
  • Limited visibility: Weblayers created in a scenario are only accessible through that scenario.

Evaluate performance

Weblayers in scenarios don't have a built-in Evaluate tab. Use a custom dashboard to track performance instead.

How tracking works

The platform tracks 2 separate events when a weblayer runs in a scenario.

When a customer reaches the weblayer node in a scenario, the system tracks a campaign event with action = serve. This confirms the customer passed all scenario conditions and reached the node — it doesn't mean the weblayer was displayed.

The weblayer is displayed only when the customer also meets the weblayer's own entry criteria (consent, filters, display rules). When that happens, the platform tracks a separate banner event with action = show.

This distinction matters when analyzing performance. A high serve count with a low show count means customers are reaching the node but being filtered out by the weblayer's entry criteria.

Set up the dashboard

To track performance, create a custom dashboard report using the campaign_id from your weblayer. Include metrics like impressions, clicks, and conversions relevant to

Campaign event attributes

The campaign event generated by a weblayer node includes the following attributes. Use action_type = banner to filter campaign events for weblayer nodes specifically.

AttributeExample valueDescription
statusserveCustomer reached the weblayer node.
action_typebannerChannel type for weblayer nodes.
action_id2Sequential node ID within the scenario.
action_nameBlank templateWeblayer template name.
campaign_id69bd0f58e368Scenario campaign ID.
campaign_name202603_target_medium_contentScenario name.
campaign_triggernowTrigger type.

© Bloomreach, Inc. All rights reserved.