People Based Destination Debugging
People-Based Destinations (PBD)
Supported partners:
Description description
How PBD Works
People-Based Destinations rely on:
- Declared ID
- Hashed Email
- Offline ID sync
- Correct Profile Merge Rule
If hashed emails are not synced correctly, segment populations will not activate as expected.
Declared ID documentation:
https://experienceleague.adobe.com/docs/audience-manager/user-guide/features/declared-ids.html
Resolution resolution
Common Failure Points
-
Offline ID Sync Issues
- Incorrect integration code
- Improper hashing (must be SHA256, lowercase, trimmed)
- Formatting errors
-
Profile Merge Rule Misconfiguration
-
Depending on use case, the merge rule must align with:
-
Authenticated user strategy
-
Cross-device requirements
-
Profile Merge Rule documentation:Â https://experienceleague.adobe.com/docs/audience-manager/user-guide/features/profile-merge-rules/merge-rules-overview.html
-
Partner Prerequisites
-
Each partner requires:
- Business Manager access
- Account linking
- Pre-approved audience sharing permissions
Ensure all onboarding steps are completed before expecting delivery.