> 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/fincome/synchronize-customers-data.md). # Synchronize customers' data ### Overview In this destination service, DinMo will export and update people’s attributes values in Fincome. To do so, you will need to go through these three steps: * [Creating a Fincome destination](/integrations/destination-platforms/fincome.md). Refer to the corresponding section for more info. * Creating a user segment composed of all the people and their attributes that will be synchronized with Fincome. 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 Fincome destination to start sending data. Refer to the [corresponding section](https://github.com/dinmo-io/docs.dinmo.io/blob/main/integrations/destination-platforms/fincome/synchronize-peoples-data.md#activation-configuration) for more info. Each time the activation runs: * *(Insert Only mode only)* All people previously unknown to Fincome will be created in Fincome with the associated attributes * *(Update Only mode only)* Existing people already available in Fincome will have their attributes updated * Existing attributes values that have changed since the last activation will be synchronized according to the selected sync mode ### 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 Fincome 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 Fincome. They define whether new records should be created, existing records updated, or both. For the Fincome destination, here are the available options: | Sync Mode | Description | Use Case | Behavior | | --------------- | ------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | | **INSERT ONLY** | Inserts new people into Fincome without updating existing records. | Initial imports or use cases where only new people should be added without modifying existing Fincome profiles. | New people are created in Fincome. Existing people already present in Fincome are ignored and remain unchanged. | | **UPDATE ONLY** | Updates existing people in Fincome without creating new records. | Keeping existing Fincome profiles synchronized while preventing the creation of additional people. | Existing people are updated with the latest attributes values. Unknown people are ignored and not created in Fincome. | **TLDR;** * **Insert only mode** creates new records but never updates existing ones. * **Update only mode** updates existing records but never creates new ones. * Neither mode deletes records from Fincome. {% hint style="info" %} **Note** No profile deletions are performed by the Fincome connector. People removed from the source segment will remain in Fincome unless deleted directly within Fincome. {% endhint %} #### **Fields mapping** In the Fields mapping section, you are asked to configure how the columns in your segment data should be mapped to fields in your destination. Some of the fields are marked as required by the destination platform to better map your data. At the moment, the only required field is customer\_id. #### **Create new custom attributes in Fincome** The selected fields will be exported as new attributes to the destination if they don't already exist. In all cases, DinMo will ensure they are kept up to date. #### Scheduling In this section, specify how often the attributes should be updated in Fincome. Every time the audience is refreshed: * **Insert only:** Any new user entering your DinMo segment since the last update will be added to Fincome * **Update only:** Existing users already present in Fincome will have their attributes updated * **All modes:** Attribute values already synchronized can be refreshed according to the selected synchronization behavior --- # 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, and the optional `goal` query parameter: ``` GET https://docs.dinmo.io/integrations/destination-platforms/fincome/synchronize-customers-data.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.