Partial Sales Force integration? | Community
Skip to main content
J
Julz_James
Level 8
January 30, 2015
Solved

Partial Sales Force integration?

  • January 30, 2015
  • 4 replies
  • 2014 views
Hi everyone,

We have a number of workspaces and partitions in our edition of Marketo, and this maps through to SFDC.  However, for some reason we have a large number of SFDC fields (400+) syncing across.  What I wanted to know was - can we pick and chose what syncs across by workspace/partition?  Or am I able to have a full sync on one workspace/parition and then have a rule set so only MQL's are sync'd across in another workspace/parition?

Any help would be much appreciated :-)

Thanks

Juli
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by
Hi Juli--

You can only define which fields sync between Marketo and SFDC and the instance level, meaning you cannot set different sync settings between workspaces. It IS possible to unsync fields though, if you feel like 400 is too many and it's slowing down your system performance. You can hide the fields from the Marketo sync user in SFDC, and hide them in the admin setting of Marketo. If you want to be extra thorough, you can create a support ticket with Marketo to have them officially removed.

As for the second part of your question, when you say "sync across," are you talking about lead records, or fields? It's hard to answer accurately without knowing more about your lead partition settings. It is possible to set up different lead lifecycles within each workspace to individually control when MQL leads are synced to SFDC. (It's a bit more complicated if you have lead partitions that are visible in more than one workspace. Leads in a shared partition would qualify for syncing in more than one workspace.)

That's a bit of a complicated answer. Hope it helps!

Kate

4 replies

A
Anonymous
January 30, 2015
Hi Juli, 

If you want to restrict the number of fields synching from SFDC, you can adjust the field level security for your SFDC integration user so those fields are not visible for them. That will prevent them synching. 

However the second part of your question seems to refer to selecting which leads you synch from Marketo to Salesforce based on partition, which is a bit different. 

I don't use partitions myself but I believe you would control this relatively easily by adding some additional logic to the campaign that synchs leads to SFDC. When you are building your rules as to when this happens you would add some additional filters or choices based on the partition the lead is in. 
A
Anonymous
Accepted solution
January 30, 2015
Hi Juli--

You can only define which fields sync between Marketo and SFDC and the instance level, meaning you cannot set different sync settings between workspaces. It IS possible to unsync fields though, if you feel like 400 is too many and it's slowing down your system performance. You can hide the fields from the Marketo sync user in SFDC, and hide them in the admin setting of Marketo. If you want to be extra thorough, you can create a support ticket with Marketo to have them officially removed.

As for the second part of your question, when you say "sync across," are you talking about lead records, or fields? It's hard to answer accurately without knowing more about your lead partition settings. It is possible to set up different lead lifecycles within each workspace to individually control when MQL leads are synced to SFDC. (It's a bit more complicated if you have lead partitions that are visible in more than one workspace. Leads in a shared partition would qualify for syncing in more than one workspace.)

That's a bit of a complicated answer. Hope it helps!

Kate
    Josh_Hill13
    Josh_Hill13
    Level 10
    January 30, 2015
    Kate is correct.

    If you wanted to restrict leads syncing by Workspace/LP then you'd have to set up complex logic on the SFDC side to block leads by whatever WS criteria as well as setup that logic on the Marketo side within each WS.
    I don't recommend it. Makes life harder.
    J
    Julz_JamesAuthor
    Level 8
    January 30, 2015
    Thanks everyone!  The issue is because we sync across so many fields (most of which are not needed or used) some of the overwritiing in SFDC is causing issues.  

    However the infromation about restricting what leads sync across to SFDC set up WS/LP is very useful.  We have different criteria for MQL's between International Markets and American Markets, so at the moment everything in Marketo is being sync'd across and sitting in a Marketing Queue.  In International we only want MQL's or certain Form Fills to trigger a sync.  The workspaces and paritions are seperated so International leads only sit in the International Parition and Workspace.
    Terms & ConditionsAccessibility statement

    Loading footer...