Visitor Groups and Personalization

Every visitor to your site has a different context — their role, industry, location, device, purchase history, and intent all differ. Showing every visitor the same content means most visitors see content that is only partially relevant to them.

Personalization addresses this by tailoring content to visitor context. When done well, it increases engagement, reduces bounce rates, and improves conversion. When done poorly — or overly aggressively — it feels invasive and erodes trust.

Optimizely provides personalization at multiple levels across its platform. Understanding which approach fits your scenario is essential before you start building.

Optimizely offers three distinct personalization mechanisms. They can be used independently or combined.

Approach	Where it lives	Defined by	Complexity	Best for
Visitor groups (CMS)	CMS content delivery	Content authors and admins	Low	Content variations on CMS pages
ODP segments	Optimizely Data Platform	Data teams and marketers	Medium	Cross-channel audiences based on unified customer data
Web Experimentation personalization	Experimentation platform	Marketers and optimization teams	Medium-High	Client-side content changes with targeting rules

Visitor groups are the simplest personalization mechanism. They are defined in the CMS admin interface and used by content authors to show different content to different audiences.

A visitor group is a set of criteria that a visitor either matches or does not. When a visitor matches a group, they see content targeted at that group. When they do not match, they see the default content.

How visitor groups work:

1. An admin defines a visitor group with one or more criteria (e.g., “First-time visitors from the UK”)
2. A content author creates a content area on a page and adds personalized content for that visitor group
3. When a visitor loads the page, CMS evaluates the visitor against all active groups
4. The visitor sees the content targeted at their matching group, or the default if no groups match

Built-in criteria include:

Criteria type	Examples
Geographic	Country, region, city
Behavioral	Number of visits, time on site, pages visited
Technical	Browser, operating system, device type
Temporal	Day of week, time of day, date range
Referral	Search engine, campaign, referring URL
User profile	Logged-in status, role, custom properties

Developers can also create custom visitor group criteria to match against any data source — CRM records, purchase history, or external APIs.

Optimizely Data Platform (ODP) provides a deeper level of personalization based on unified customer profiles. Unlike visitor groups (which evaluate criteria in the moment), ODP builds persistent customer profiles from data collected across all channels — website, mobile app, email, and in-store.

When ODP segments add value over visitor groups:

• You need to target based on historical behavior (e.g., “customers who purchased in the last 30 days”)
• You want cross-channel consistency (same segment applies on web, email, and mobile)
• You need real-time audience computation based on streaming events
• You want to sync audiences with advertising platforms

Web Experimentation’s personalization feature delivers targeted experiences through client-side JavaScript. It operates independently of the CMS — changes are made in the Experimentation visual editor and deployed via a snippet on your site.

When to use Experimentation-based personalization:

• You want to personalize without CMS deployments
• You need to run A/B tests on personalized experiences
• Your personalization changes are visual (copy, images, layout) rather than structural
• You want marketers to manage personalization without developer involvement

Choose your approach based on your scenario:

Scenario	Recommended approach
Show different hero banners by country	Visitor groups — simple, built into CMS
Target users who abandoned cart last week	ODP segments — requires historical data
Test two different CTAs for returning users	Web Experimentation — combines personalization with measurement
Show VIP pricing to logged-in wholesale customers	Visitor groups with custom criteria — server-side, secure
Personalize email and website consistently	ODP segments — cross-channel by design
Quick copy changes without a CMS deploy	Web Experimentation — client-side, no deploy needed

In practice, many organizations use all three. Visitor groups handle content-level personalization inside CMS. ODP provides the audience intelligence. Experimentation measures what works.

Personalization and experimentation are complementary, not competing. Personalization decides who sees what. Experimentation measures whether it works.

A common workflow:

1. Hypothesize — “Returning visitors convert better when shown product recommendations”
2. Personalize — Create a visitor group for returning visitors, show them a recommendations block
3. Experiment — A/B test the personalized experience against the default
4. Measure — Use Experimentation analytics to determine if the hypothesis was correct
5. Scale — If the test wins, roll out the personalization permanently

This workflow is why Optimizely combines CMS, Experimentation, and ODP into a single platform — the data flows between products enable this loop.

Visitor group evaluation happens server-side during page rendering. Each request evaluates the visitor against all active groups on that page. Keep the number of concurrent visitor groups reasonable (under 20 per page) to avoid latency.

Personalized content complicates caching. A page with three visitor group variations is effectively three different pages from a cache perspective. Optimizely handles this through output cache variation, but architects should understand the trade-off between personalization granularity and cache efficiency.

Personalization relies on visitor data. Ensure your approach complies with privacy regulations (GDPR, CCPA). Visitor groups based on geographic or behavioral criteria may require consent. ODP segments based on identified customer data require clear consent management.