> For the complete documentation index, see [llms.txt](https://docs.bugsplat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugsplat.com/education/how-tos/using-the-crash-attribute-feature.md).

# Using the Crash Attribute Feature

BugSplat supports user-defined metadata, also known as Custom Crash Attributes, in crash and error reports**.** These attributes are composed of name-value pairs that can be seamlessly integrated into your application's crash reporting setup. Each custom attribute can be displayed as a column on the crashes page, with all attributes accessible on the crash detail pages.

<figure><img src="/files/fcNid0ZgWjALJJZ3HfCp" alt=""><figcaption></figcaption></figure>

**Features:**

* **Display and Visibility:** Custom attributes can be viewed as columns on the crash report page, and are fully accessible on the crash detail pages.
* **Search, Group, Sort:** Custom attributes can be used in search, sorting, and grouping operations, just like other column values.

**Implementation:**

* Custom Crash Attributes are supported on all BugSplat crash platforms
* For **Windows** and **Xbox**, refer to the [BugSplat for Windows C++ documentation](/introduction/getting-started/integrations/desktop/cplusplus.md);
* For **PlayStation**, please refer to the documentation in the download found on the [Gaming Consoles](https://app.bugsplat.com/v2/database/integrations#consoles) tab on the Integrations page.
* For **Apple** platforms, refer to the [macOS](/introduction/getting-started/integrations/desktop/macos.md)/[iOS](/introduction/getting-started/integrations/mobile/ios.md#attributes) documentation.
* For **Linux**, **Crashpad**, **Qt**, **CMake**, and **Android,** BugSplat parses annotations as attributes. See the [Crashpad documentation](/introduction/getting-started/integrations/cross-platform/crashpad.md#initialization) for more info on how to add annotations.

For any issues or inquiries, please reach out to us at <support@bugsplat.com>. Our team is dedicated to helping you optimize your BugSplat integration and ensuring your application's crash reporting performs seamlessly.


---

# 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.bugsplat.com/education/how-tos/using-the-crash-attribute-feature.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.