Abstract: Methods, systems, and devices are described that support extensible data mapping. A data mapping server may receive an indication of a source schema for a data source and may receive a user input indicating creation of a custom data object to handle the source schema. The server may create the custom data object based on the user input. The data mapping server may automatically map one or more data fields for a source data object (e.g., based on the source schema) to one or more custom data fields for the custom data object (e.g., based on a custom schema). The server may import a set of data records stored at the data source and may store the data records in a database system according to the custom schema based on the data mapping. The stored custom data objects may be used for segmentation, activation, analysis, or some combination thereof.

Abstract: Methods, systems, and computer program products for a customer relationship management (CRM) system are provided herein. Embodiments presented herein provide for exchange of data between disparate, distributed systems; subscribe to and/or publish customer data change event; creation of master records for consumers using static and streaming sources; providing data provenance, auditing capabilities, and queries across multiple tenants and third party systems. Embodiments provide a single view of a customer in a distributed system environment.

Abstract: Disclosed herein are method, system and device embodiments for setting up a graphical user interface (GUI) for a commerce architecture. An embodiment operates by providing a GUI that displays a first button for adding a first data source and a second button for adding a second data source, the second data source being related to the first data source, receiving a first response via the first button to add the first data source and a second response via the second button to add the second data source, providing a view of a first data schema and a second data schema, wherein the first data schema includes at least one object from the first or the second data source, and wherein the second data schema is a canonical data model, mapping the at least one object of the first data schema to at least one object of the second data schema, and providing a single entity view of the at least one object of the second data schema.

Abstract: Methods, systems, and computer program products for a customer relationship management (CRM) system are provided herein. Embodiments presented herein provide for exchange of data between disparate, distributed systems; subscribe to and/or publish customer data change event; creation of master records for consumers using static and streaming sources; providing data provenance, auditing capabilities, and queries across multiple tenants and third party systems. Embodiments provide a single view of a customer in a distributed system environment.

Abstract: Methods, systems, and computer program products for a customer relationship management (CRM) system are provided herein. Embodiments presented herein provide for exchange of data between disparate, distributed systems; subscribe to and/or publish customer data change event; creation of master records for consumers using static and streaming sources; providing data provenance, auditing capabilities, and queries across multiple tenants and third party systems. Embodiments provide a single view of a customer in a distributed system environment.

Abstract: Methods, systems, and devices are described that support extensible data mapping. A data mapping server may receive an indication of a source schema for a data source and may receive a user input indicating creation of a custom data object to handle the source schema. The server may create the custom data object based on the user input. The data mapping server may automatically map one or more data fields for a source data object (e.g., based on the source schema) to one or more custom data fields for the custom data object (e.g., based on a custom schema). The server may import a set of data records stored at the data source and may store the data records in a database system according to the custom schema based on the data mapping. The stored custom data objects may be used for segmentation, activation, analysis, or some combination thereof.

Abstract: Methods, systems, and computer program products for a customer relationship management (CRM) system are provided herein. Embodiments presented herein provide for exchange of data between disparate, distributed systems; subscribe to and/or publish customer data change event; creation of master records for consumers using static and streaming sources; providing data provenance, auditing capabilities, and queries across multiple tenants and third party systems. Embodiments provide a single view of a customer in a distributed system environment.

Abstract: Methods, systems, and computer program products for a customer relationship management (CRM) system are provided herein. Embodiments presented herein provide for exchange of data between disparate, distributed systems; subscribe to and/or publish customer data change event; creation of master records for consumers using static and streaming sources; providing data provenance, auditing capabilities, and queries across multiple tenants and third party systems. Embodiments provide a single view of a customer in a distributed system environment.

Abstract: Methods, systems, and computer program products for a customer relationship management (CRM) system are provided herein. Embodiments presented herein provide for exchange of data between disparate, distributed systems; subscribe to and/or publish customer data change event; creation of master records for consumers using static and streaming sources; providing data provenance, auditing capabilities, and queries across multiple tenants and third party systems. Embodiments provide a single view of a customer in a distributed system environment.

Abstract: Methods, systems, and computer program products for a customer relationship management (CRM) system are provided herein. Embodiments presented herein provide for exchange of data between disparate, distributed systems; subscribe to and/or publish customer data change event; creation of master records for consumers using static and streaming sources; providing data provenance, auditing capabilities, and queries across multiple tenants and third party systems. Embodiments provide a single view of a customer in a distributed system environment.

Abstract: Methods, systems, and computer program products for a customer relationship management (CRM) system are provided herein. Embodiments presented herein provide for exchange of data between disparate, distributed systems; subscribe to and/or publish customer data change event; creation of master records for consumers using static and streaming sources; providing data provenance, auditing capabilities, and queries across multiple tenants and third party systems. Embodiments provide a single view of a customer in a distributed system environment.

Abstract: Methods, systems, and computer program products for a customer relationship management (CRM) system are provided herein. Embodiments presented herein provide for exchange of data between disparate, distributed systems; subscribe to and/or publish customer data change event; creation of master records for consumers using static and streaming sources; providing data provenance, auditing capabilities, and queries across multiple tenants and third party systems. Embodiments provide a single view of a customer in a distributed system environment.

Abstract: Disclosed herein are method, system and device embodiments for setting up a graphical user interface (GUI) for a commerce architecture. An embodiment operates by providing a GUI that displays a first button for adding a first data source and a second button for adding a second data source, the second data source being related to the first data source, receiving a first response via the first button to add the first data source and a second response via the second button to add the second data source, providing a view of a first data schema and a second data schema, wherein the first data schema includes at least one object from the first or the second data source, and wherein the second data schema is a canonical data model, mapping the at least one object of the first data schema to at least one object of the second data schema, and providing a single entity view of the at least one object of the second data schema.