> 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/piano-analytics/synchronize-catalogs.md).

# Synchronize Catalogs

## Overview

Integrating your product catalog into Piano Analytics enables you to transform raw traffic data into actionable business intelligence by linking user behavior directly to product attributes, sales performance, and granular e-commerce KPIs... That's why DinMo allows you to keep it up to date!

In this destination service, DinMo will keep your catalog up to date.

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

* Creating a Piano Analytics destination. Refer to the [corresponding page](/integrations/destination-platforms/piano-analytics.md) for more info.
* Creating a custom segment/model composed of all the products that you will be kept up to date in your Piano Analytics.
* Activating the segment/model to the Piano Analytics destination

## Destination setup

{% hint style="info" %}
Learn how to create such a destination in our [step-by-step tutorial](/guides/get-started-with-dinmo/initial-configuration-of-dinmo/create-a-destination.md)
{% endhint %}

To start updating your catalog, you are first required to create a Piano Analytics destination with the corresponding destination service.

Refer to the [corresponding page](/integrations/destination-platforms/piano-analytics.md) for more info.

## Activation configuration

Once the destination has been setup, and your DinMo segment created, you can create an activation to start sending product data to Piano Analytics right away.

The only sync mode possible for this destination is **upsert**, which means that DinMo will:

* Insert new products
* Update products for which at least one attribute has changed

### Activation core parameters

In this section, specify:

* The **ID of the catalog** you want to enrich in Piano Analytics
* The name of the **reconciliation key** in your Piano Analytics Catalog<br>

### Fields mapping

In this section, configure how the columns in your segment data should be mapped to fields in your destination. The Reconciliation Key is marked as required by the destination platform to better map your data.

You can then fill in as many fields as you want in the associated properties.

{% hint style="warning" %}
Please note that the name of the custom attribute must match the name of the column in Piano Analytics. Similarly, be careful to send the correct data type for each column (string, boolean, etc.).
{% endhint %}


---

# 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/piano-analytics/synchronize-catalogs.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.