The problem ODP solves
Section titled “The problem ODP solves”Your customers interact with your brand across many touchpoints — website visits, mobile app sessions, email clicks, purchases, support tickets, and in-store interactions. Each system captures a fragment of the customer’s journey, but no single system sees the complete picture.
Without unified data, personalization decisions are based on incomplete information. Your website does not know what emails the customer opened. Your email system does not know what pages they browsed. Your marketing team cannot target campaigns to customers who are about to churn because no system connects the signals.
Optimizely Data Platform (ODP) solves this by collecting behavioral data from all channels, unifying it into a single customer profile, and making those profiles available for segmentation, personalization, and experimentation across Optimizely One.
How ODP works
Section titled “How ODP works”Data collection
Section titled “Data collection”ODP collects events from every customer touchpoint:
| Source | What it captures | How it connects |
|---|---|---|
| Website | Page views, clicks, form submissions | JavaScript SDK or tag |
| Mobile app | Screen views, in-app actions | Mobile SDK (iOS/Android) |
| Opens, clicks, unsubscribes | ESP integration | |
| E-commerce | Purchases, cart actions, product views | Commerce integration |
| CRM | Support tickets, account changes | API integration |
| Point of sale | In-store purchases | Batch import or API |
| Custom sources | Any event your systems generate | Events API |
Identity resolution
Section titled “Identity resolution”The key challenge is recognizing that the same person interacted across channels. ODP resolves identities by linking identifiers:
- Anonymous visitor → Cookie ID from website
- Known visitor → Email from form submission
- Customer → Customer ID from purchase
When a visitor fills out a form on your website, ODP links their anonymous browsing history (cookie) to their email address. When they later make a purchase, their customer ID is linked too. All three identifiers now point to one unified profile.
Customer profiles
Section titled “Customer profiles”A unified profile contains:
- Identity — All linked identifiers (email, customer ID, device IDs)
- Attributes — Demographics, preferences, account details
- Event history — Every tracked interaction across all channels
- Computed metrics — Lifetime value, engagement score, recency/frequency
- Segment membership — Which audiences the customer belongs to
Real-time segments
Section titled “Real-time segments”Segments are audiences defined by rules applied to customer profiles. Unlike traditional batch-processed segments (updated nightly), ODP segments update in real time as events arrive.
Example segments:
| Segment | Rule | Use case |
|---|---|---|
| High-value customers | Lifetime revenue > $1,000 | VIP personalization |
| At-risk churn | No activity in 30 days AND was active | Re-engagement campaigns |
| Product researchers | Viewed 5+ product pages in 7 days, no purchase | Retargeting |
| New subscribers | Signed up in last 7 days | Onboarding nurture |
| Enterprise prospects | Company size > 500 AND visited pricing page | Sales hand-off |
Segments can combine behavioral rules (what they did), temporal rules (when they did it), and attribute rules (who they are).
ODP in Optimizely One
Section titled “ODP in Optimizely One”ODP is the data backbone that powers intelligent decisions across the platform:
| Integration | What it enables |
|---|---|
| CMS + ODP | Personalize CMS content based on customer lifetime data, not just session behavior |
| Experimentation + ODP | Target experiments to behavioral segments (high-value, at-risk, new) |
| Personalization + ODP | ODP segments sync to CMS visitor groups for content personalization |
| Analytics + ODP | Unified reporting across web, email, and commerce |
| Opal + ODP | AI agents access customer context for intelligent recommendations |
| Commerce + ODP | Product recommendations based on browsing and purchase history |
Key capabilities
Section titled “Key capabilities”Event tracking
Section titled “Event tracking”Track any customer action across any channel:
// Website eventzaius.event('pageview', { page_title: 'Pricing', url: '/pricing' });
// Custom eventzaius.event('demo_requested', { plan: 'enterprise', source: 'pricing_page' });
// Purchase eventzaius.event('purchase', { order_id: 'ORD-123', total: 299.99, products: [{ id: 'PROD-1', name: 'Annual Plan', price: 299.99 }]});Audience builder
Section titled “Audience builder”Build segments using a visual rule builder:
- Behavioral rules — “Viewed product page X in the last 7 days”
- Attribute rules — “Country is US AND plan is enterprise”
- Computed rules — “Lifetime value > $500”
- Temporal rules — “Last purchase was more than 30 days ago”
- Combined rules — AND/OR/NOT logic across all rule types
Data export and activation
Section titled “Data export and activation”ODP segments can be activated across channels:
- Optimizely products — CMS visitor groups, Experimentation audiences
- Advertising platforms — Google Ads, Facebook, LinkedIn (audience sync)
- Email platforms — Triggered campaigns based on segment entry/exit
- Webhooks — Real-time notifications when customers enter/exit segments
Privacy and consent
Section titled “Privacy and consent”ODP includes consent management:
- Consent tracking — Record and respect consent preferences per customer
- Data retention — Configurable retention periods
- Deletion requests — API for GDPR/CCPA right-to-deletion
- Anonymous mode — Collect behavioral data without PII until consent is given
When to use ODP
Section titled “When to use ODP”| Scenario | Without ODP | With ODP |
|---|---|---|
| Website personalization | Session-based rules only | Lifetime behavior + cross-channel data |
| Experiment targeting | Demographics, device type | Behavioral cohorts, purchase history |
| Email campaigns | Basic list segmentation | Real-time behavioral triggers |
| Churn prevention | Manual identification | Automated risk scoring |
| Customer understanding | Siloed per system | Unified 360° profile |
ODP is most valuable when you have multiple customer touchpoints and want your marketing, personalization, and experimentation decisions informed by the complete customer journey — not just the current session.
1. A visitor browses your website anonymously, then fills out a contact form with their email, and later makes a purchase using a customer ID. How does ODP connect these three interactions into one profile?
ODP's identity resolution links multiple identifiers (cookie ID, email, customer ID) as they are discovered, unifying all interactions into a single customer profile.
ODP's identity resolution links multiple identifiers (cookie ID, email, customer ID) as they are discovered, unifying all interactions into a single customer profile.
Review this topic →2. A marketing team wants to target a re-engagement campaign at customers who were active last month but have not visited in 30 days. Which ODP capability should they use?
Real-time segments can combine behavioral rules (was active) with temporal rules (no activity in 30 days) to automatically identify at-risk churn customers as events arrive.
Real-time segments can combine behavioral rules (was active) with temporal rules (no activity in 30 days) to automatically identify at-risk churn customers as events arrive.
Review this topic →3. An architect is designing a personalization strategy. The website currently personalizes based on session-level visitor group rules in CMS. The team wants to personalize based on a customer's lifetime purchase history across web and in-store channels. What should they add?
ODP collects data from all channels (web, mobile, in-store), builds unified customer profiles with lifetime data, and can sync segments to CMS visitor groups for content personalization.
ODP collects data from all channels (web, mobile, in-store), builds unified customer profiles with lifetime data, and can sync segments to CMS visitor groups for content personalization.
Review this topic →