Adding Custom Marketo Fields to Salesforce | Community
Skip to main content
Mike_Reynolds2
Level 10
August 5, 2016

Adding Custom Marketo Fields to Salesforce

  • August 5, 2016
  • 53 replies
  • 26309 views

Included in this article

Overview

Marketo uses a set of fields to capture certain kinds of marketing related information. If you would like this data in Salesforce, please follow the instructions below.

  1. Create three custom fields in Salesforce on the lead and contact objects: Lead Score, Acquisition Program, and Acquisition Date.

  2. Map these custom fields between leads and contacts so that on conversion in Salesforce, the values carry over.

  3. You can create other additional fields, if necessary (see the table below).

All of these custom fields are optional and are not required to sync Marketo and Salesforce. As a best practice, we recommend that you do create fields for Lead Score, Acquisition Program, and Acquisition Date.

Add Marketo Fields to Salesforce

Add three custom fields on the lead and contact objects in Salesforce listed above. If you want to add more, see the table of available fields at the end of this section.

Perform the following steps for each of the three custom fields to add them. Start with Lead Score.

1. Log into Salesforce and click Setup.

2. In the Build menu on the left, click Customize and select Leads. Click Fields.

3. Click New in the Custom Fields & Relationships section at the bottom of the page.

4. Choose the appropriate field type (for Lead Score — number; Acquisition Program — text; Acquisition Date — Date/Time).

5. Click Next.

6. Enter the Field Label, Length, and Field Name for the field, as shown in the table below.

Field Label

Field Name

Data Type

Field Attributes

Lead Scoremkto71_Lead_ScoreNumberLength 10
Decimal Places 0
Acquisition Datemkto71_Acquisition_DateDate/Time
Acquisition Programmkto71_Acquisition_ProgramTextLength 255

7. Click Next.

8. Specify the access settings and click Next:

  • Set all profiles to Visible and "Read-Only".
  • Uncheck "Read Only" for the profile of your sync user.
  • Often customers have a user with the profile of a System Administrator as the sync user. If that's the case with you, then uncheck “Read Only” for the System Administrator profile as shown in the picture below.

  • If you have created a custom profile for the sync user, then uncheck "Read-Only" for that custom profile

9. Choose the page layouts that should display the field.

10. Click Save & New to go back and create each of the other two custom fields. Click Save when you're done with all three.

11. In the Build menu on the left, click Customize and select Contacts. Click Fields.

12. Perform steps 3 through 10 for the Lead Score, Acquisition Date, and Acquisition Program fields on the contact object, just as you did for the lead object.

13. Optionally, use the above procedure for any additional custom fields from this table.

     NOTE: These fields are additional optional fields you may choose to add as well. The Lead Score, Acquisition Date and Acquisition Program fields      are detailed above

Field Label

Field Name

Data Type

Field Attributes

Acquisition Program Idmkto71_Acquisition_Program_IdNumberLength 18
Decimal Places 0
Original Referrermkto71_Original_ReferrerTextLength 255
Original Search Enginemkto71_Original_Search_EngineTextLength 255
Original Search Phrasemkto71_Original_Search_PhraseTextLength 255
Original Source Infomkto71_Original_Source_InfoTextLength 255
Original Source Typemkto71_Original_Source_TypeTextLength 255
Inferred Citymkto71_Inferred_CityTextLength 255
Inferred Companymkto71_Inferred_CompanyTextLength 255
Inferred Countrymkto71_Inferred_CountryTextLength 255
Inferred Metropolitan Areamkto71_Inferred_Metropolitan_AreaTextLength 255
Inferred Phone Area Codemkto71_Inferred_Phone_Area_CodeTextLength 255
Inferred Postal Codemkto71_Inferred_Postal_CodeTextLength 255
Inferred State Regionmkto71_Inferred_State_RegionTextLength 255

Map Custom Fields for Conversions

A custom field on the lead object in Salesforce should be mapped to a contact field on the contact object so that data is carried over when a conversion occurs. 

1. In the top right corner, click Setup.

2. Type "Fields" into the Nav Search without pressing Enter. Fields appears under different objects; Click Fields under Leads.

3. Go to the Lead Custom Fields & Relationships section and click Map Lead Fields.

4. Click the drop-down next to the field you want to map.

5. Select the corresponding contact custom field.

6. Repeat the above steps for any other fields you've created.

7. Click Save when you're done.

Here's a video of the entire process that should make it easy to follow along: Salesforce Connector Setup

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

53 replies

September 16, 2016

Thanks, that's what I figured, but wanted to be sure.

(It could be made more explicit in the instructions. :^)

September 16, 2016

Once this is configured, how do we see / know it's working properly?

Just keep checking to see if the new fields are populated?

Mike_Reynolds2
Level 10
September 16, 2016

If you're doing this as part of the recreation of the fields for the changes to the SFDC Sync configuration change, the recreation of the fields will kick off a backfill process to pull existing data from the Marketo fields over into the newly created SFDC fields.

Even if you aren't creating the fields for that purpose (like for a brand new setup instead), it will still pull over all of the existing values from Marketo into these SFDC fields automatically. Since these are brand new fields in SFDC, no lead/contact records will have any values in them, so a quick report looking for any records that do have a value will show you the records that have been updated so far (assuming you have some leads in Marketo that have a value there to be pulled over). Give it a little time to get some fields updated - it pushes data at roughly 10k records per hour, but it shouldn't take long to at least get some records updated.

Thanks,

Mike

September 16, 2016

Heads-up for others....

We do a lot of copying Lead fields to other fields, or other objects (e.g. campaign members) to be able to propagate them downstream to multiple objects (contact, oppty, member) for reports, etc.

e.g.

if( isblank(ContactId),Lead.mkto2__Acquisition_Program__c, Contact.mkto2__Acquisition_Program__c )

If you do the same, you'll need to go an update those formulas...

Mike_Reynolds2
Level 10
September 16, 2016

@David Howard​

An excellent point! We have this troubleshooting doc Changes to Marketo Salesforce Sync – Preventative Troubleshooting to spot things like this. You happened to mention this right as I was in the middle of adding a new section to it to speak to the formula field issue as well

-Mike

September 16, 2016

Need to go and update reports and list views as well, to pull the new fields...

Mike_Reynolds2
Level 10
September 16, 2016

Reports are included in that doc. Take a look here and let me know if that's what you're referring to.

September 16, 2016

It is.

You might add a note to prompt people to go into their list views and reports and remove the old field and update with the new "mkto71_" field...

October 19, 2016

I created the fields with the apis as requested, but they don't seem to be backfilling.  What can we do to check to see what is not set up correctly?  Thanks!

Mike_Reynolds2
Level 10
October 19, 2016

HI @Kathleen O'Connell​

The backfill process runs in the background through a separate communication pipeline, so seeing the results immediately may be a challenge even when it's working properly. Marketo will give you an instance notification as soon as the backfill process has completed, but if it's not actually running, it'd never finish, so you'd never get that notification. If you're not seeing any values in any of those fields for any records, it's possible that something isn't running properly. Contact Marketo Support and we'll be able to use the back end tools we have to check it and make sure it's running properly.

-Mike