New SFDC Object for GDPR : Individual | Community
Skip to main content
Level 1
May 11, 2018
Question

New SFDC Object for GDPR : Individual

  • May 11, 2018
  • 2 replies
  • 4187 views

Has anyone looked into the functionality/Marketo integration potential of the new SFDC Object they are calling "Individual"?

Reference article:  medium.com/@Q9ELEMENTS/gdpr-compliance-and-salesforce-individual-object-bf41e04e7fa3

Our company is trying to decide if we add new fields and process steps in SFDC to sync with the new fields we added in Marketo (Opt in date, Opt in source, etc)

Or if we could use this new object in SFDC.

Any thoughts on this yet?

Thanks!

2 replies

Grégoire_Miche2
Level 10
May 11, 2018

Hi Dana,

I am pretty surprised that none had asked the question yet

I have. For the moment, this object is ignored by Marketo. I have not even been able to map it as a custom object, probably because the SFDC API version Marketo connector is using does not render it. This means you will not been able to read it from Marketo, and even less update it.

Vote here:

I would recommend that, with regards to GDPR, Marketo be your source of trust rather than SFDC. and this is because the activity log provides you with information such as IP addresses on form fill out and cannot be tempered with.

-Greg

Veronica_Holme4
Level 9
May 22, 2018

Honestly at the moment I have to advise people using Salesforce and Marketo not to go down the road of the Individuals object. But it's quickly not cutting it. It has to be supported, and soon. But it definitely isn't right now.

Grégoire_Miche2
Level 10
May 22, 2018

Hi Veronica,

We have been investigating the Individual object form strictly a SFDC perspective and for the moment it's added value is almost zero. It cannot be populated even from a SFDC web-to-lead form and it has no impact whatsoever.

It's an interesting step towards the unicity of the person, which is one of SFDC bigger weakness with regards to Marketing*, but for the moment, it's really limited and SFDC doc about it simply says that it will evolve in the future. The only way it seems you can make use of it is if you are using Pardot. I am not even sure that SFDC API enables you to access it...

-Greg

* Remember the lead object conception is dated back the the end of the 90's and was created in a time where a lead was converted into an opportunity or deleted, never recycled, and in which the first and last touche campaign were usually the same (which is why SFDC standard attribution model is last touch).

Veronica_Holme4
Level 9
June 4, 2018

I wasn't aware Pardot could use it, which is interesting information.

The real issue I'm having with it is that it is encouraging a whole wave of Salesforce consultants to now bring out keeping deliberate duplicates in Salesforce and uniting them through the "Individuals" object (which Marketo can't see) as a legitimate strategy, even though most of Salesforce's own processes, including Process Builder, won't even be able to access the object on first release. Over the next year or so though I think we're going to find a lot of businesses moving to a model that Marketo will struggle to support, because we all know how fun managing deliberate duplicates is in Marketo if you are doing any inbound marketing through forms... Best case future state is we are able to configure the Marketo sync to only look at the individuals object, not the lead or contact, if businesses go down this road. The sync has needed extra levels of flexibility for a looooong time.