It's been a very long time since the last improvement to the Salesforce connector. Browsing the community product and Idea sections enables to see how much some improvement is needed. So I wrote this recap on all the ideas that would really make a difference and enable the Marketo / SFDC connector to widen the gap again with the competition, which has been catching up over the past 2 years.
The first item would be an increase in performance, as we just got for MS Dynamics in the Spring'16 release (Release Notes: Spring '16 - Marketo Docs - Product Docs). And this is especially true for the campaign member table that can be really huge!
This long list is also there for the reader to vote for them!
The first areas on which some improvement is the data schema management and mapping:
We also need some strengthening of the way custom objects are mapped and handled:
The way the user object is handled needs a serious enhancement:
On the chapter of how Marketo programs interact and sync with SFDC campaigns, a lot has to be done:
A few enhancements would be welcome in the way we can leverage SFDC campaigns in filters and triggers:
Task / activity creation needs a serious improvement:
Lead assignment mechanism is by far too limited to enable to manage all the complexities of the most flexible or largest organizations. In these advanced SFDC users, at minimum, some lead assignment rules have been set up but very often some complex logic has been created, for instance to attach leads to accounts before they are converted. So:
Last but not least, we really need some improvement in how we can manage the sync and troubleshoot any issue:
I'll probably also compile a list of improvement that we would need to see coming on Marketo Sales Insight...
Also note that the version of the API which Marketo uses is only v20 - Salesforce is now on v37!!!
Yes, you are right, and surely implementing some of these ideas will require an upgrade of the API version.
I just ran into this within the past 24 hours (I was working off SFDC's SOAP API documentation to try to map something only to realize "oh I guess Marketo doesn't support that field yet") and it's yet another "I'd make an idea but no one would understand", so: cosigning updating the API version.
Upgrading the API version is not a goal by itself, but most of the ideas in this post would require an upgrade of the SFDC API version used by the Marketo connector.
Just wanted to add an update to this particular comment - the Marketo Salesforce connector now supports v37 of the Salesforce API. We are also regularly keeping an eye on new developments in the Salesforce API, and will upgrade to later versions as necessary.
Thanks for letting us know this has been updated! While I'm genuinely excited to hear this, I do have one minor complaint--which is that if I wasn't involved with this thread, I wouldn't've known this even happened. While I realize this would make most of Marketo's user base's eyes glaze over, can we please please please get release notes when technical changes like this happen? It definitely matters to a subset of us. Heck, even just having a changelog in the developers' section would be nice.