Can Marketo fields be added to Salesforce after the initial sync? | Community

A

Anonymous

Question

Can Marketo fields be added to Salesforce after the initial sync?

Forum|Forum|8 years ago
April 26, 2017
3 replies
9221 views

Hello,

Can Marketo fields be added to Salesforce after the initial sync?

Thank you,

Maria

_ _ _ _

Clarification:

I actually meant to ask specifically about the "additional Marketo fields" such as Original Referrer, Acquisition Program ID, Inferred Company, Inferred City etc (the fields that come with pre-made Marketo API names) - not about new custom fields. I wonder if that changes things or not...

Thank you!

M.

Message was edited by: Maria Savelyeva

Marketo

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

Level 10

Maria,

Marketo fields won't be added to SFDC, rather you create a new SFDC field and create a new Marketo field and map them together. The alternative is to create the field in SFDC and add that field to the sync user profile and it will then be visible in Marketo for use.

More info: Add an Existing Salesforce Field to the Marketo Sync - Marketo Docs - Product Docs

Level 10

It is almost always better to create in SFDC, map between objects, and then expose to the Marketo User.

If you create the field in Marketo first, it is harder to connect back to SFDC (need Support); and there is potential data loss.

Level 2

Hey @Josh Hill -

Curious how did you get support to help with this? We have several fields that were created in Marketo that we'd like to get pushed to Salesforce. However, Marketo support isn't being very cooperative. Any help would be much appreciated.

Thanks,

-Troy

Level 5

You can ask the support to change the mapping of a custom Marketo field with another field in SFDC, if that field is visible to the Marketo user. As a best practice, it is always better to create a new field in CRM and then let it sync over to MKTO.

Darrell_Alfons2

Level 10

And don't forget to create it with the same API name on both the contact and lead object if applicable