> 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/synchronize-customer-attributes.md).

# Synchronize customer attributes

Configure a full Customer Attributes dataset update from DinMo to Monetate.

DinMo sends one complete CSV snapshot to an existing Monetate Customer Attributes dataset for each activation run. A successful DinMo upload means the file reached SFTP; check Monetate's dataset update history to confirm that Monetate processed it.

## Configure the activation

1. Create or choose a DinMo model or segment with one row per customer identifier.
2. Create an activation with the **Monetate** destination and select **Synchronize customer attributes**.
3. Enter the numeric **Dataset ID** from the dataset's **SFTP Info** in Monetate.
4. Enter the **Identifier column** exactly as it appears in the Monetate dataset, including capitalization.
5. Map the DinMo fields to the dataset's column names. Include the identifier column and use each output column name only once. The exported file includes a header row, so keep the names aligned with the Monetate dataset schema.
6. Schedule runs at least 10 minutes apart for the same dataset.

The activation uses a full snapshot: each successful file replaces the dataset's previous contents. Removed customers are therefore absent from the next successful snapshot. Partial updates and delta sync are not available for this destination.

## File requirements

DinMo writes a UTF-8 CSV with a header row to `/datasets/full`. The file name starts with the dataset ID, followed by a hyphen. Each file can contain up to 100 million rows, 30 columns, and 10 GB of uncompressed data. Identifier values must be present and unique in the exported rows. Monetate treats `NULL`, `None`, and empty values as missing. See [Monetate's upload requirements](https://docs.monetate.com/docs/customer-dataset-upload-requirements) for supported field formats, including dates and booleans.

Monetate advises sending no more than one file per dataset in a 10-minute period. Leave room for manual runs and retries when planning the schedule. If a run fails, inspect the DinMo sync error. If the upload succeeds but the dataset does not update, inspect the dataset's update history and error notifications in Monetate.


---

# 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/synchronize-customer-attributes.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.