Platform App Registry — Integration

Overview

Use platform app capability declarations to discover installed audience providers and connected business apps without introducing a separate audience broker.

Capabilities

• List installed apps that declare audience-provider capability

• Resolve app identity, workspace installation, controller contract, scopes, and launch metadata

• Keep provider discovery centralized while segment catalog and snapshot calls remain direct

• Validate that a selected provider is installed, enabled, licensed, and allowed in the workspace

• Discover compatible ProjectBoard, FileVault, HomeBridge, AccessGuard, EmailHub, and PulseGate installations

1. 1

   Step 1

   In Platform Control, ensure EngagementHub is installed in the target workspace.

   Back to top
2. 2

   Step 2

   Register EngagementHub capabilities for content publishing, campaign management, feed serving, event registration, promotion claims, and audience consumption.

   Back to top
3. 3

   Step 3

   For PeopleGraph, ProspectLayer, AccessGuard, HomeBridge, and future source apps, declare the common audience-provider capability and controller metadata.

   Back to top
4. 4

   Step 4

   Grant EngagementHub permission to request the installed-app capability list for its own workspace.

   Back to top
5. 5

   Step 5

   Verify the returned list includes only installed and enabled audience-capable apps.

   Back to top
6. 6

   Step 6

   Select one provider and confirm EngagementHub can call its segment catalog controller directly.

   Back to top

Limitations

• The platform registry discovers providers but does not query provider business tables or create audience snapshots.

• An installed app that does not declare the common capability will not appear as an audience source.

• Provider controller requests still require app-to-app authentication, workspace matching, and route allowlisting.

FAQs

Pricing