Personalization, Components, and Experience Fragments
What to know
Personalization targets content to audiences. Candidates must know context hub, segments (rules based on traits), and activities in Adobe Target or AEM's built-in targeting. Understand teasers and targeted components that swap content per segment.
Experience Fragments (XFs) are reusable, channel-agnostic content composed of components, with variations for different contexts. Know that XFs can be exported to Adobe Target and used across channels, and that Content Fragments (CFs) are structured, schema-driven content (models) distinct from XFs.
Component knowledge: proxy components, core components, HTL/Sightly, and the cq:responsive grid. Know that components are defined by dialogs and sling:resourceType.
Traps
- XFs are layout/presentation-oriented; CFs are structured data-oriented. Don't swap them.
- Personalization requires a segment; without a matching segment, default content shows.
- XF variations are not the same as language copies.
- Target integration requires configuration; not all XFs automatically sync.
- Core components differ from foundation components; questions may ask which is recommended.
Rule of thumb
If content must be reused across web, email, and ads with a consistent look, choose an Experience Fragment; if content is structured data for headless delivery, choose a Content Fragment.
Worked example: A homepage hero should differ for returning customers. Create a segment for returning visitors, add a targeted component with two experiences (default and segment-specific), and map each to the appropriate XF variation.