SOLVED

Re: Creating Custom Score Fields

Go to solution
Anonymous
Not applicable

Creating Custom Score Fields

I'm confused. I'm doing a lead scoring project and created Demographic and Behavior Score fields in SFDC. There is no "Score" field type in SFDC so I checked to see what the Lead Score field type is and found it to be "number". This is true across multiple instances I have access to -  but it syncs over to Marketo as type Score. However, my new Behavior Score and Demographic Score fields synced over as type "integer." Yet in other instances, Behavior and Demographic score fields are type "number" in SFDC and type "score" in Marketo. What do I need to do to turn the Behavior and Demographic Score fields into type Score on the Marketo side?

Grégoire Michel​ or Sanford Whiteman​ - might one of you know the answer?

1 ACCEPTED SOLUTION

Accepted Solutions
Anonymous
Not applicable

Re: Creating Custom Score Fields

Hi Again - Found the answer. You create the custom field in SFDC as type Number and then in Marketo, change the field type to Score.

View solution in original post

4 REPLIES 4
Anonymous
Not applicable

Re: Creating Custom Score Fields

Hi Again - Found the answer. You create the custom field in SFDC as type Number and then in Marketo, change the field type to Score.

Grégoire_Miche2
Level 10

Re: Creating Custom Score Fields

Hi Denise,

Yes this is only partially correct

  • If you want the field to map with Marketo score field, you should have the salesforce field use a very specific field name "mkto71_Lead_Score" (the field label can be "score"), as explained in the doc here: Step 1 of 3: Add Marketo Fields to Salesforce (Enterprise/Unlimited) - Marketo Docs - Product Docs
  • Be aware that, since the last update to the salesforce connector, we have observed many issues on value sync from SFDC to Marketo if you create a custom field and change its type to "score" in Marketo: the values you set in SFDC are not pushed back to Marketo. This is really a problem if you want to use SFDC to sum up behavior + demographic as the total will not flow back to Marketo. The way we work around this is creating a formula field in SFDC. Calling it "Total Score" and make it the sum of B+D. when the field syncs with Marketo, we leave it to be an Integer field. Then in Marketo, we create a smart campaign that juts copies this field into the lead score with a "Data value change".

-Greg

Anonymous
Not applicable

Re: Creating Custom Score Fields

Hi Greg -

I understand that Lead Score needs to be mapped to mkto71_Lead_Score (and it is). However, I am talking about Behavior Score and Demographic Score. The intent is that these fields will be populated and updated by Marketo - not by SFDC. In fact, they are read-only in SFDC (except for the Marketo sync user). Marketo doesn't document (to my knowledge) any specific API name for these fields. Also, I hadn't intended to use SFDC to sum the fields. Given our use case - namely that we will push values to these fields from Marketo to SFDC but not the other way around, do you still foresee a problem with changing them from type integer to type Score?

Thank you,

Denise

P.S. I do like the idea of using a formula field in SFDC to sum B+D instead of having to increment L every time B or D is incremented but I already build the campaigns. For future reference - can you point me to documentation on how to do this? I'm pretty sure I could search and figure out how to build the formula field but how do you "trigger" it to do the sum whenever B or D is changed?

Grégoire_Miche2
Level 10

Re: Creating Custom Score Fields

Hi Denise,

Creating a formula field in SFDC is pretty straightforward and the formula assistant will make it easy. Just create that field on both lead and contact objects. The most important is to let this "total score" field to be an integer one in Marketo and not a score one, otherwise it will not sync back.

The big advantage of using this technique comes when in the future you recompute and/or reset behavior or demographic scores. Because then the total score remains accurately and easily computed.

-Greg