Personalizations
Personalizations allow you to make real-time visual changes on your website or application based on specified targeting conditions. It takes a piece of your site, like the promotions on the homepag...
Covered in the Academy. Lesson 6.2 of Intempt Academy covers experiences part 2: personalization step by step.
A Personalization answers "who has this yet?" rather than "does this work?" -- you choose who sees which version instead of splitting traffic to measure a winner.
It is authored in the visual editor and applies to your website. The same thing applied through an SDK -- so it reaches a backend, a mobile app or a native screen -- is a feature flag: identical targeting and identical selection, plus a key your own code asks for by name. See the four experience types.
Personalizations allow you to make real-time visual changes on your website or application based on specified targeting conditions. It takes a piece of your site, like the promotions on the homepage, and swaps that content out for different behaviorally targeted audiences. You can create a new personalization for each site section where you want to deliver targeted experiences.
Use cases
-
Homepage customization. Change the content of the homepage or landing pages based on the user’s past interactions, demographics, or session behavior
-
Geo-targeted offers. Offer personalized offers based on the user’s geo location
-
Personalized navigation. Adjust the navigation menu to highlight categories or pages the user has shown interest in, making it easier for them to find their preferred sections
-
Dynamic testimonials. Showcase relevant case studies or testimonials that resonate with the user’s industry or use case to demonstrate value and build trust.
-
Behavior-based CTAs for ICPs. Adjust CTA buttons or messages on the website and in-app based on the user’s lifecycle stage, encouraging them to take the next step in their journey, whether it's upgrading or utilizing a new feature.
Where to start
Web personalization
Mobile personalizations
Personalization analytics
Rollout and the off value apply here too
These are not flag-only, even though the feature flag guide is where they are explained in full.
Rollout. A personalization reaches the share of its audience you set. Widening it reaches people already evaluated, and closing it to 0% stops serving them — a personalization re-derives on every call rather than holding a pin, which is what makes the change take effect immediately.
The off value. When a personalization is paused or stopped it drops out of the evaluation response entirely, so server-channel callers receive nothing and cannot tell "the product turned this off" from "the service did not answer". The off value is what they receive instead. Set it on the setup tab.
Experiments differ on the first point and only the first. A running experiment keeps each participant's assignment until it ends, because re-bucketing mid-flight destroys the reading the experiment exists to produce.
Personalizations your code applies
Ask Intempt what to show through the REST API, then apply it in your own code. This is the path a backend, a mobile app or a native screen uses.
Measuring Personalization Impact
Read the Result tab on a personalization to see exposure, compare variants against Control, and decide whether a variant is ready to ship.