I have a question about how a field that is created in SFDC on the lead and account objects and mapped appears in Marketo once it syncs over.
If I go into SFDC and create a field called MKTO Test as a custom field on the Lead and Account object. Immediately after creating the two fields, I map the custom lead field to the custom account field. When this field syncs over to Marketo, how should I expect to see this field in Field Management?
OPTION A: One Field - I will see the MKTO Test field appear as one field in Field Management
OPTION B: Two Fields - I will see a MKTO Test and a MKTO Test (A) field appear in Field Management
Which of these two options is the expected behavior?
Option B is the expected behavior since the fields are created one by one in SFDC. You'll have to create a support ticket to have the fields merged in Marketo so that you can have things function like Option A.
Thanks for your reply, Andy Varshneya. What confuses me is that if you do the same process I described above and map a custom Lead field to a custom Contact field (instead of a custom Account field) in SFDC, they will automatically map into one field when they sync over to Marketo.
Option B is what I've seen happening in our instance. However, in the past no one took the time to get these fields merge, which has resulted in a lot of mistakes in our instance, lost data upon lead conversion, and the running list I've created to send over to Support to fix. It's ridiculous to have to open a Marketo Support case anytime you want to ensure that data isn't lost upon lead conversion and I can't imagine how many support tickets Marketo deals with on a daily basis having to fix these issues because there is no way for the end user to do this themselves.
Try to turn off the sync while creating and mapping new fields in SFDC, so that Marketo gets access to them after they are mapped correctly.
Well what you need to remember is that Marketo's objects don't line up perfectly with SFDC's. SFDC has different objects for Leads and Contacts while Marketo has a single object for People.
And yeah, it's pretty frustrating but from what I understand they did it because people would incorrectly map the fields and end up doing more damage than good, and creating support tickets to fix those bigger problems.