Personalization
Always-on personalization with Ours Privacy. Show targeted content to specific audience segments using the visitor data and audiences already in your CDP.
Personalization
Personalization is about delivering the right message to the right visitor — not testing to find out which message works better.
With personalization rules, you define which content a specific audience should see, and that content is shown to them every time. There's no traffic split, no statistical test, and no winner to declare. The rule runs until you stop it.
Personalization vs. A/B Testing
| A/B Test | Personalization | |
|---|---|---|
| Goal | Discover which variant converts better | Show targeted content to a known audience |
| Traffic | Split between variants | 100% of the matching audience sees the rule |
| End date | When a winner is declared | Runs indefinitely |
| Statistics | Bayesian probability to be best | None |
| Use case | "Which headline drives more sign-ups?" | "Show healthcare-specific messaging to healthcare visitors" |
Use A/B testing when you have a hypothesis and want data to decide. Use personalization when you've already decided — you just need to deliver it.
What Personalization Is Good For
Industry-specific messaging. Healthcare companies get a hero tailored to HIPAA and care networks. Enterprise visitors get an enterprise pricing pitch. Everyone else sees your default.
Returning visitor recognition. First-time visitors see your acquisition pitch. Visitors who've already explored your product see a message that reflects where they are in the journey.
Campaign landing pages. Visitors arriving from a specific ad campaign or UTM source see copy that matches the ad they clicked. Everyone else sees the default page.
Geographic or regional content. Show region-appropriate messaging, pricing context, or compliance language based on where the visitor is located.
Audience-driven content. Any audience you've built in the Audience Builder — based on page visit history, event history, behavioral patterns, or custom attributes — can be used as a personalization target.
How It Uses Your Existing CDP Data
Personalization is built into the CDP, so the data you're already collecting is already available as targeting criteria.
Audience segments you've built in the Audience Builder are directly available as targets. If you've defined a "Healthcare Provider" or "Enterprise Prospect" segment, you can use it in a personalization rule without any extra setup.
Visitor properties captured by the CDP — UTM parameters, geographic data, device type, referral source, visit count, custom attributes — can all be used to target personalization rules without a saved audience.
Events you're already tracking provide behavioral targeting. Show a message to visitors who have previously viewed your pricing page, completed an onboarding step, or triggered any other tracked event.
How to Set Up a Personalization Rule
Everything is configured in the Ours Privacy dashboard.
- Create a new experiment and select "Personalization" as the type
- Set the URL where the rule should apply
- Choose your audience — select an existing audience segment, or define targeting criteria directly (visitor properties, UTM source, geography, etc.)
- Define the content changes using the visual editor — the same point-and-click tool used for A/B tests
- Start the rule
Matching visitors see the personalized content immediately. Everyone else sees the original page.
Multiple Rules on the Same Page
You can run multiple personalization rules on the same page at the same time. When a visitor matches more than one rule, all matching rules are applied.
If two rules modify the same element, the last one in priority order wins. You can reorder rules in the dashboard to control priority.
Consent
Personalization rules respect the same consent settings as A/B tests. Visitors who have not consented to analytics do not see personalization rules. This is handled automatically by the platform — you don't need to add any consent checks to your rules.
Next Steps
- Content A/B Tests: Run a statistical experiment when you want data to make the decision
- Redirect Tests: Test two completely different pages against each other
- JavaScript SDK: Access personalization assignments from your own code
How is this guide?