Anonymous visitor web personalization
This guide describes the anonymous visitor web personalization use case pattern, which uses Adobe Journey Optimizer (AJO), Adobe Real-Time Customer Data Platform (RT-CDP), and Adobe Experience Platform (AEP) to deliver personalized web content to anonymous (unidentified) visitors based on in-session behavioral signals. It is designed for solution architects, marketing technologists, and implementation engineers who need to understand what this pattern does, the business objectives it supports, the tactical use cases it enables, and the Adobe applications involved.
The pattern operates with limited data – only what can be observed in the current session and any anonymous edge profile accumulated from prior visits with the same device or cookie. This makes it suitable for top-of-funnel personalization where the visitor has no account or has not authenticated.
Use case pattern
The following describes the core pattern and execution plan for this use case.
Anonymous Visitor Web Personalization
Deliver personalized content based on in-session behavioral signals for unidentified visitors via AJO web channel.
Execution plan: Web Surface Configuration > Behavioral Rule Evaluation > Content Delivery > Impression Tracking > Reporting
Use case overview
Anonymous Visitor Web Personalization addresses the business need to deliver relevant, personalized content to website visitors who have not yet been identified – they have not logged in, have no known identity, and cannot be resolved to a unified customer profile. Despite this limitation, meaningful personalization is achievable using in-session behavioral signals: pages viewed, time on site, scroll depth, referral source, geographic location, device type, and UTM campaign parameters.
This pattern uses AJO’s web channel surfaces and code-based experiences to modify page content in real time. Edge segmentation is the primary evaluation method since decisions must be made with sub-second latency as the visitor navigates the site. The Web SDK collects behavioral signals and sends them to the AEP Edge Network, where edge-evaluated audience rules determine which content variant to deliver.
Unlike known-visitor web/app personalization, which leverages the full unified profile and segment membership, this pattern is constrained to data observable in the current session and any anonymous edge profile associated with the visitor’s ECID (Experience Cloud ID). This distinction is critical for implementation planning: the behavioral signals available for personalization are limited to what the Web SDK captures and what persists in the edge profile store across sessions via the cookie-based ECID.
Key business objectives
The following business objectives are supported by this use case pattern.
Improve time on site, pages per session, and interaction with web content through relevant experiences tailored to anonymous visitor signals.
Deliver personalized customer experiences
Tailor content, offers, and messaging to individual preferences, behaviors, and lifecycle stage – even for visitors who have not yet identified themselves.
Improve the percentage of visitors and prospects who complete desired actions such as purchases, sign-ups, or form submissions by presenting the most relevant content based on behavioral context.
Example tactical use cases
The following examples illustrate specific scenarios where this pattern can be applied.
- Landing page headline A/B test based on referral source – Test different headlines for visitors arriving from Google, social media, or direct traffic to optimize engagement by acquisition channel
- Category affinity recommendations based on browse behavior – Display product or content recommendations based on pages viewed in the current session to increase discovery and conversion
- Exit-intent offer for visitors about to leave – Present a promotional offer or lead capture form when behavioral signals indicate the visitor is about to abandon the site
- Geo-targeted promotional banner – Show location-specific promotions, store locator content, or regional offers based on the visitor’s geographic location
- Device-specific content layout optimization – Adapt content layout, image sizes, and CTA placement based on whether the visitor is on desktop, tablet, or mobile
- New vs. returning visitor welcome messaging – Differentiate the experience for first-time visitors versus returning anonymous visitors using ECID persistence across sessions
- Content recommendations based on viewed pages in current session – Dynamically surface related articles, products, or resources based on the pages the visitor has already viewed
- Dynamic hero banner based on UTM campaign parameters – Personalize the hero banner to match the messaging or creative from the referring campaign
Key performance indicators
Use the following KPIs to measure the effectiveness of this use case pattern.
Applications
The following applications are used in this use case pattern.
- Adobe Journey Optimizer (AJO) – Web channel surface configuration, content authoring (web and code-based experiences), campaign execution, content experimentation (A/B testing), decisioning (dynamic content selection), and reporting
- Adobe Real-Time Customer Data Platform (RT-CDP) – Edge segmentation for real-time audience evaluation based on in-session behavioral signals; anonymous edge profile management
- Adobe Experience Platform (AEP) – Web SDK for behavioral signal collection, Edge Network for real-time data routing and personalization delivery, datastream configuration
Architecture
The following reference architecture illustrates how anonymous visitor signals are collected at the edge, evaluated against audience rules, and used to deliver personalized content.
Related documentation
The following Experience League resources provide additional detail on the capabilities used in this use case pattern.
Web channel and code-based experiences
Audiences and segmentation
Personalization and content
Content experimentation
Decision Management
Campaigns
Web SDK and data collection
Identity and profile
Data modeling
Reporting and analytics
Data governance and privacy
Guardrails