> For the complete documentation index, see [llms.txt](https://developers.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.didomi.io/cmp/web-sdk/third-parties/direct-integrations/salesforce-dmp-krux.md).

# Salesforce DMP (Krux)

The Didomi CMP can automatically share the consent status of the user with the Salesforce DMP (Krux) tag. When the integration is enabled, the SDK will call `Krux('consent:set', { ...consent information })` as needed.

See the following articles from the Salesforce DMP documentation for more information on what the SDK does:

* <https://konsole.zendesk.com/hc/en-us/articles/360000754674-JavaScript-Consent-Tag-Spec>
* <https://konsole.zendesk.com/hc/en-us/articles/360000486853>
* <https://konsole.zendesk.com/hc/en-us/articles/360001614194-DMP-Implementation-Best-Practices-for-GDPR>

To enable the integration, you must add the `salesforce` vendor to your tag configuration and also add a dedicated section for the integration:

```javascript
window.didomiConfig = {
    app: {
      vendors: {
        didomi: [
          'salesforce',
        ],
      }
    },

    integrations: {
      vendors: {
        'salesforce-dmp': {
          enable: true,
          namespace: 'namespace', // Optional ; set to null if you do not use a namespace
        },
      },
    },
};
```

The `namespace` property is optional and allows you to specify what namespace you are using in the Salesforce DMP.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.didomi.io/cmp/web-sdk/third-parties/direct-integrations/salesforce-dmp-krux.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.