> For the complete documentation index, see [llms.txt](https://docs.decube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decube.io/org-settings/custom-attributes/deprecation-guide-tags-to-column-tags.md).

# Deprecation Guide: Tags → Column Tags

{% hint style="info" %}
**Migration complete.** Tags were deprecated on **15 June 2026**. All existing tag data has been automatically migrated to Column Tags — your data is preserved. If you use the Decube API to read or write tags, update your integrations now to avoid disruption.
{% endhint %}

Tags have been migrated to **Column Tags**, a new custom attribute that covers the same use case with fewer constraints and more control. This guide explains what changed and what you may still need to do.

***

## What is changing and why

Tags have served as a lightweight way to label columns in the catalog. As usage has grown, the limitations of the original implementation have become clear: there is no central management interface, the number of tags per asset is arbitrarily capped, and tags are excluded from Decube's custom filter rules.

Column Tags is built on the [Creating & managing custom attributes](/org-settings/custom-attributes.md) framework and resolves all three of these constraints:

|                       | Tags (deprecated)         | Column Tags                                     |
| --------------------- | ------------------------- | ----------------------------------------------- |
| Management interface  | None                      | Managed in **Org Settings → Custom Attributes** |
| Field limits          | Maximum 3 tags per column | No limit                                        |
| Custom filter support | Not supported             | Full support, including complex filter rules    |

Your existing tag data is fully preserved — it migrates automatically to Column Tags on the deprecation date.

***

## Key dates

| Date                   | Event                                                             |
| ---------------------- | ----------------------------------------------------------------- |
| First week of May 2026 | Deprecation notice published (this guide)                         |
| Early June 2026        | Final reminder issued                                             |
| 15 June 2026           | ✅ Tags deprecated; all data automatically migrated to Column Tags |

***

## What you need to do

### General users

Nothing further. Decube automatically migrated all existing tag values to Column Tags on 15 June 2026. Your data is preserved exactly as-is.

You can find your tags under **Custom Attributes** on any column asset page. See [Finding Column Tags after migration](#finding-column-tags-after-migration) below.

### API users

If your integrations read or write tags via the Decube API and you have not yet updated them, do so now. The `tags` field has been removed from five endpoints.

***

## API impact

The table below lists every endpoint where `tags` appears as a request or response field.

| Endpoint                               | Method | Location | Field type |
| -------------------------------------- | ------ | -------- | ---------- |
| `/data_quality_scores/report/generate` | POST   | Payload  | `string[]` |
| `/data_quality_scores/report/result`   | GET    | Response | `string`   |
| `/assets`                              | GET    | Response | `string[]` |
| `/assets`                              | PATCH  | Payload  | `string[]` |
| `/assets/search`                       | POST   | Payload  | `string[]` |

{% hint style="warning" %}
The `tags` field has been removed from all affected endpoints as of 15 June 2026. Integrations that still reference it will receive empty or missing values. Update your integrations now to restore expected behaviour.
{% endhint %}

### POST /assets/search — update filter payloads

If you filter assets by tags in a `POST /assets/search` request, update your payload to reference the Column Tags custom attribute instead of the `tags` field.

### GET /assets — tag values moved to custom attributes

Tag values are no longer returned in the `tags` field of an asset response. They now appear under `custom_attributes`, keyed to the Column Tags attribute.

### PATCH /assets — update tag write payloads

If you write tags to a `property` asset via `PATCH /assets`, update your payload to use the Column Tags custom attribute field instead of `tags`. This endpoint overwrites all existing tag values, so review any automation that relies on this behaviour.

### POST /data\_quality\_scores/report/generate — update scorecard filter payloads

If you filter monitors by tag name in a `POST /data_quality_scores/report/generate` request, update the filter to reference Column Tags values instead of the `tags` field.

### GET /data\_quality\_scores/report/result — tag values moved to custom attributes

Tag values are no longer returned in the `tags` field of the scorecard result response. They now appear under `custom_attributes`, keyed to the Column Tags attribute.

***

## Finding Column Tags after migration

After the migration, all column tag values appear in the **Custom Attributes** section of any column asset page in the catalog.

To manage the Column Tags attribute definition — rename values, adjust descriptions, or review all tagged assets — go to **Org Settings → Custom Attributes**.

{% content-ref url="/pages/GlFSneGL1vEEvo1TcLLf" %}
[Creating & managing custom attributes](/org-settings/custom-attributes.md)
{% endcontent-ref %}

***

## Frequently asked questions

#### Will any of my tag data be lost during migration?

No. Every existing tag value is carried over to Column Tags automatically. The migration preserves all tag data exactly as it exists on the deprecation date.

#### Do I need to do anything in the UI before the deprecation date?

No action is required for general catalog users. Your tag data migrates automatically. You will find it under Custom Attributes after the migration date.

#### When was the `tags` field removed from the API?

The `tags` field was removed from all affected endpoints on **15 June 2026** — including `POST /assets/search`, `GET /assets`, `PATCH /assets`, `POST /data_quality_scores/report/generate`, and `GET /data_quality_scores/report/result`. If your integrations still reference this field, update them now.

#### Were tags applied close to the deprecation date included in the migration?

Yes. All tags applied before the cutover on 15 June 2026 were included in the automatic migration.

***

## Get help

If you have questions about this migration or need assistance updating your API integrations, contact <support@decube.io>.


---

# 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.decube.io/org-settings/custom-attributes/deprecation-guide-tags-to-column-tags.md?ask=<question>&goal=<endgoal>
```

`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.