​Help to recover data loss caused by misconfiguration

[alessandroventuri]

Hello, I made a wrong selection in the Origins of Contact ID, SAP FORM.
I probably misunderstood the meaning of the check for "For identification"

What happens now is that every time a persons submits a form, a contact is NOT created.

A certain number of people have done so already, so I have lost them as contacts, that is, I am unable to create a target group made of their contact email.

Instead, a contact X now has attached some interactions made by another person.

Is there a way to access a log of the changes of the record X so that I can recover the data?

[alessandroventuri · Accepted solution]

Hi Saravanakumar, thanks for your reply.
In the screen attached ypu can see the contact.

The original contact is the green one. Then, the blue one filled the form. After that, the contact was updated mixing the two. As a result, the contact now has still the original ID (green email) but with the wrong name (the blue name).

contatct-inter.png

Now, if I understand your reply, I could use the Browse interaction app and delete the interaction, that is, the form submit, so that the contact gets again the correct data, that is, green email and green name.
But my bigger problem is to recover the blue email/name because he submitted important information that I don't want to lose. I need to extract its data and upload as a contact, possibly with the other data submitted via the form. Is there a way to obtain this?

[vervinckt_joyca · Accepted solution]

Hi Alessandro,

I fear it may not be possible to retreive this data.

If you marked the "SAP_FORM" origin as "for identification", then next to the blue data, there might have already been multiple other data that you don't even see anymore.

Because every time that an identical Origin + ID enters the mkt system, it will overwrite previous data on that same combination.

So you will probably have had:

Origin: SAP_FORM

ID: 42010xxxDB8

email: kxxx@company.de

but earlier there may have also been:

Origin: SAP_FORM

ID: 42010xxxDB8

email: oldersubmit@company.de

as the origin + id are identical, the email address would just get overwritten each time. And for the SAP_FORM origin, the ID is just the ID of the form, not a unique id per submit. While in other situations you usually have a different origin or a different id, with perhaps a match on the "email address" which will trigger the match&merge process and append that extra origin data to your existing contact instead of overwriting the existing origin data.

[alessandroventuri]

Hi vervinckt.joyca, thank you.

I see.

Would you mind explain in which possible scenario would be desirable this "for identification" setting? I mean, in my scenario I should have set it in the opposite way. But I wonder when this is the right choice then. When overwriting the previous data would be appropriate?

[vervinckt_joyca]

In any situation where the source assignes a unique identifier to the customer and uses that as an ID.

For example on a Hybris Commerce webshop, the origin is SAP_HYBRIS_CONSUMER and the ID is a unique id that the commerce webshop assignes to this user.

Within the "my profile" settings, the user can always change his personal data. And this update of data would then be interfaced to marketing with the unique identifier of that user.

Also SAP_C4C_BUPA is another example, the c4c system also assignes a unique identifier to each business partner.

But the SAP_FORM just works differently as it doesn't assign a unique identifier to each form submit.

Usually, every origin that starts with SAP_ is best not to touch the default settings.

[former_member599277]

Hi Alessandro,

You wont be able to check the Change log but you can use the Browse Interaction data tile to check the Interactions for a particular contact , and in case of wrong Interactions , you can only delete them and may be reupload after configuration changes to correct the same.

Regards,
Saravana.