---
date: 2026-05-20
title: "Blob storage, PostHog, and Mixpanel exports default to enriched observations for new Cloud projects"
description: New Langfuse Cloud projects use enriched observations for blob storage, PostHog, and Mixpanel exports. The legacy traces/observations sources stay available on existing projects and self-hosted deployments.
author: Niklas
---

> **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 current documentation (https://langfuse.com/docs) and the API/SDK reference (https://api.reference.langfuse.com).

Blob storage, PostHog, and Mixpanel integrations on Cloud projects created on or after **2026-05-20** use the **Enriched observations (recommended)** source. The **Traces and observations (legacy)** and **Traces and observations (legacy) and enriched observations** sources are hidden from the UI for these projects. For blob storage, the REST API also rejects legacy values for post-cutoff projects with `400 BAD_REQUEST`.

Nothing changes for **existing Cloud projects** or **self-hosted deployments**: all three sources remain available and the legacy sources are fully supported. Existing Cloud projects can switch to Enriched observations at any time.

Enriched observations are part of the [Langfuse v4 data model](/docs/v4), which introduced a single denormalized observation row as the canonical export shape across all integrations.

If a downstream consumer expects the legacy `traces/` and `observations/` file shapes, see the [Export Field Reference](/docs/api-and-data-platform/features/blob-storage-export-fields) for the column map between the two layouts.

<!-- 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/2026-05-20-blob-storage-enriched-default.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>.