> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/integrations/data-visualization-tools/amplitude-integration/metadata-extracted.md).

# Amplitude Metadata Extracted

If your data stack includes Amplitude, then you may want to consider integrating Secoda with your Amplitude instance. We've created a space for your event-based data to be represented within the Catalog.

You can create Event resources in Secoda for each event that you track and add metadata like descriptions, related resources, owners, etc. Check out Amplitude's documentation on managing event types and properties: <https://help.amplitude.com/hc/en-us/articles/360047138392-Manage-events-and-properties>

### What does Secoda extract from Amplitude?

* Events
  * Event Name
  * Event Type
  * Event Category
  * Event Description
  * Event Properties


---

# 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.secoda.co/integrations/data-visualization-tools/amplitude-integration/metadata-extracted.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.