Salesforce DMP Destination

Segment makes it easy to send your data to Salesforce DMP (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to Salesforce DMP in the format they understand. Learn more about how to use Salesforce DMP with Segment.


Supported Sources and Connection Modes

WebMobileServer
📱 Device-based
☁️ Cloud-based

To learn more about about Connection Modes and what dictates which we support, see here.

Settings

Segment lets you change these destination settings via your Segment dashboard without having to touch any code.

Salesforce DMP Config Id

Enter your Config ID here. You can find this by going to the Salesforce DMP Console > Manage Tab > Sites > Config Column. It should be a string of letters and numbers, like ra789sxab.

Track Call - Event Attribute Mapping

If you are using Salesforce DMP on server-side or mobile, then you can enter Segment Track event properties to map to custom attributes to be sent to Salesforce DMP. For example, if you wanted to send a track call like analytics.track('Video Watched', { videoLength: 120 }) and send that value to Salesforce DMP under the property video_length - then put videoLength on the left column and video_length on the right. If the property exists when the call is made, we will send it along with the call. Note that this is case-sensitive, and you need to generate the property first on the event definition in Salesforce DMP.

If you are using Salesforce DMP on web, the instructions are the same. However, we will instead inject these properties onto window.kruxDataLayer on whitelisted Track events.

Track Call - Event ID Mapping

If you are using Salesforce DMP on server-side or mobile, then you can enter Segment Track event names to map to event IDs in Salesforce DMP. For example, if you wanted to send a track call like analytics.track('Order Completed') and send that to Salesforce DMP under the event ID lK4Tsh7 - then put Order Completed on the left column and lK4Tsh7 on the right. If the property exists when the call is made, we will send it along with the call. Note that this is case-sensitive.

Page/Screen Call Domain

If you are using Salesforce DMP on server-side or mobile, then enter your Salesforce DMP Domain here. If you have your pixel URL from your representative, then it is the parameter that _kpc_d is set to. For example, if your url contains _kcp_d=example_kcpd, then input example_kcpd. If you don’t have this value, contact your Salesforce DMP representative.

Page/Screen Call Site

If you are using Salesforce DMP on server-side or mobile, then enter your Salesforce DMP Site here. If you have your pixel URL from your representative, then it is the parameter that _kcp_s is set to. For example, if your url contains _kcp_s=example_kcps, then input example_kcps. If you don’t have this value, contact your Salesforce DMP representative.

Page/Screen Call Section

If you are using Salesforce DMP on server-side or mobile, then enter your Salesforce DMP Section here. If you have your pixel URL from your representative, then it is the parameter that _kcp_sc is set to. For example, if your url contains _kcp_sc=example_kcpsc, then input example_kcpsc. If you don’t have this value, contact your Salesforce DMP representative.

Page/Screen Call - Page Attribute Data

If you are using Salesforce DMP on server-side or mobile, then you can enter Segment properties to map to custom page attributes to be sent to Salesforce DMP. For example, if you wanted to send a page call like analytics.page('my_site', { customProperty: 7 }) and send that to Salesforce DMP under the property custom - then put customProperty on the left column and custom on the right. If the property exists when the call is made, we will send it along with the call.

Publisher UUID

If you are using Salesforce DMP on server-side or mobile, then enter your Salesforce DMP Publisher UUID here. If you have your pixel URL from your representative, then it is the parameter that _kpid is set to. For example, if your url contains _kpid=example_kpid_a5b4, then input example_kpid_a5b4. If you don’t have this value, contact your Salesforce DMP representative.

Page/Screen Call - User Attribute Data

If you are using Salesforce DMP on server-side or mobile, then you can enter Segment properties to map to custom user attributes to be sent to Salesforce DMP. For example, if you wanted to send a page call like analytics.page('my_site', { customUserProperty: 7 }) and send that to Salesforce DMP under the property userCustom - then put customUserProperty on the left column and userCustom on the right. If the property exists when the call is made, we will send it along with the call.

Namespace

Client-side Track Calls: This is your namespace for your Salesforce DMP instance. It should look something like ns:namespace. Make sure that this namespace matches the namespace bound to your Config ID, or additional pixel.gif calls will not fire!

AJS Track Event Whitelist

Client-side Track Calls: Add in the names of track events that you would like to re-fire pixel.gif on Salesforce DMP. Only events on this list will fire, and this list is case-insensitive.


If you have any questions or see anywhere we can improve our documentation, please let us know or kick off a conversation in the Segment Community!