I am designing a proposal for a client who has already run pilots, and hinted that they have faced certain limitations with marketing cloud connector (native salesforce integrator).

With the exception of sms tracking information not been sent back to sales cloud, and possible API limitations on the use of Data Stream, I can't seem to think of anymore. I would like to put my best foot forward and welcome any input or pointers on this


You should be cautious with multi-org setup, since it has some limitations/shortcomings, which you can find listed here.

It is especially vital to note, that you cannot disable multi-org once it is enabled. I will personally go for the single-org integration, and if needed, pass data from parent BU using query activities.

| improve this answer | |
  • Thanks for this. Multi org is required as they will be connecting to multiple SF instances. I am more concerned with any limitations of the connector. – Samuel Dare Mar 16 '17 at 9:49

Another limitation is that the related list "individual email results" is not a lightning enabled object, so if you're using service console in lightning, you'll need to build a custom object that scrapes the IER related list.

Additionally, here's a link to an SMS history posting solution.

| improve this answer | |

Data streams work only at parent BU level but with multi-org this can be resolved

Also, Marketing Cloud Connect is only one way data flow (except for some tracking information)

| improve this answer | |
  • Thanks for this. Since we have a multi org set up in mind, are there any other considerations for MC connect? – Samuel Dare Mar 16 '17 at 9:51

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.