I wish to demonstrate the creation of the golden record and the merger of multiple inputs. This already happens with the demo loads:
- Rose Simpson has four interactions and creates one ROOT and four FACET records
- Ronald Scobee has a single contact load and so a single ROOT. He has extra FACET records representing EMAIL, PHONE and MOBILE.
Rose was unified because each record shared an email address. Ronald only ever had one record and so no unification was required.
I wish to demonstrate unification of multiple contacts using multiple keys. I will not use BADI and so will be restricted to EMAIL and PHONE as my key fields.
As far as I can tell unifying contacts who have no interaction will not display evidence of the unification in the web interface. I do not want my audience to have to view the DB tables. Therefore I must unify contacts who have interactions. Is this correct?
Interactions records carry email addresses but no phone numbers. Therefore if I want to unify across multiple fields I need to do a contact load. Is this correct?
The scenario that this leads us to is as follows.
- I run a contact load with two records for the same contact. They share a phone but have different emails. They will be unified based on phone.
- an interaction load with interactions for each of the contacts. These interactions will match the contacts on email. (They will not match each other)
- The two interactions will be linked through the shared contact and so have one golden record. The screens will show the interaction history (two interactions) for the single contact.
Please let me know if this sounds correct.
Cheers
Cliff