> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/plugins-and-integrations/convai-unity-sdk/features/scene-metadata.md). # Scene metadata Find guides, component reference, and examples for Scene Metadata — the feature that gives Convai characters awareness of objects in your Unity scene. Scene Metadata gives Convai characters awareness of the objects in your Unity scene. Add a `ConvaiObjectMetadata` component to any GameObject to describe what it is — that static name, description, and include flag send automatically when a session connects, and re-sync live to every connected character if you edit them afterward, no scripting required. The same component can also expose optional tracked properties that report an object's live runtime state to characters while a session is active.


How scene metadata works Understand the registration and delivery flow, and when to use Scene Metadata vs. Dynamic Context.	How scene metadata works
Scene metadata quick start Register your first scene object and confirm it reaches Convai.	Scene metadata quick start
Scene metadata component reference Every Inspector field for `ConvaiObjectMetadata`, including tracked properties, and `ConvaiSceneMetadataCollector`.	Scene metadata component reference
Scene metadata scripting API `ConvaiObjectMetadata`, `ConvaiMetadataRegistry`, and `ConvaiSceneMetadataCollector` public methods.	Scene metadata scripting API
Scene metadata usage examples Complete setups for medical training, industrial safety, museum guides, runtime object exclusion, and tracked properties.	Scene metadata usage examples
Troubleshoot scene metadata Diagnosis for AI ignoring objects, validation errors, empty metadata payloads, and dependency failures.	Troubleshoot scene metadata

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.convai.com/api-docs/plugins-and-integrations/convai-unity-sdk/features/scene-metadata.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.