Overview
Publish authorized content into canonical placements and track per-viewer feed interactions.
Problem
Customer-facing applications need a consistent capability for current engagement content while EngagementHub remains the publishing authority.
Solution
EngagementHub exposes placement and feed operations backed by publication state, placement definitions, visibility, audience rules and feed indexing.
How it works
A customer-facing app requests a placement feed using trusted workspace and viewer context. EngagementHub returns eligible published items and can record interactions such as views, reads, dismissals or acknowledgements.
Who is this for
Expected outcomes
- Canonical placement vocabulary across applications
- Publication and visibility rules stay centralized
- Per-viewer feed state supports interaction-aware experiences
Key metrics
Returned feed items backed by active placement state
0 %
100 %
Feed interactions linked to feed item and viewer context
0 %
100 %
Placement items linked to published content
0 %
100 %
Gallery
Security impact
- Placement definitions, feed index, content references and viewer interaction state · PII: Viewer identifiers can be stored for feed read and interaction state
Compliance
- Workspace-scoped application permissions and trusted execution context
- Operation/resource authorization for application calls
- Auditable workflow, queue, event or interaction records for this use case