Thank you for asking this! 1. Salesforce integration is the section I dislike the most. You can edit some basic sync options, and see a timestamp of the last sync and whether or not it's in progress, but it gives very little other visibility, and that makes admin'ing the integration difficult. Would be great if some of the information (object schemas, field visibility and field types, sync logs) were available to admin users through non-secret and supported methods. It would be great to see a log of the sync cycle - how many records of a given object synced to and from Salesforce, how many were new, updated, a count of the how many records are pending sync for each object. An error log too please! FYI - I used to work in Marketo Support and I know that all of this information is already available to them, and simply needs some work to make it presentable and supportable for users. In my opinion, it would also deflect a lot of their cases related to the Salesforce integration. It would also be fantastic to have a "Field Mapping" tab where we can change the field mapping between Marketo and Salesforce on our own without having to go through Support. Additionally, it would be great if fields did not automatically sync down to Marketo simply because the sync user can see them - if the fields simply became available for sync in this hypothetical "Field Mapping" tab, it would help us tremendously with keeping our fields clean, giving us control rather than being at the mercy of our SFDC admins remembering to follow processes around permissions. 2. Field Management is the most used. For an agile team, there is constant change coming downstream from Salesforce. We have to adapt quickly to process changes in CRM by making sure new fields are synced properly and finding where old fields are in use to make sure there are no dependent processes. It would be really nice if we could (1) delete old fields rather than hiding them, (2) relabel fields even though they are in use. Our instance is 10 years old, and we have an enormous list of hidden fields. Also, when removing a field from assets, we find the field in Field Management and look at the Used By list - but the assets there aren't clickable links, which makes it even more painful trying to remove references to the field. 3. I think I covered this in #1 and #2 4. I'm not sure how I would apply an export feature of admin configurations. If other people have use cases for that I'd be curious.
... View more