> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/getting-started/features/customer-engagement-platform/profiles/data-management.md).

# Data management

{% hint style="warning" %}
The Data management page shows the list of all the custom data collected on the Profile base that powers **Email, Push v2 & SMS**.
{% endhint %}

It includes all the custom data collected at least once on your apps and website, from the Batch SDKs or the Profile API. To manage this data, open the **Data** tab, then go to **Profile Data**.

### Enabling New Data

Attributes and events that were recently tracked but not yet enabled are displayed in a dedicated section. New custom data need to be manually enabled before being displayed in the targeting and personalization fields.

### Why is my custom data not available in the targeting?

If a custom attribute or event does not appear in the targeting or personalization fields of your orchestrations, check the following:

1. **The data has never been sent to the Profile base.** The Data management page only lists custom data that Batch has received at least once from the Batch SDKs or the Profile API. If a data has never been sent, Batch does not know it exists, so it cannot be displayed in the targeting. Ask your technical team to check that the data is sent through the SDK or the [Profile API](https://doc.batch.com/developer/api/cep/profiles/update).
2. **The data has been received but not enabled yet.** New custom data is not displayed in the targeting until it is enabled. Go to **Data** > **Profile Data**: recently tracked data that is not enabled yet is listed in a dedicated section. Enable it to make it available in the targeting and personalization fields.
3. **The data has been archived.** Archived data is hidden from targeting and personalization. You can restore it from the Data management page (see [Archive data](#archive-data)).

{% hint style="info" %}
Custom data is specific to your implementation: Batch does not create it natively. If a custom attribute is missing from the Data management page, it means it has never been sent to the Profile base. Check with your technical team, who manages the data your apps and website send to Batch.
{% endhint %}

### Editing Data

You can add a display name to any attributes or events. This is useful if you want to display simplified names in the interface instead of the technical name of the attributes/events. The technical name will still be displayed in the Profile view for debug purposes.

You can also change the data type of an attribute (e.g. from string to date) if you already made that change in the code of your app or in your call to the Profile API. Batch will adapt the operators displayed in the campaign editor to the new data type. If you changed the data type by mistake, Batch indicates with a \* the data type detected for that attribute (e.g. "Integer\*").

### Archive data

Archiving data makes it unavailable for targeting and personalization. It can be restored at any given time.


---

# 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://doc.batch.com/getting-started/features/customer-engagement-platform/profiles/data-management.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.