Golden Record Guide

Created by Dariusz Szczendzina, Modified on Tue, 28 May at 2:55 PM by Harry Drew

The 'Golden Record' refers to a concept within Master Data Management. It means 'a single version of the truth', or, perhaps more literally, one data point that captures all necessary information.

The Golden Record module (optional) will allow Users to 'flag' records as Golden when merging or linking them. This allows Users to specify whether they would like to: match non-golden records with non-golden records / match golden with non-golden records / match golden records with golden records.

This page will explain how to get the most out of this optional module.


Standard Linking of Parent/Child Records

When running a match session, after identifying duplicates you may want to link records as opposed to merging them. This will link the Master Record (Parent) with any duplicates (Children).

This can be performed when running a Standard session by selecting Link on the duplicate review screen.

After selecting Link, a dialog box will appear asking whether or not you will want to overwrite any existing parent values on any of the duplicates.

  • Overwrite Parent - If the Duplicate already has a parent link, it will overwrite the existing parent with the master record.
  • Do Not Overwrite Parent - If the Duplicate already has a parent link, it will not overwrite the existing parent with the master record.

NOTE: Linking records within a standard session will not flag the Master records as 'Golden'. This can only be done when selecting 'Match Non Golden Records' from the Session Type dropdown within Step 1 - Session Setup.


Creating a 'Golden Record' Session

To create a Golden Record session, head to Create Session on the home screen and name your session as normal. Then select Single Entity under Match Type.

Under Session Type, you will notice alongside Standard will be three other options. These session types are what utilise the Golden Record optional module. You will notice the application will auto-select Account as an entity type, as the golden record functionality is exclusively available within the Account entity.

When records are made 'The Master', they are flagged as the new 'Golden Record'. This therefore allows other records to be linked to this Golden Record. Therefore, to make our Golden Records, then we need to use this set of Golden Records to compare against new, incoming data which might need to be linked to the golden records.

An explanation of all three additional session types and when they should be used can be found below:

Match Non Golden Records

This session type allows you to match non-golden records to other non-golden records.

To utilise this optional module, you must start creating your golden records in your CRM database. This can only be done by linking/merging duplicates within this session type.

On the Group Review screen, you will notice the Create & Link button has appeared.

Selecting this option will create a new record in which to set as a master. This record will be created as a copy of the Master record and have the original master record linked to your new golden record as a child.

Match Golden with Non-Golden Records

This session type allows you to match records that have already been flagged as golden to non-golden records.

After running Match Non-Golden Sessions, this should be your next step. Matching your newly golden records to non-golden records allows you to perform a cross comparison to match records, allowing the necessary linking of legitimate duplicates that have been introduced into your CRM.

Match Golden Records

This session type allows you to match golden records to other golden records.

This option allows you to complete a match session to de-duplicate your golden records. This will prevent multiple duplicate golden records from co-existing.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article