Best way of limiting Salesforce records from going to Marketo | Community
Skip to main content
Tom_Hauervig
Level 1
September 6, 2017
Question

Best way of limiting Salesforce records from going to Marketo

  • September 6, 2017
  • 1 reply
  • 2757 views

Hi

I am currently looking into limiting salesforce records from going into Marketo. We have a lot of private person records and contact persons that are not relevant for marketing purposes which we do not need in Marketo. All leads form Salesforce will still go into Marketo

As far as I can read on the community then there are two ways of doing this and I am trying to decide which would be the best approach

  1. One is to implement a sync to Marketo checkbox and have Marketo support use that as a filter in the back end and then we can use different rules in Salesforce to populate this field as true.
  2. The other is to prevent the Marketo Sync user in Salesforce from seeing the record via sharing rules in Salesforce.

What do I need to think about in order to choose the best solution? Any thoughts on this would be greatly appreciated

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

1 reply

SydneyMulligan
Level 7
September 6, 2017

Hi Tom! The best way to do this in my opinion is to have Marketo Support set up the custom sync with a field you build in SFDC on the Lead and Contact. It's quite simple and quick to have them do this, and you have total control over how to populate the field in Salesforce.

September 25, 2017

Hi,

Do you know if the custom "do not sync" checkbox is also restricting records in an ongoing practice?

I understood that this can only be used for the initial sync. Did I miss anything?

Thank you

SydneyMulligan
Level 7
September 25, 2017

Nope, it is ongoing! I set up a simple trigger campaign in Marketo so if anyone's Block from Marketo field changes to TRUE, it deletes the lead from Marketo but doesn't delete it from the CRM. The custom sync filter set up through Support keeps it from being re-synced unless the field is changed back to FALSE in the CRM.