Overview
The Contact Details enricher listens for system events related to these user actions in the storefront:
- a new user registers for the storefront and provides personal data
- a user signs in to a storefront using the created credentials
- a user enters the storefront
When the system sends these events, the Contact Details enricher adds a new subdocument to the user's profile document. It not only adds contact details to the customer profile document, but also connects these details with internal links, and associates the with a relevant session.
The Contact Details enricher reacts to the following events in the Context service:
- user-registered
- user-logged-in
- frontend-entered
Events
The following events in the Context service trigger the Contact Details enricher:
| Event | Triggered by Schema | Payload example |
|---|---|---|
| user-registered | context/commerce/UserRegistered | Example |
| user-logged-in | context/commerce/UserLoggedIn | Example |
| frontend-entered | context/commerce/FrontendEntered | Example |
| Attributes | Properties |
|---|---|
profiles/observations/web | |
profiles/contactDetails | |
profiles/addresses |
Metamodel
The following interactive graphic displays the schemas that invoke this enricher.
Glossary
| Term | Description |
|---|---|
| authorization | The process of determining whether a given microservice has permission to gain consent. |
| consent | Permission to access (read, write) specific profile data, for example, permission to read or write an age estimation or physical address. A consumer and a tenant can grant and revoke consent for subsets of their respective data. |
| consent class | A developer-defined string alias that references a set of profile data, or "schemas", for which to grant and revoke consent. |
| consent reference | A unique, randomized string that serves as a passcode to decrypt data associated with one or more schemas. |
| consumer | The end user whose actions yield profile data in the profile document. A profile describes a single consumer. |
| context | Data that affects the state of the profile document. You can collect this data from consumer-triggered events or from third-party sources such as weather stations. |
| context service | An internal microservice that manages the insertion of, and the retrieval of, context data in the Context Repository. |
| enricher | A microservice that retrieves data from the Context repository and the profile document, possibly alters or extends it, and then persists data in the profile document. An enricher can interpret data points, or sets of data points, to yield new data to persist. For example, an enricher can interpret purchasing data and contemporaneous weather station data to yield new data indicating that the consumer is a rainy-day shopper. |
| identity | One of many independent units of data used to identify a unique profile, such as an email address, browser type, or version. |
| profile | Technical definition: Data in the profile document that is interdependent and associated with a single consumer. Business definition: Data about a single consumer, collected and derived from events that the consumer triggers, or events that are logically associated with that consumer. |
| schema | A string representation of a path in the profile document, which represents an abstraction of a particular data structure, and used to define read and write permissions for SAP Hybris Profile microservices. |
| tenant | A tenant is a group of users on a project sharing common access, with specific privileges to a service. |
If you find any information that is unclear or incorrect, please let us know so that we can improve the Dev Portal content.
Use our private help channel. Receive updates over email and contact our specialists directly.
If you need more information about this topic, visit hybris Experts to post your own question and interact with our community and experts.