Personalization component source

Created on 21 May 2025, 18 days ago

Overview

Marketers want to create personalized experiences for their end users. They want to show the right content to the right person at the right time.

For achieving that, they need to be able to create personalization variations for each personalization segment.

Proposed resolution

We architected that a new component source will wrap the personalization variations.
Refine the implementation details still under discussion.
Provide that component source.

User interface changes

None.

📌 Task
Status

Active

Version

0.0

Component

Personalization

Created by

🇪🇸Spain penyaskito Seville 💃, Spain 🇪🇸, UTC+2 🇪🇺

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @penyaskito
  • 🇪🇸Spain penyaskito Seville 💃, Spain 🇪🇸, UTC+2 🇪🇺
  • 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺

    Bumping to because this is what will get us to 100% confidence in answering

    1. feature: ability to store variants of component trees for use cases like personalization (i.e. different component subtree for Belgians & Brits vs everyone else), responsive design (i.e. breakpoint-specific overrides), and arbitrary future use cases
Production build 0.71.5 2024