Words in bold indicate that there is an additional definition elsewhere in this glossary.
Account nodes ACL
Enables a user to read and/or write customer and event data on a specific node.
A property that is predefined in Contacthub, which represents the profile of a customer.
The circumstances or setting in which an event occurs. For example, a transaction event type can have an e-commerce or a retail context.
A view of the customer data, made up of both Base and Extended properties, as well as Events.
The place where customer-specific data and events are entered.
Data related to customer behavior, for example, making a purchase. An event is associated with the date on which it took place and a particular customer. Events are organized according to their type and may have specific properties. All event types are predefined in Contacthub.
All the metadata that is defined by the company using Contacthub, to extend the base metadata that is already available.
A customer identifier defined by an external system.
External ID policy
A check carried out by Contacthub to avoid customers being created with the same External ID. The default option is for the External ID to be unique on each node. The policy can also be set for the External ID to be unique in the entire workspace, or for no check to be carried out.
A place where customer data can be saved without defining a formal structure.
The unique identifier of an object or resource.
The market in which the company using Contacthub operates, for example, fashion, supermarket chains, travel and similar. The KPIs that are provided are linked to the defined industry.
One or more Base or Extended properties that can be used to determine whether two Customers, who are present in different nodes, are the same customer.
The behavior that is applied to an individual Property when two Customers are aggregated together. Behaviors are predefined in Contacthub and are associated with the type of field, for example, object, string, numeric and similar.
The hierarchical organization of the data nodes in the system. For example, a nodal hierarchy reflecting to the organizational structure of the company using Contacthub, such as the company, groups, brands and so on. The hierarchy determines how customers are aggregated.
A view of the data related to a specific customer, which is made up of Base and Extended properties.
The metadata that makes up the Customer profile. Metadata can be simple, for example, name, date of birth and so on, or complex, such as a list, work history and similar.
A method of accessing the data stored in Contacthub, for example, an API, a plug-in and similar.
An information flow that is provided by a data source. In the context of Contacthub, an information flow may be customer and/or events related.
A group of customers who are selected from the database by applying a series of rules. For example, every men from Milan, or all of the women in Rome who are over 25 years of age.
A temporary identifier that allows currently unassigned events to later be associated with a customer who, for example, may not be present within Contacthub at the moment.
The data required to configure a source. The configuration data is predefined for each provider.
Authorizes an application to carry out operations on data stored in Contacthub.
Source Token Nodes ACL
Defines the read and/or write access permissions for a specific source.
A keyword or term associated with a customer. Tags enable customer data to be classified and searched using keywords.
An automatic procedure that runs automatically when a certain event takes place.
The authorized staff of an organization, that operate Contacthub and are assigned a user profile.
The set of rules that are used to define an aggregated view of a customer. An aggregated view applies to data related to the same customer, at a defined level. For example, data related to two brands, which belong to the same category (such as shoes) and the same company, or company division.
Workspace (organization, company, consumer base)
The configuration and organization of customer data that is needed to read, write and assimilate the data.
Previous page: [previous_page] | Next page: [next_page]