Nodes enable you to add, divide and store data in different containers. This is particularly useful when you want to separate data that is related to, for example, different countries, individual brands, or sales channels and similar, but still access all the relevant information in the same workspace.
There are three types of node:
- Entry nodes.
Separate nodes where customer and event data is written to individual customer profiles. For example, you could have one entry node for online purchases and another for in-store activity. See Managing entry nodes for more details.
At least one entry node is needed for Contacthub to work.
- View nodes.
Containers that you cannot write to directly. Instead, view nodes are populated with demographic information from entry nodes, according to the Tree hierarchy configuration. No event data is stored in view nodes, and they cannot be used as a source for marketing activities, or synchronized with Plan, Flow, Send or other environments. See Managing view nodes and Configuring trees for more details.
View nodes are now deprecated. As a result, existing ones can still be seen and used, but new view nodes cannot be created.
- Aggregate nodes.
Nodes that create aggregated yet still individual customer profiles, from the demographic and events data in the entry nodes they relate to. They enable you, for example, to combine the data from two or more entry nodes, such as separate online and in-store purchases ones, to create a comprehensive customer purchases profile. The resulting profiles can readily be used for marketing activities and be synchronized with Plan, Flow, Send and other environments. See Managing aggregate nodes for more details.
Contacthub enables you to view all node types and create or edit Entry nodes. Aggregate nodes can only be created or edited by Contactlab staff. Neither entry or aggregate nodes can be deleted. See Managing entry nodes, Managing view nodes and Managing aggregate nodes for more details.
Unique customer policies and matching properties
Unique customer policies are defined on entry node pages. They enable you to select the property fields that should be used to determine whether data apparently belonging to two customers, actually relates to same one. See Managing entry nodes for more details.
The defined policy is applied in combination with the Customer uniqueness setting for the relevant workspace. See Configuring workspaces for more details.
Aggregate nodes include Matching properties, which are configured by Contactlab staff when a node is created or edited. They define the field/s that are used to determine whether profiles should be aggregated.
A Tree defines the data hierarchy and, as a result, the priorities that are applied when aggregating and merging data in view nodes. See Configuring trees for more details.