---
date: 2026-10-22
title: "Export score metadata and provenance to blob storage"
description: Two opt-in field groups add score metadata and the annotation, config, and evaluator behind each score to scheduled S3, GCS, and Azure exports.
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).

Score files in scheduled blob storage exports can now include each score's metadata and where it came from. Two new field groups add these columns on top of the core score columns:

- **Join scores to their origin in your warehouse.** `score_provenance` adds `author_user_id`, `config_id`, `queue_id`, `evaluator_id`, `evaluation_rule_id`, and `execution_trace_id`, so you can break down annotation scores by reviewer and queue, or LLM-as-a-judge scores by evaluator.
- **Debug a judge's verdict.** Follow `execution_trace_id` to the trace of the evaluator run that produced the score.
- **Analyze custom score attributes.** `score_metadata` adds the `metadata` column with the key-value pairs you attached when creating the score.

Enable the groups under **Project Settings → Integrations → Blob Storage**, or add `score_metadata` and `score_provenance` to `exportFieldGroups` on [`PUT /api/public/integrations/blob-storage`](https://api.reference.langfuse.com/#tag/blobstorageintegrations). Both groups are off by default, including on new integrations, so existing score files keep their current columns. Group columns are appended after the core columns and apply to future exports only.

## Learn more

- [Export field selection](/docs/api-and-data-platform/features/export-to-blob-storage#export-field-groups)
- [Score field reference](/docs/api-and-data-platform/features/export-to-blob-storage#scores)

<!-- 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-10-22-blob-storage-score-field-groups.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>.