Overview
Use a HomeBridge segment that requires a ProjectBoard project identity and returns a provider-owned customer snapshot.
Problem
EngagementHub does not know how interest, enquiry, reservation, assignment, or waitlist relationships are stored in HomeBridge.
Solution
HomeBridge describes a parameterized segment and performs its own query when EngagementHub supplies the selected project ID.
How it works
The campaign manager selects HomeBridge, chooses Customers interested in a project, selects Mandilas Tower through a ProjectBoard lookup, previews the matched customer count, and requests a frozen HomeBridge snapshot. EngagementHub stores the provider, segment, project parameter, snapshot ID, and count.
Who is this for
Expected outcomes
- No cross-app database coupling
- Reusable dynamic relationship segments
- Exact project parameter retained for audit
Key metrics
Custom audience SQL inside consumers
8 count
0 count
Audience creation time
45 minutes
5 minutes
Snapshot requests with complete parameters
0 %
100 %
Gallery
Downloads & templates
Security impact
- Provider segment metadata, project identity parameter, preview metrics, snapshot reference, and relationship-derived recipient identifiers · PII: Customer user IDs and permitted contact information supplied through HomeBridge’s approved enrichment path
Compliance
- HomeBridge owns relationship truth
- ProjectBoard owns project truth
- Only necessary recipient fields returned