Overview
Show project updates, news, events, promotions, and announcements in one experience while preserving app ownership.
Problem
Customers should not experience the backend as disconnected apps or visit several separate feeds.
Solution
HomeBridge or the customer frontend composes ProjectBoard updates and EngagementHub content through stable feed contracts and current visibility rules.
How it works
EngagementHub returns active items for the requested placements and customer context. HomeBridge combines them with project updates, preserving source type, canonical link, media, CTA, priority, and timestamps for a consistent interface.
Who is this for
Customer Experience
Frontend Engineering
Product Operations
Expected outcomes
- One coherent customer experience
- Independent backend ownership
- Visibility enforced by authoritative apps
Key metrics
Customer feed sources combined
1 count
4 count
Feed API p95 latency
1800 milliseconds
500 milliseconds
Ineligible content exposures
5 count
0 count
Gallery
Downloads & templates
Security impact
- Feed request context, content summaries, project references, visibility decisions, placements, and interaction analytics · PII: Authenticated user identity or audience context used to filter content
Compliance
- No full audience member list in feed responses
- Per-request visibility enforcement
- Source app and content ID retained
Availability & next steps
Free
Growth
Business
Enterprise