Why did lead change to person | Community
Skip to main content
Mark_Wallace1
Mark_Wallace1
Level 4
March 31, 2017
Question

Why did lead change to person

  • March 31, 2017
  • 3 replies
  • 2903 views

Anyone have any background on this?

3 replies

A
Anonymous
March 31, 2017

Hi Mark,

Marketo has rolled out new updates in the naming convention where there are updates in:

Field Name and Tokens

Real-Time Personalization (RTP)

Predictive Content

Lead Database

You can refer the following document for details: https://nation.marketo.com/docs/DOC-4218

Hope this will help.

Jagbir Singh

jagbirs@grazitti.com

    Mark_Wallace1
    Mark_Wallace1Author
    Level 4
    March 31, 2017

    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?

    Dan_Stevens_
    Dan_Stevens_
    Level 10
    March 31, 2017

    in addition to the URL provided above (see the comments posted) here is a related thread on this:

    When lead to person transition was a little too enthousiastic

    Dan_Stevens_
    Dan_Stevens_
    Level 10
    March 31, 2017

    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).

      A
      Anonymous
      June 6, 2017

      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.

        Terms & ConditionsAccessibility statement

        Loading footer...