Changes to Marketo Salesforce Sync – Questions and Discussion

[Mike_Reynolds2]

Updates to the Marketo Salesforce Sync Configuration

This discussion thread has been set up to ensure you get answers to your questions regarding the upcoming configuration changes between Marketo and Salesforce. It is being monitored by the Marketo team so please post any questions you have and we’ll be happy to get you answers!

Quick Overview

Due to changes to the SFDC integration architecture, action is required soon to continue syncing a small number of fields to your Salesforce instance. There are 16 fields affected, but most customers are only using a couple of these fields in their Salesforce instance – Lead Score and Acquisition Program. The configuration update will shut off the sync of data to the MLM package and these fields, so the data in those fields in SFDC will become stale and won’t update.

You can keep syncing this data to SFDC but it requires creating new custom fields. When the fields are re-created, a drip process will be triggered to backfill existing data from Marketo into the new fields in SFDC. If you aren’t using these fields, or aren’t using SFDC at all, this doesn’t apply to you and there’s nothing for you to do.

When to Make the Changes

The configuration changes are being scheduled over time into month-long groups. Please see the Release Schedule for specifics.

Important Note About Schedule Requests

Fields Affected

Lead Score Acquisition Program Acquisition Program Id Acquisition Date Original Search Phrase

Original Source Info Original Source Type Original Referrer Original Search Engine Inferred Company

Inferred Metropolitan Area Inferred Phone Area Code Inferred State Region Inferred City Inferred Postal Code Inferred Country

Where to go for More Information

Changes to Marketo Salesforce Sync – Frequently Asked Questions

Changes to Marketo Salesforce Sync - Overview

Changes to Marketo Salesforce Sync – Release Schedule

Changes to Marketo Salesforce Sync – Under The Hood

Adding Marketo Fields to Salesforce​

Changes to Marketo Salesforce Sync – Preventative Troubleshooting

New Related Discussion Threads

Is the Marketo lead management app still available? Initial set up required for Marketo to salesforc...​

Weird bug with "Score" field type?

All score fields have stopped to sync from SFDC to Marketo 

[Anonymous]

Hi Mike,

Will SFDC allow me to uninstall the MLM package if I have existing workflows and/or formula fields using the old fields?

Hoi

[Mike_Reynolds2]

Hoi Nguyen​

No, if the fields are in use anywhere else, referenced in workflows or anything else, then SFDC will give you an error when you try to uninstall it.

Mike

[Anonymous]

Can you tell me if the Inferred Company or ISP field will start showing the company name again? Do we have the ability to select what we want displayed (co v ISP)? Our anonymous web traffic report is much less useful with just an ISP shown rather than the company name.

Thanks much!

[Mike_Reynolds2]

Hi Lisa Edington​

I don't think the reporting issue you're seeing is directly related to this, but is part of the changes to how Anonymous leads are promoted to Known leads that started rolling out in the Winter 2016 release. We have some detailed documentation on that upgrade, but the specific one that applies here is the document on the changes to Analytics Reports.

Let me know if that helps!

Thanks,
Mike

[Anonymous]

Hi Mike,

Is there anything I need to do to prepare for the cut over? It sounds like the primary action item is to create the new fields with the mkto71_ prefix in the field name during our specified cut over time and the data will only backfill if you use the mkto71 prefix, is that correct?

Also wondering, why the 71 as a prefix?

Just want to make sure I'm not missing any steps before creating the new fields.

Thanks!

Mary

[Mike_Reynolds2]

Hi Mary Martin​

You'll definitely want to be sure to create the new fields during the scheduled window since that will kick off the backfill process. In terms of what to do ahead of time, we do have some documentation here that goes over common things to look for: Changes to Marketo Salesforce Sync – Preventative Troubleshooting

As for the prefix to the fields, why the specific prefixes uses the 71, honestly I'm not sure. The easy answer is that it's not used elsewhere, which prevents conflicts with other API names. But why 71 as opposed to 15 or 94712, I'm not really sure. It was designed by our Engineering team with the goal of preventing it from being already in use elsewhere as API names.

Does that answer your questions? Let me know if there's anything else I can help with.

Thanks,

Mike

[Anonymous]

This is a great post, thanks

[Anonymous]

Hi Mike,

We use Lead Score in many of our Marketo campaigns. Will we need to update these Marketo campaigns to reflect the newly created Lead Score field? If so, what is the best and quickest way to see all the campaigns in our Marketo instance that uses the field "Lead Score"?

