Spain omnichannel POC · selected environment: local
Business requirements mapped to IDHub capabilities
Each requirement below links to live evidence from the selected IDHub realm. Status is not inferred from repository sample files.
—source profiles in IDHub
—unified accounts
—multi-source examples loaded
—resolved relationships loaded
OM1 No evidence in this environment Bring every source feed into IDHub
BayTouch and Club Bayer data is available through one identity platform without replacing the source systems.
IDHub capabilityGENERIC profile providers + event receiver + provider cache
View evidence OM2 No evidence in this environment Recognize the same person across systems
A pharmacist appearing in contacts, engagements and trainings becomes one customer account.
IDHub capabilityField-equality matching + AccountMatchID + account mixer
View evidence Keep people, pharmacies and employees distinct
Different entity types never merge accidentally even when identifiers look similar.
IDHub capabilityPopulation-specific match fields and account mappings
View evidence OM4 Partially demonstrated Connect a pharmacist to their pharmacy
Applications can follow a stable IDHub account reference from a person to the related pharmacy.
IDHub capabilityextra.relationships[] + SIA account ID enrichment
View evidence OM5 No evidence in this environment Preserve source traceability
Integration and support teams can see which source records contributed to an account.
IDHub capabilityAccount providerdata and raw cached profiles
View evidence OM6 Awaiting business decision Respect communication consent
Marketing and commercial audiences include only people with the required legal basis.
IDHub capabilityData-processing purposes + putConsent + consent tags
View evidence OM7 Partially demonstrated Build journey audiences from IDHub data
Klaviyo can combine consent, role, territory, Methal, sell-in and Club Bayer membership.
IDHub capabilityAccount tags + person fields + SIA-denormalized organization attributes
View evidence Send stable customer identities downstream
Klaviyo receives the IDHub account ID and updated audience properties when customer data changes.
IDHub capabilityIDH.EXT events + Klaviyo integration SIA
View evidence Give integration teams a repeatable API contract
Teams can ingest data and consume unified accounts using documented realm-scoped APIs.
IDHub capabilityEvent receiver + Profile API GraphQL + Core API resources
View evidence