> 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/crisp/synchronize-peoples-data.md).

# Synchronize people’s data

### Overview

In this destination service, DinMo will export and update people’s attributes values in Crisp.

To do so, you will need to go through these three steps:

* [Creating a Crisp destination](/integrations/destination-platforms/crisp.md). Refer to the corresponding section for more info.
* Creating a user segment composed of all the people and their attributes that will be updated in Crisp. Refer to this [step-by-step tutorial to learn how to build segments without SQL](/guides/get-started-with-dinmo/create-and-activate-segments-on-dinmo.md) in DinMo.
* Activating the segment to the Crisp destination to start sending data. Refer to the [corresponding section](#activation-configuration) for more info.

Each time the activation will be running:

* *(Upsert or Mirror mode only)* All people previously unknown to Crisp will be created in Crisp, with the associated attributes
* All attributes values that have changed since the last activation will be updated in Crisp

### Activation configuration

Once the destination has been set up, and your DinMo segment or model created, you can create an activation to start sending data to Crisp right away.

{% hint style="info" %}
Learn how to activate a segment in our [step-by-step tutorial](/guides/get-started-with-dinmo/create-and-activate-segments-on-dinmo.md)
{% endhint %}

#### **Sync Modes**

When configuring your sync, you will be asked to choose the **Sync Mode**.

Sync modes determine how data is synchronized between your data source and Crisp. They control whether to insert new records, update existing ones, or keep the destination aligned with the source.

For the Crisp destination, here are the available options:

| Sync Mode       | Description                                                 | Use Case                                                                                                            | Behavior                                                                                                                                                        |
| --------------- | ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **UPSERT**      | Inserts new people and updates existing people in Crisp.    | Initial data loads. Standard synchronization when new people can be created in Crisp.                               | New people are created in Crisp. Existing people are updated with the latest attributes values. No deletions are handled.                                       |
| **UPDATE ONLY** | Updates existing people in Crisp without creating new ones. | Keeping Crisp data up to date only for people already known in Crisp. Avoiding the creation of new people in Crisp. | Existing people are updated with the latest attributes values. Unknown people are ignored and not created in Crisp. No deletions are handled.                   |
| **MIRROR**      | Keeps Crisp aligned with the source dataset.                | Maintaining an exact replica of the source. Use cases requiring strict consistency between DinMo and Crisp.         | New people are created. Existing people are updated. People missing from the source are removed or no longer synchronized, depending on the connector behavior. |

**TLDR;**

* **Upsert mode** never deletes records from the destination, even if they are removed from the source.
* **Update only mode** never creates new records in the destination.
* **Mirror mode** ensures full alignment between the source and the destination.\
  ⚠️ This irreversibly deletes the profile from Crisp.

{% hint style="danger" %}
**Warning — Use Mirror Mode with Caution**

**Mirror sync mode permanently deletes records from the destination when they are no longer present in the source.** This includes contacts and related data.

Once deleted, these records **cannot be recovered** unless they are reintroduced from the source in a future sync.

Mirror mode should therefore be used **only when the source is the single source of truth** and when permanent deletions are an intended and fully controlled behavior. Always validate deletion rules and run Mirror syncs carefully, especially on production environments.
{% endhint %}

#### **Fields mapping**

In the Fields mapping section, you are asked to specify the field contained in your DinMo segment that Crisp will use to link each segment’s records to a Crisp person.

Depending on your Crisp configuration, it may be the email address of the person, or another external identifier.

You can also map the standard fields required to identify and update people in Crisp.

#### **Synchronized attributes**

In this section, any field you select will be exported as a people attribute in Crisp.

If the attribute does not already exist in Crisp, DinMo will create it. The associated field will have the same name in Crisp and DinMo.

These values of the attributes selected here will then be updated at each activation.

#### Scheduling <a href="#scheduling" id="scheduling"></a>

In this section, specify how often the attributes should be updated in Crisp. Every time the audience is updated:

* **Mirror and upsert:** Any new user having entered your DinMo segment since the last update will be added to your Crisp website
* **All modes**: For all existing profiles, the attributes will be updated
* **Mirror:** Any user having left your DinMo segment since the last update will be deleted from your Crisp account


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dinmo.io/integrations/destination-platforms/crisp/synchronize-peoples-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.