Salesforce account updates do not reflect in Marketo | Community
Skip to main content
I
ItayOved
Level 2
August 4, 2020
Solved

Salesforce account updates do not reflect in Marketo

  • August 4, 2020
  • 2 replies
  • 3493 views

Hi all,

We are seeing some massive discrepancies between SFDC and Marketo. We see it mainly (maybe only) at the account level. It seems that the first time the information comes in from SFDC to Marketo, the account data is updated but any further updates do not sync into Marketo (so for example, we don't see once an account becomes a paying customer since this update did not come to Marketo.)

 

We tried to manually update some fields on SF for some contacts, leads, and accounts - Only leads and contacts information was also updated in Marketo. The account information was not.

 

We're not sure what causes it - Is it something in the Salesforce objects sync section? Maybe we're not syncing the right objects?

Any one-time solution isn't sufficient since we're looking to fix that problem once and for all. No fields are blocked from updates.

 

What do you think?

 

Thanks!

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 Jay_Jiang

most common cause is field security settings in SFDC for your sync user. check your sync user's permission sets and field security access for all account fields. make sure it has write access.

2 replies

Ronen-Was-SRpro
Ronen-Was-SRpro
Level 5
August 6, 2020

Hi @itayoved,

 

Did you check the Notification tab to see what are the Sync errors that are specified there?

Ronen Wasserman
I
ItayOvedAuthor
Level 2
August 6, 2020

Hi Ronen,

Yup, I do see notifications that are "Marketo is unable to update Lead in Salesforce." (which is another issue that we have - though we just had a breakthrough!), but this is more of a "Salesforce is unable to update Lead in Marketo." type of issue - which I do not see any notification on that.

Jay_Jiang
Jay_JiangAccepted solution
Level 10
August 6, 2020

most common cause is field security settings in SFDC for your sync user. check your sync user's permission sets and field security access for all account fields. make sure it has write access.

Terms & ConditionsAccessibility statement

Loading footer...