Have any other SFDC / Marketo users found that SFDC is reversing unsubscribe information and then overwriting the Marketo values?
I'm having a problem where someone will unsubscribe, things will be perfectly updated in Marketo, Marketo will sync with SFDC, and SalesForce will then reverse the unsubscribe. (SERIOUSLY?! Yeah, I know.)
Has anybody else had this problem? Marketo support could only tell me it's got to be resolved on the SalesForce side, and my SFDC admin can't figure it out.
Did you find a solution to your issue? We are currently facing a similar problem and we are stuck. We were told to check the field permissions for the Salesforce Sync user and to take a look at our SFDC workflows. Our SFDC admin took a look at both but couldn't figure it out.
Please let me know if you have luck on your end. Thanks!
Timothy, the field permission is read-only and visible for all SFDC user profiles. If you can remember how you solved it, I'd love to know so I can get this fixed!
Andrew, I haven't been able to get this resolved yet...SalesForce's support team is looking at it, but they haven't made any progress yet. I'm supposed to hear back from them today, and I'll post any progress/ideas/etc they have.
We're in a similiar position. The user profile has read/write access to the opt out field. We looked into our workflows to see if that was the issue but it doesn't look like it is. It takes about 10-15 minutes for the SFDC sync to revert the unsubscribe.
I've looked at a few of them...they're all happening right away for me. Someone will unsubscribe, and within 10-15 minutes, that info is synced over to SFDC (odd, b/c I thought the sync was usually every 5 minutes). Then, Marketo will sync with SFDC, and the very next line will show (at the same time) a Change Data Value for the unsubscribe field - from True to False. When I called Marketo Support, they said the change was coming over from SalesForce when Marketo was trying to update the SalesForce data.
So it doesn't seem to me that a workflow could be triggering it, but I've asked my SFDC admin to look at that again. A workflow wouldn't work that quickly, right?