Person Partitions & Salesforce Sync | Community
Skip to main content
A
Anonymous
April 30, 2018
Solved

Person Partitions & Salesforce Sync

  • April 30, 2018
  • 2 replies
  • 5353 views

Hi,

I am getting ready to set up 2 new person partitions in 1 marketo instance to account for 3 different brands. Salesforce is currently synced to the Marketo database. How does adding two new person partitions affect the Salesforce sync? Will it continue to sync as it does now to the current database or will I need to write some additional logic on the back end once I've created the two new person partitions to ensure that Salesforce is syncing to the correct database?

Thanks,

Courtney

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 Grégoire_Miche2

Hi Courtney,

This is not that easy to prevent records to sync to SFDC. The only safe way to do it is the following:

  • Create a lead field in SFDC. call it "Mkto Insertion Authorized" make sure the Marketo sync user has access to this field. Let it be created into Marketo
  • Flag this field for all your SFDC leads (you can set a smart campaign for this in Marketo: Filter: SFDC Sync [Perrson] not empty. Flow Step: Change data value, field is "Mkto Insertion Authorized", new value = True
  • Create a validation rule in SFDC that block creation of leads when this field is not flagged and the creating user is the Marketo sync.

You will then be able to use the "Mkto Insertion Authorized" field to control which records are inserted into SFDC.

Another way to look at this is through segmentation of duties between the workspaces:

  • all "sync" tasks in the B2B workspaces, none in the global workspace, none in the B2C Workspace
  • No program/SFDC campaign sync in the global workspace nor in the B2C workspace
  • No "add to SFDC campaign" and alike in the global workspace nor in the B2C workspace

This a topic covered here: Marketo / salesforce integration needs a serious overhaul, don't you "sync"? and more precisely vote here:

-Greg

2 replies

Jim_Thao7
Jim_Thao7
Level 8
May 1, 2018

If all you're creating is partitions, you should have no worries because you should by default have just 1 single workspace that has visibility into all of the partitions (at least that's what I would hope you have).  If you have more than 1 workspace and those workspaces have visibility into specific partitions, you need to make sure that any campaigns you created around SFDC processes are in the workspace that has access to all partitions.

Grégoire_Miche2
Grégoire_Miche2
Level 10
May 1, 2018

Hi Courtney,

The partitions have no effect on the salesforce sync directly. In fact, salesforce even ignores in what partition a lead is and does not need to have this info to sync the lead.

Chat you need to pay attention to is that the smart campaigns that push the leads to SFDC are located in a workspace that access the leads. There are various ways to implement this : it can be centralized in a workspace that can access all partitions (which is a safe workspace to have, as pointed out by Jim) or you can have different lead lifecycle campaigns in various workspaces, one for each partition. This is fact depend on your organisation and your business processes.

-Greg

A
Anonymous
May 1, 2018

Great, this is very helpful. Is there a way so that leads in one of the partitions that are tied to a separate workspace, won't be synced to Salesforce? Basically two of the product lines are B2B and one of the product lines is B2C. We want to be able to target those B2C prospects with marketing emails, etc. but sales does not need to have visibility into them or be following up with them at this time given the current business model. Is it possible to make sure that those B2C leads in that person partition are not synced to Salesforce?

Grégoire_Miche2
Grégoire_Miche2Accepted solution
Level 10
May 1, 2018

Hi Courtney,

This is not that easy to prevent records to sync to SFDC. The only safe way to do it is the following:

  • Create a lead field in SFDC. call it "Mkto Insertion Authorized" make sure the Marketo sync user has access to this field. Let it be created into Marketo
  • Flag this field for all your SFDC leads (you can set a smart campaign for this in Marketo: Filter: SFDC Sync [Perrson] not empty. Flow Step: Change data value, field is "Mkto Insertion Authorized", new value = True
  • Create a validation rule in SFDC that block creation of leads when this field is not flagged and the creating user is the Marketo sync.

You will then be able to use the "Mkto Insertion Authorized" field to control which records are inserted into SFDC.

Another way to look at this is through segmentation of duties between the workspaces:

  • all "sync" tasks in the B2B workspaces, none in the global workspace, none in the B2C Workspace
  • No program/SFDC campaign sync in the global workspace nor in the B2C workspace
  • No "add to SFDC campaign" and alike in the global workspace nor in the B2C workspace

This a topic covered here: Marketo / salesforce integration needs a serious overhaul, don't you "sync"? and more precisely vote here:

-Greg

    Terms & ConditionsAccessibility statement

    Loading footer...