8 Replies Latest reply on Aug 12, 2016 4:12 PM by Sanford Whiteman

    Marketo Field Clean Up

    Lisa Heay

      I am working on a Marketo to Marketo migration for a client and am working to clean up their list of fields.  Their previous instance has 280 fields, a lot of which are not being used or are redundant and do not need to be moved to their new instance.  It would be helpful as I organize my list to get a quick list of the standard Marketo fields as a starting place so that I know which ones I have control over changing.  I've poked around in the Help articles but can't seem to locate one.

       

      I am also hoping someone could give me a quick tutorial on Rest and Soap API.  I exported the field list, and there are columns for each API name.  Hoping there are clues in the field naming that will let me know if the field was came from a Salesforce integration or integration with another tool.

       

      Any help would be much appreciated!

        • Re: Marketo Field Clean Up
          Nicholas Manojlovic

          Hey Lisa,

           

          Here is a list of standard fields: List of Standard Fields » Marketo Developers

           

          You can also export a list of the fields you are currently using in your Field management section of the Admin area.

           

          There is no access to the fields via API.

          1 of 1 people found this helpful
          • Re: Marketo Field Clean Up
            Lisa Heay

            Thank you both - the list of standard fields helps. 

             

            As for the API part of my question - I probably didn't ask the right question.  Here is what I am doing:

             

            I had exported the list of fields being used in their Marketo instance via Admin > Field Management.  In the spreadsheet generated, I am working through each field to determine where the field originated from (i.e. Marketo Standard Field, SFDC, or another plug in or integration) so that when we move to a new instance, we can eliminate some of the fields that are no longer needed or redundant with other fields.  I was hoping that the columns for Rest API or SOAP API would offer me some kind of clue as to where the field came from.  I think they do to some degree, but I don't want to make any incorrect assumptions.

             

            Here are a couple of examples of what I am seeing (Friendly Marketo Name --- REST API Name):

             

            Activation Date --- Activation_Date__c

            Admin Score Increment --- CFCR_Admin_Score_Increment__c

            Hide Date --- mkto_si__HideDate__c

            Infer Encoded Rating --- infer3__Encoded_Rating__c

            Person Notes --- mktoPersonNotes

             

            What does the "__c" indicate? 

            Is "mkto_si" a standard field as part of Marketo Sales Insight? 

            I am assuming the fields that begin with "infer3__" were added from their Infer Lead Scoring. 

            Are fields that begin with "mkto" a custom field created in Marketo?

             

            Is there a list of standard fields that get added from integrated tools?

              • Re: Marketo Field Clean Up
                Sanford Whiteman
                • *__c -- SFDC custom field
                • mkto_si_* -- Marketo Sales Insight
                • mkto* -- meant to denote Marketo-originated, but technically can be used for any field; mktoPersonNotes is a Marketo standard, not custom, field that is mapped to SFDC Description
                  • Re: Marketo Field Clean Up
                    Lisa Heay

                    Thank you!  Appreciate the help. 

                    • Re: Marketo Field Clean Up
                      Lisa Heay

                      Since you're helpful and quick....are these the right assumptions?

                       

                      sfdcAccountId, sfdcContactId, etc - Assuming these are standard SFDC fields that get added to Marketo when the two become integrated.

                       

                      Finally, there are a few others that are not listed on the Marketo Standard field list that have the same Rest API naming convention, like:

                      behaviorScore, EmailBouncedDate, reportID, demographicScore, contactUsFormDescription.  I know that at least Behavior Score and Demographic Scores are Marketo fields - but not sure why they aren't part of the "Standard" field list.

                       

                      behaviorScore
                        • Re: Marketo Field Clean Up
                          Sanford Whiteman

                          sfdcAccountId, sfdcContactId, etc - Assuming these are standard SFDC fields that get added to Marketo when the two become integrated.

                          In effect, yes. Though sfdcContactId and sfdcLeadId, in some contexts but not all, are viewed only through the standard function field (that is, macro field) SFDC Id.

                           

                          As I pointed out on my blog, it can get very confusing when you're dealing with different definitions of "custom" and "standard" -- and even different definitions of "field"!

                           

                          Finally, there are a few others that are not listed on the Marketo Standard field list that have the same Rest API naming convention, like:

                          behaviorScore, EmailBouncedDate, reportID, demographicScore, contactUsFormDescription. I know that at least Behavior Score and Demographic Scores are Marketo fields - but not sure why they aren't part of the "Standard" field list.

                           

                          Because they're not standard given the public UI definition.  They may be standard SFDC fields and part of the standard mapping table in Marketo, but they don't qualify as standard fields.

                      • Re: Marketo Field Clean Up
                        Sanford Whiteman

                        Is there a list of standard fields that get added from integrated tools?

                        This wouldn't be practical because managed stuff you add to SFDC is going to add its own range of fields that may or may not be visible to Marketo and may change over time.