Neil_Robertson6

Correct - especially on iPhone where it marks as an open no matter what.

I think we also need to be wary of noting "bugs" (there are some 😉 in Marketo when things like IP are not bugs - they are, in most cases, facts of life. If you are on a shared IP range (you are on more than one f you are) you will hit a spam trap pretty much at least once every day and more than l...

Have you signed up/attended the London User Group yet?

Also note that docs.marketo.com is entirely open and free to read/consume.

Yep, this is an out of the box feature for Marketo (as long as the record is known to Marketo)

Also note that the version of the API which Marketo uses is only v20 - Salesforce is now on v37!!!

As others have noted, it is certainly possible (but no advised) to connect 1 Marketo instance to multiple SFDC instances but it does become tricky if you are not sending information to an ESB or API endpoint via Webhooks etc so you know where to route decisions etc.

We also see this with Custom Object where there is a lot of R/W going on. If the numbers will never match then great please tell us 😉 if the over count is down to delta processing then tell us - but perhaps split the logic up as Marketo Rows being higher than Salesforce Rows doesn't make sense?!

From a Salesforce perspective yes - there is no issue re: compatibility but the fact Marketo is using an older version is detrimental to the fact Salesforce is increasing their feature sets etc. A quick API check of v20 and v36 show a few fields (on account in this case) which are now visible in th...

Not really sure I understand the reply TBH my point is that Marketo accessing (using) a version of the API 16 versions behind the latest Salesforce API (version 36) therefore Marketo is not supporting a lof of new fields (and features) which are present in the latest. There are fields which are p...