To my mind, the main problem with using a personal SFDC account as the sync user is if you ever want to restrict your sync in any way.
As Edward mentioned, restricting field visibility is one example. Maybe you have a field that makes no difference to Marketo but changes often, perhaps via a workflow rule. This will constantly be triggering a sync, increasing API calls. This won't make much difference in the beginning, but it can as you scale.
Another issue -- what if you want to prevent some records from synching over to Marketo entirely, example, leads or contacts with no email address? Typically this is done via restricting sharing rules on the sync user. But if that user is your admin user that you use for other purposes, then you have a problem.
Lastly, there is the password issue. Salesforce will occassionally expire your password and then break your sync unless you update the credentials in Marketo quickly.
If you have a dedicated sync user you could potentially set them as an API-only user and tell Salesforce not to expire the password (some businesses may be comfortable with that, others not, but at least it's an option). You may not want to do that with a personal account though.
All that being said, when I worked at a small company we used my personal account for a while as the sync user and it was fine. But eventually it did make sense to have a dedicated account for the reasons above.
Justin Norris |
Perkuto
.png)