Limitless 1:1 Personalization uses Optimizely Opal to create and update landing pages for each target account or audience segment. The solution addresses the mid-funnel (the consideration stage between awareness and purchase) content problem. The full-funnel strategy works at the top with brand campaigns and at the bottom with high-intent content. The middle breaks because content production cannot match the resolution that the funnel demands.
B2B personalization at scale is a volume problem. Every member of the B2B buying committee (the economic buyer, technical evaluator, business champion, and others) needs content that addresses their concerns. The content required to reach every member at every target account exceeds what any team can produce manually. B2C brands serving diverse segments, geographies, or product categories face the same challenge. Limitless 1:1 Personalization solves both.
Prerequisites
Limitless 1:1 Personalization requires the following Optimizely products.
- Opal – The AI agent layer that powers the workflow.
- Optimizely Content Management System (CMS) – A dedicated additional production instance of CMS is required to support the volume of pages this solution generates. This keeps the solution's content environment independent from your primary CMS instance.
- Optimizely Content Marketing Platform (CMP) – The content approval and governance layer. CMP supports human review before publishing pages.
- Optimizely Data Platform (ODP) – Powers event tracking and audience intelligence. Engagement signals from generated pages flow back through ODP to the Customer Relationship Management (CRM).
How it works
B2B account personalization
The agent pulls target accounts from a CRM system. It enriches each account with web research and ODP behavioral data. The agent then infers buying committee personas (representative profiles for each buying role). CMS publishes pages as content items on a customer subdomain. CMP approval modes handle governance. Sales Development Representatives (SDRs) receive persona-specific URLs.
B2C audience personalization
The same architecture generates segment-, persona-, or product-specific pages at any volume. Examples include loyalty members, traveler types, and product categories. Only the data source changes.
The agent pulls audience segments from a Customer Data Platform (CDP) or similar data source. It generates a page for each segment. CMS publishes pages as content items on a customer subdomain. CMP approval modes handle governance. Marketing teams receive segment-specific URLs to use in campaigns, emails, and paid media.
Opal agents
Limitless 1:1 Personalization uses a set of purpose-built Opal agents to power the workflow. These agents run inside Opal. Like all Opal agents, these agents support ongoing updates and refinements. Optimizely assigns a Field Delivery Engineer (FDE) to assist with configuration.
The agent researches a target account, writes personalized copy, and publishes a CMS page. The agent operates in two modes depending on whether a page already exists for the target account.
- Creating a new page – When no page exists, the agent checks CMS, researches the account, generates personalized copy, and publishes the page.
-
Updating an existing page – When a page already exists, the agent runs a lightweight check instead of repeating full research. It pulls recent CRM activity and scans for new signals from the last three months. If the change is material, the agent rewrites only the affected sections.
Signals trigger updates. These include a new C-suite hire, a merger or acquisition, a rebrand announcement, a competitor change in the technology stack, or a shift in the account's buying stage. If no material change is found, the agent confirms the existing page is current and takes no action.
Pages improve over time as accounts engage and signals accumulate. The agent that creates a page can refresh it months later when the account moves to active evaluation.
Regardless of mode, the agent applies the same guardrails for accuracy, brand compliance, and character limits.
Get started
Onboarding with Limitless 1:1 Personalization is a guided process. To get started, contact your Account Executive (AE) or Customer Success Manager (CSM).
After purchase, complete the following steps:
- Provisioning – Optimizely provisions a dedicated CMS instance, separate from your existing CMS environment.
- FDE scoping call – Your assigned FDE meets with your team to review your technology stack, data sources, and use case goals. Data sources may include CRM or CDP.
- Agent configuration – The FDE configures the Opal agents to pull from your data sources. The agents then connect to your CMS, CMP, and ODP instances.
- Subdomain configuration – Point a subdomain or subfolder to Optimizely. Generated pages live here alongside your existing site. No site rebuild is required.
- Go live – Pages begin generating. For B2B, SDRs receive persona-specific URLs. For B2C, segment pages are live and indexed.
Page characteristics
Generated pages are standard CMS content items, not microsites, overlays, or temporary experiences. Pages have the following characteristics:
- Crawlable and indexed by search engines.
- Shareable through direct URL.
- Attributable to audience or account data.
- Governed through CMP approval modes.
- Durable and persistent, not session-based.
- Updatable over time by the agent or manually.
What this is not
Limitless 1:1 Personalization is not the following:
- A chatbot – Creates landing pages, not conversational experiences.
- Real-time personalization – Sets pages per account or segment, not dynamically per visitor session.
- A digital asset management system or content hub – Generates pages and does not organize existing assets.
- A site rebuild – Runs on a subdomain or subfolder alongside the existing site. No migration is required.
- Ephemeral content – Produces durable, indexed, and crawlable pages, not temporary overlays.
If you use Opti ID, administrators can turn off generative AI in the Opti ID Admin Center. See Turn generative AI off across Optimizely applications.
Article is closed for comments.