Combination ID_Origins and Marketing Area

[vervinckt_joyca]

Dear all,

I have a question regarding customer data coming from origins vs marketing area's.

Suppose we have origin "website" and have two marketing areas for two brands, AREA1 and AREA2.

We interface some contact data with origin Website, ID 123 and marketing AREA1 (e.g. John Doe, johndoe@gmail.com).

Then data comes in from origin WEBSITE, ID 123 but marketing AREA2 (e.g. John Doe, Main Street 2, doejohn@gmail.com).

Then this contact asks to brand from AREA2 to delete all his data (GDPR right to be forgotten).

How can we then only delete data from AREA2 without deleting data from AREA1?

as the origin was "website" both times; the job to remove origin data wouldn't cover this...

Anyone an idea?

Kr,

Joyca

[Former Member · Accepted solution]

Hi Joyca,

very good point. I double checked and would not see an option to make it happen as of now. The deletion report always deletes the full golden record.

I believe you should create a SAP Influence item out of this one.

Cheers, Anton

[former_member267312]

Hi Joyca,

I'm not sure whether I understood your business requirement. Sounds like you want to build a golden customer record based on marketing areas (i.e. have separate records based on marketing area). Why don't you implement custom logic to map and merge contacts based on marketing area?

The way you described your scenario makes me wonder how you want to achieve to implement duplicate ID_ORIGINs (same ID_ORIGIN, same ID) for one contact without just updating one facet.

Otherwise I guess it'd make more sense to have separate ID_ORIGINs as well.

Hope this makes sense.

BR

Theo

[vervinckt_joyca]

Hi Theo,

No, I don't need two separate records for each marketing area; it should be one golden record still.

It's just when a customer asks to "be forgotten" and he asks that to one specific marketing area (area's can be brands or sister companies within the same company for example), then you would not want that their info is removed from the other marketing area as well (as the customer did not ask to be forgotten to that other area).

Like on the SAP Help example image:

https://help.sap.com/doc/PRODUCTION/ac1eab4c66bc490da7ac2c378c46b0e7/1808.500/en-US/loiocd78c8281f86...

In that picture, if you'd want to delete the data associated with area A.

To get technical, I think that ID_Origin+ID is the Key of the facet data table and that marketing area isn't a part of the Key... So I'm afraid that my requirement wouldn't be possible currently. Unless indeed you go create many extra Origins e.g. WEBSITEAREA1 and WEBSITEAREA2 instead of just WEBSITE.

Kr,

Joyca

[former_member267312]

Hi,

As far as I know marketing area is (like you suspected) not part of the facet keys and thus your scenario of building a golden record with several "duplicated" facets would not work as the key pair ID_ORIGIN + ID does not allow duplicates (and marketing area is not considered). So I guess before worrying about deleting certain records you first need to make sure that you get the data in (as separate facets). In my opinion several ID_ORIGINs would be required.

BR

Theo