Weblayers in scenarios

Weblayers are website banners that display on your site based on customer behavior, profile data, or campaign logic. They let you show targeted messages—promotions, surveys, sign-up forms, or time-sensitive offers—without interrupting the rest of the page experience.

Adding weblayers to scenarios takes this further by connecting 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 might 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

Adding weblayers to your scenarios offers 3 key advantages.

Improve customer engagement

• Show targeted messages at key points in the customer journey.
• Create compelling calls-to-action that influence customer behavior.
• Promote time-sensitive offers and collect survey data.

Create seamless cross-channel marketing

• Keep your messaging consistent across email, mobile, and web.
• Make sure customers see related content on any channel they use.
• Build a cohesive experience throughout the customer journey.

Run more effective campaigns

• See how customers move between different marketing channels.
• Create coordinated promotions for events like Black Friday.
• Reach customers who missed your emails when they visit your site.

How to 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.

4. Double-click the weblayer node to edit it.
5. 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.

6. 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
7. Go to the Design tab to build your content.
8. Click Save.

Configure your weblayer

In the Settings tab, define your weblayer's audience, display rules, and performance settings. Unlike weblayers in campaigns, these only target users who reach this scenario node and can't expand beyond your scenario's original audience:

Entry criteria

Define who can see your weblayer using 2 filtering options:

• Consent category: Show weblayers 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 further by adding conditions based on customer behavior, profile information, or funnel progress. For example, target 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.

Display settings

Configure when and where your weblayer displays across your website:

• Show on: Choose which pages display your weblayer. Select from options like 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. Use desktop-only for detailed forms, mobile-only for app downloads, or both for universal messages.

Display control

Control how often users see your weblayer to balance visibility with user experience:

• 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 to keep content relevant:

• After conversion: Hides the weblayer once the customer completes your goal.
• After specific date/time: Sets 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. This is what you'll use to measure impact..

Differences from standalone weblayer campaigns

Weblayers in scenarios work differently from standalone campaigns. Here are the key differences and how to work with the limitations:

Work around known limitations

• Can't control individual weblayers: You must start or stop the entire scenario.

• 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 approach lets you test different messages, designs, or targeting strategies within your scenario workflow.

  

• No Evaluate tab: Set up a custom dashboard to track performance.

• Manual enablement required: Ask your CSM to enable weblayers for your project.

• Limited visibility: Only accessible through the scenario where created.

Evaluate performance

Since weblayers in scenarios don't have a built-in Evaluate tab, you'll need to create a custom dashboard to track performance.

Serve and show

When a customer reaches the weblayer node in a scenario, the system tracks a campaign event with action = serve. This means the customer passed all the conditions in the scenario and reached the weblayer node—not that the weblayer was actually displayed.

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

• campaign event, action = serve: Customer reached the weblayer node in the scenario.
• banner event, action = show: Weblayer was actually shown to the customer.

This distinction matters when analyzing performance: a high serve count with a low show count usually means customers are reaching the node but being filtered out by the weblayer's own 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 your goal.

Use cases

Here are popular ways to use weblayers in scenarios:

Follow up on missed emails

• Show website offers to customers who didn't open your email.
• Give your promotions another chance to be seen.

Recover abandoned carts

• Display reminders when customers with items in cart return to your site.
• Highlight products they left behind.

Grow your audience and data

• Collect customer data by offering incentives through weblayers.
• Encourage newsletter sign-ups through special offers.

Create urgency

• Use countdown timers for sales and limited-time offers.
• Drive faster action by creating a sense of urgency.