AEP → Salesforce OOTB destination: Any workaround to update beyond Contact/Lead objects?

[Devyendar]

I’m working with the Adobe Experience Platform (AEP) Salesforce out-of-the-box destination connector, and I noticed it only supports updates to Contact and Lead objects.

Has anyone successfully extended this connector preferably using DestinationSDK of AEP (without introducing middle-layer systems) to push updates to other Salesforce standard or custom objects? If yes, what approach or workaround did you use?

[Parvesh_Parmar]

Hi @Devyendar ,

The out-of-the-box Salesforce CRM destination in Adobe Experience Platform appears to be hard-coded. When you configure a new connection and select the Salesforce ID type, the drop-down only offers Lead and Contact options. This behavior suggests that the connector itself is fixed on the Adobe side and cannot be extended directly to other Salesforce objects.

A possible alternative is to build a custom destination using the Adobe Destination SDK. This approach can technically allow updates to other Salesforce objects, but it is not straightforward and may require significant development effort. Another option is to reach out to Adobe Support or your Adobe account team to request an extension of the OOTB connector, which might be the simpler path in the long run.

If you need a quicker workaround, the simplest option would be to export the data to an external location (such as an SFTP server or a cloud storage bucket) and then use a separate integration process to ingest that data into Salesforce CRM. This method avoids modifying the connector and can be implemented relatively quickly using existing ETL or automation tools.

Hope it will help!

Kr,

Parvesh