> For the complete documentation index, see [llms.txt](https://docs.dinmo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dinmo.io/integrations/destination-platforms/monetate.md).

# Monetate

Send complete customer attribute datasets to Monetate over SFTP with DinMo.

Connect Monetate to DinMo to update an existing Customer Attributes dataset from a model or segment. DinMo exports a CSV file over SFTP each time the activation runs. Monetate processes the file after it arrives.

## Before you connect

You need a Customer Attributes dataset in Monetate, its numeric dataset ID, and an SFTP user for the site. The dataset's identifier and attribute column names must be known before you configure the activation. DinMo updates the dataset; it does not create it.

## Connect Monetate

1. In DinMo, open **Destinations** and select **Add a new destination**.
2. Choose **Connect a new platform**, then **Monetate**.
3. Enter a connection name and the Monetate SFTP username. Use either the user's password or the private key matching the public key registered for that user in Monetate.
4. Keep the server `sftp.monetate.net` and port `22`, then save the connection.

To configure the dataset ID, field mapping, and schedule, follow [Synchronize customer attributes](/integrations/destination-platforms/monetate/synchronize-customer-attributes.md).

For SFTP user setup, including Monetate's public-key format, see [Manage SFTP Users](https://docs.monetate.com/docs/manage-sftp-users). For dataset IDs, see [Monetate's Customer Attributes SFTP guide](https://docs.monetate.com/docs/update-a-customer-attributes-dataset-via-sftp).


---

# 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://docs.dinmo.io/integrations/destination-platforms/monetate.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.