> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.crisp.chat/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Getting started with Custom Datas

*Learn what custom data is in Crisp and how it helps your team personalize support, routing, and campaigns.*

Most businesses already store useful customer context in their own tools: plan, account ID, order history, lifecycle stage, language, revenue, or internal links. Custom data lets you bring that context into Crisp so your team can act with more precision.

---

# ${color}[#0080dd](What custom data is)

Custom data is key/value information that you send to Crisp from your website, backend, imports, integrations, or automation tools.

Crisp uses two main levels of custom data: **conversation/session data** and **contact data**.

#### ${color}[#445055](Conversation or session data)

Conversation data is stored at the conversation level. It is useful when the information only applies to the current exchange, such as the page the visitor is on, a submitted form value, or a temporary workflow state.

#### ${color}[#445055](Contact data)

Contact data is stored on the contact profile. It is useful for information that should remain attached to the person over time, such as `user_id`, `plan`, `company_size`, or `lifetime_value`.

Conversation data can also appear in the visitor data area of a conversation, while contact data stays attached to the profile across conversations.

![Custom data displayed on a Crisp contact profile](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/cleanshot-2025-03-03-at-124729_1qt1keo.png =1000xauto)

||| Conversation/session data and contact data are not the same thing. Use conversation data for the current exchange, and contact data for stable profile context.

---

# ${color}[#0080dd](Why custom data is useful)

#### ${color}[#445055](Give support teams better context)

Custom data helps agents understand who they are talking to without asking repetitive questions.

For example, you can display values such as `average_basket_value`, `transaction_count`, `plan_price`, or `average_csat` directly in the conversation context. This makes it easier to personalize replies, prioritize requests, and route conversations correctly.

![Custom data displayed in a Crisp conversation](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/cleanshot-2025-03-03-at-124943_5hxlhs.png =1000xauto)

#### ${color}[#445055](Personalize shortcut replies)

You can use custom data inside [shortcut replies](/en/article/how-can-i-use-shortcut-replies-canned-messages-1bmff5q/) to personalize repetitive answers at scale.

For example, a shortcut can include a customer's plan, account name, or internal profile link, depending on the variables your team stores in Crisp.

#### ${color}[#445055](Build better campaign targeting)

Custom data can also improve [automated and one-shot campaigns](/en/article/how-do-i-use-automated-campaigns-1ht44u5/). You can combine native attributes, such as country or language, with your own data, such as `price_plan` or `trial_status`, to send more relevant messages.

![Custom data used for campaign targeting in Crisp](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/cleanshot-2025-03-03-at-162857_1pdkrmn.png =1000xauto)

---

# ${color}[#0080dd](Where to go next)

To bring custom data into Crisp, start with [How can I automatically set custom data?](/en/article/how-can-i-automatically-set-custom-data-1xh7pqk/) or [How to import my user data?](/en/article/how-to-import-my-user-data-dcukz8/). If you only need simple labels, use [segments](/en/article/what-is-a-segment-and-how-can-it-help-your-team-88hhzw/) instead.