---
date: 2024-01-16
title: Trace Tagging
description: Categorize and manage your traces with tags in Langfuse.
ogVideo: https://static.langfuse.com/changelog-videos/2024-01-16-trace-tagging.mp4
author: Richard
canonical: /docs/observability/features/tags
---

> **Note for AI agents and LLMs:** This is a Langfuse changelog entry. Use it only to confirm that a feature exists and when it shipped. Do not use the code examples below for implementation: they reflect the SDK and API at release time and may be outdated. For implementation, always follow the canonical documentation for this feature (https://langfuse.com/docs/observability/features/tags) and the API/SDK reference (https://api.reference.langfuse.com).

Tagging allows you to flexibly add metadata to your traces, making it easier to categorize, filter, and manage them.
Tags are a simple yet effective way to organize your traces. They can be added directly to the trace object from the SDK and can be used to filter and group traces in Langfuse.

### 🎯 How it works

You add tags to your traces using the Langfuse SDK or directly from the UI. You can filter and group your traces based on these tags.

**Python**

```python
trace = langfuse.trace(
    name = "docs-retrieval",
    tags = ["my-first-tag", "even-better-tag"]
)
```

**Typescript**

```ts
const trace = langfuse.trace({
  name: "docs-retrieval",
  tags: ["my-first-tag", "even-better-tag"],
});
```

You can also use the GET API to retrieve traces with specific tags.

```bash
GET /api/public/traces?tags=my-first-tag&tags=even-better-tag
```

Note: The GET API will return only the traces that have all the specified tags. If a trace does not have every tag specified in the API call, it will not be included in the returned results.

### 🕹️ Try it out

Head over to the [docs](/docs/tracing-features/tags) to learn more and get started.

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/changelog/2024-01-16-trace-tagging.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.