Overview
Discover compatible apps, load a segment catalog directly from the selected app, render parameters, preview matches, and freeze the final recipients.
Prerequisites
- At least one installed app declares audience-provider capability
- Direct controller access permitted
Permissions required
Steps (6)
-
1
Choose an audience source
EngagementHub asks the platform for installed apps that declare audience-provider capability. Select PeopleGraph, ProspectLayer, AccessGuard, HomeBridge, or another compatible app.
Tips
Validation
Success criteria
- The list comes from platform app capability declarations, not a hard-coded provider list.
-
2
Load provider segments
EngagementHub calls the selected app controller for its segment catalog. PeopleGraph may return tags; ProspectLayer may return lists; AccessGuard and HomeBridge may return dynamic definitions.
Tips
Validation
Success criteria
-
3
Render required parameters
Select a segment. EngagementHub requests its description/schema and renders required fields such as project_id, role_id, reservation status, tag ID, or list ID.
Tips
Validation
- Required values and lookup sources are displayed before preview is allowed.
Success criteria
-
4
Preview the audience
Send the selected segment code and parameters directly to the provider preview controller. Show total matches, channel-ready counts, excluded counts, and a limited sample where permitted.
Tips
Validation
Success criteria
-
5
Create the snapshot
At launch, request a provider-owned frozen snapshot and store the provider app, segment code, parameters, snapshot ID, count, creation time, and integrity metadata.
Tips
- Do not copy a mutable provider tag as the campaign truth; retain the returned snapshot reference.
Validation
Success criteria
-
6
Use and audit the snapshot
Attach the snapshot to the campaign or publication. Delivery and reporting use the same snapshot reference, while dispatch-time consent and contact validity remain the responsibility of identity and messaging apps.
Tips
Validation
Success criteria
- The campaign can prove exactly which provider snapshot was selected and when.
About this guide
EngagementHub gives organizations one governed backend for news, announcements, events, promotions, and coordinated campaigns. A shared content engine keeps titles, summaries, bodies, media, categories, tags, calls to action, related records, placements, visibility, and publication status consistent across every content type.
Teams can plan campaigns around a business objective, connect news, announcements, events, promotions, and communication instructions, then move content through draft, review, approval, scheduling, publication, expiry, and archive states. Events support registration, capacity, waitlists, approvals, reminders, check-in, attendance, feedback, and follow-up. Promotions support eligibility, claims, redemption, limits, terms, and automatic expiry.
Audience targeting uses the platform pattern already shared by PeopleGraph and ProspectLayer. EngagementHub discovers installed apps that declare audience-provider capability, requests each app’s segment catalog, collects any required segment parameters, previews the match, and asks the selected source app to create a frozen snapshot. AccessGuard can expose account segments, HomeBridge can expose parameterized property audiences, PeopleGraph can expose tags, and ProspectLayer can expose lists. EngagementHub never needs direct knowledge of another app’s database.
ProjectBoard supplies project truth, FileVault supplies secure files, HomeBridge exposes the customer experience, AccessGuard handles identity and in-app notification records, EmailHub sends email, and PulseGate sends SMS, WhatsApp, and voice. EngagementHub owns the content, campaign plan, audience reference, schedule, publication lifecycle, and performance record.