My scenario is :- I have a person account(Member) stored in data extension with ContactId as the Subscriber key. I have another data extension(Product Interest DE) that stores the products that every contact is interested in(One member can have multiple product interest). Currently, for this data extension, I have set the Subscriber key as ContactId and ContactId as the Contact Key.
I am facing two problems when I use this data extension in journey with decision split:-
Contacts that have multiple records in the Product Interest DE do not follow the appropriate path in the decision split. The moment the system find a contact with multiple records, it pushes that contact in the remainder path of the decision split.
Suppose there are 10 records with 9 unique contactIds in the data extension. Journey entry source only considers 9 contacts instead of 10 records.
Workaround:- I raised a case with Salesforce and they replied I should use a unique identifier as the ContactId or filter the data extension such that there are only unique contacts. Hence, in the Product Interest DE, I have created Id(Primary key of the DE) as the Subscriber Key and again "Id" as the Contact Key.
Question:- Is the above workaround correct? will this affect the tracking data for the subscribers.