This topic provides examples and considerations for common consolidation rules.

Full Name Consolidation Rules

When creating custom consolidation rules for Full Name, the values under related fields including First Name and Last Name may not be consistent with the Full Name value unless they are configured to have consolidation rules that ensure this consistency.

In the example below, the Full Name value is chosen from records with the most common non-null Primary: Country value:

To ensure that the First Name attribute value is the same as the Full Name attribute value, the consolidation rule for First Name is set to consider only records with the most common Primary: Country value and with the most common non-null Full Name value.

Selecting Values Based on Date

You can constrain golden record values based on the oldest, latest, or most common date value in a specified attribute using the Constraint condition.

In the example below, the schema has a custom attribute for create_date. The Company Name value is selected from records with the maximum (latest) create_date.

Note: See Requirements for Source Datasets for supported data formats.

Prioritizing Values from Dataset

You can choose to prioritize values from a specified source dataset. If there is a tie for the most common or longest value, the attribute from the prioritized dataset is chosen. Any datasets not specified in the rule are considered lowest priority.

In the example below, Postal Code is set to the longest value, prioritizing records from the source b2b_customers_le_sf_firmographic. Additionally, values from the source b2b_customers_le_phone_urlare excluded.

Consolidating Records Based on Matching or Non-Matching Values

The Value Comparison option allows you to consider only records in which selected attribute values match or do not match specific values or the values of other selected attributes.

Data Comparison Example

In this example, the user wants to ensure that the license number attribute list all license numbers that are not inactive for a golden record.

The License Number is set to its distinct values, excluding empty values, from records in which the License Status value is not inactive.

Attribute Value Comparison Example

In this example, the user wants to ensure that the license state corresponds with the state listed in in the primary address state.

The License State is set to the most common value, excluding empty values, from records with matching values for the License State and Primary: State attributes.