The same applies to our Salesforce workflows and formula fields. What is the best and quickest way to see all affected workflows and formula fields?

Thanks,

Hoi

[Mike_Reynolds2]

Hi Hoi Nguyen​

The Marketo side will be completely unaffected. No fields in Marketo are changing at all. The same Lead Score and others will stay the exact same as they've been, so no campaigns in Marketo will need to be changed at all. The only difference is which field on the Salesforce side that these Marketo fields are mapped to. That change will only affect Salesforce and has no affect within Marketo at all.

Inside of Salesforce, everything that references the older fields must be updated to reference the newly created fields instead. We have the doc here that talks through this in more detail: Changes to Marketo Salesforce Sync – Preventative Troubleshooting

I can't really tell you how to get info out of SFDC since it's not our product. What I can tell you is that if the fields are in use, you won't be able to delete/uninstall them. If you try, my guess (and this is a complete guess--again, it's not our product) is that it should tell you where they're in use. Best bet would be to check with SFDC Support for more details there.

Hope that helps!

Mike

[Anonymous]

Hi,

I am confused on how to work this out. The fields already exist, so should i delete the fields on sales force and then recreate for Lead, Contact and Account. If there are any other fields do let me know.

Regards

Vyshak

[Mike_Reynolds2]

Hi Vyshak Simha​,

You'll want to create the fields just on the Lead and Contact objects. No need to do it on the Account object. Once the new fields are created, that's when you'd want to uninstall the MLM package, which will in turn delete the old fields for you.

You'll only need to worry about the affected fields listed here. No others will be affected other than these ones.

Let me know if you have any other questions at all!

Thanks,

Mike

[Anonymous]

If I only leverage the "Lead Source" field, do I need  still need to make this update? 

Lead Source is a native field in SFDC, so I'm confused why this field would need to be replicated.  It makes sense for the others.

Please advise.

[Grégoire_Miche2]

Hi Alicia,

No, nothing to worry about. Lead source is not part of the MLM package. As you pointed out, it's a std SFDC field.

-Greg

[Anonymous]

Thank you! 

[Anonymous]

Hi,

We would like to have any new data synced to these fields but do the backfill ourselves. The way we were anticipating doing this is to create the new fields AFTER the backfill window closes (october 1 for our group).

I normally work on the salesforce side of things, so would like some feedback on this plan, specifically:

1) By creating these fields after the window close date, will it actually block the backfill?

2) We will NOT loose any existing data in the legacy fields.

3) The new fields will receive data even if they are created on / after october 1

thanks

[Mike_Reynolds2]

Hi Andrew Johnson​

The creation of the new fields is what initiates the backfill process. There isn't any way to create the fields without immediately starting that backfill process, so as soon as you create them, it kicks off. The scheduled time for your window is the time frame for when you should create the fields. Whether you create the fields today, October 1st or July of next year (after the whole process is completed and after the data stops syncing on January 31st), whenever those fields are created, that's when the backfill begins.

If the scheduled timeframe doesn't work for you, we can reschedule you to a different group - just Contact Marketo Support and we'll be happy to work on getting you into a different group.

There won't be any loss of data at all, no matter when you recreate the fields and start the backfill process. The only thing to keep in mind is that the data will stop syncing to the existing legacy fields after January 31st.

Hope that helps! Let me know if there are any other questions I can answer at all.

Thanks,
Mike

[Jason_Hamilton1]

Hi Mike Reynolds,

I believe you have answered this question a hundred times by now but want to confirm that for the new fields we create we use the actual API field names listed in the doc provided (mkto71_...) I just want to be sure that mkto71_ is not just a placeholder.

Thanks,

Jason

[Mike_Reynolds2]

Hi Jason Hamilton​

Yes, you'll definitely want to make sure you're using the API names just as they're given in the doc. Adding Marketo Fields to Salesforce Enterprise/Unlimited Edition The "mkto71_..." piece is used at the start of all of the fields, but isn't just a placeholder--it's part of that API name, so be sure to include it just as it's given there. Let me know if you have any other questions at all!

Thanks,

Mike

[Jason_Hamilton1]

Awesome, thats what I thought, thanks for the quick reply.

[Anonymous]

Thanks, thi is really helpful

[Mia_Whitfield]

Additional question for you, Mike... we just refreshed our Salesforce sandbox... I had been planning to install MLM before connecting it to our Marketo sandbox... instead, should I create the fields as you document above (even though our window isn't until October)?