> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/connectors/fr/pos/cegid/donnees-client-et-fidelite.md).

# Données client et fidélité

Mappez les données client, les cartes de fidélité, les vouchers, les reçus et la valeur stockée de Cegid Retail Y2 aux parcours Wallet.

Les données client et les parcours de fidélité connectent les enregistrements Cegid Retail Y2 avec les pass Wallet. Ces pages couvrent le mappage des champs, les cartes de fidélité, les documents de vente, les reçus, les bons et la valeur stockée.

{% content-ref url="/pages/337bef3442d041947b0ca274173d4a50fc6a760d" %}
[Mappage des champs Cegid Retail Y2](/connectors/fr/pos/cegid/donnees-client-et-fidelite/cegid-retail-y2-fields-mapping.md)
{% endcontent-ref %}

{% content-ref url="/pages/1d7dbb3011547f7dfd29ac90f7093c1f1e363c98" %}
[Personnaliser le mapping](/connectors/fr/pos/cegid/donnees-client-et-fidelite/customise-the-mapping.md)
{% endcontent-ref %}

{% content-ref url="/pages/84989e7f133e3d4d63d2c178eba504ccfd911847" %}
[Cartes de fidélité et programmes](/connectors/fr/pos/cegid/donnees-client-et-fidelite/loyalty-cards-and-programmes.md)
{% endcontent-ref %}

{% content-ref url="/pages/21fd4670c84f5496698735ef5121fe9729431fff" %}
[Reçus, vouchers et documents de vente](/connectors/fr/pos/cegid/donnees-client-et-fidelite/receipts-vouchers-and-sales-documents.md)
{% endcontent-ref %}


---

# 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.thewalletcrew.io/connectors/fr/pos/cegid/donnees-client-et-fidelite.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.