Concepts overview
Use this section to understand the core concepts behind Experiences and how the pieces fit together, so you can choose the right integration approach and configuration options.
If you're new to Experiences, start with Getting started for a product overview and end-to-end system flow.
Where to look in the docs
| If you need to… | Go to |
|---|---|
| Understand what Experiences can do and how the pieces fit | Concepts (this section) |
| Wire APIs, initialize the SDK, or set style properties in code | Platform SDK sections (iOS, Android, Web, React Native, Flutter) |
| Manage content, labels, schedules, widgets, or analytics in Experiences CMS | CMS |
| Check which software versions and components are supported | SDK component compatibility and versions |
| Choose and implement the viewer ID | Viewer ID (Requirements) |
| Implement privacy and tracking modes | Viewer privacy considerations and privacy compliance (Requirements) |
Concepts stay at the mental-model layer. They don't replace SDK property reference, CMS how-to steps, or Requirements policies.
Start by role
Use this as a suggested reading order for your job, not a go-live checklist. Pick the path that matches how you work with Experiences, then follow the links in order. Jump to another path when your responsibilities overlap.
- App owner: Content types → Content recommendations → Viewer ID and privacy → Analytics. Decide privacy, personalization policy, and what developers must implement.
- Developer: Player sources → Data sources → Viewer ID and privacy → your platform SDK getting-started page. Use Concepts for the model, then SDK pages for wire-up.
- Content manager: Content types → Labels → CMS overview → CMS-configured widgets when widgets are managed in CMS.
To see these concepts in a working implementation, use the sample apps. If you use AI tools, connect the Experiences MCP servers for access to docs and sample apps in your tool. See Experiences MCP servers.
What you'll learn in Concepts
- How content is modeled (Stories, Moments, Videos) and what metadata drives behavior
- How apps deliver content with player sources (widgets, entry points, and the Moments container)
- How data sources (labels, IDs, search, and recommendations) determine what the SDK loads
- How recommendations work: Trending (global), Personalization with explicit signals (like follows), and implicit For you (see Content recommendations).
- How the player UI behaves and what you can customize
- How localization and language fallback affect viewer experience
Updated 24 days ago