2 of 2 people found this helpful
Marketo has rolled out new updates in the naming convention where there are updates in:
Field Name and Tokens
Real-Time Personalization (RTP)
You can refer the following document for details: https://nation.marketo.com/docs/DOC-4218
Hope this will help.
So if a host of web APIs are populating Lead source and its now Person source (which doesnt make sense) do i need to rapidly correct all of the web integrations?
The primary reason was to avoid confusion with the lead entity in CRM (since Marketo refers to both CRM contacts and leads as "leads"). Many are welcoming this change as long as it doesn't disrupt/impact existing workflows (where references to lead.xxx records may have been inadvertently changed to person.xxx).
Have to agree this change doesn't make sense to me either - yet another field that says X in Marketo, but it's actually Y in Salesforce - this is MORE confusing, not less. A compromise for changes like this would be to allow users to change the label to what they prefer - something Salesforce offers, even on standard fields and objects.