> 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/google-data-studio/metadata-extracted.md).

# Looker Studio Metadata Extracted

### What does Secoda extract from Looker Studio?

* Reports
  * Report Name
  * Report Description
  * Report Last Updated Time
  * Report URL
* Charts
  * Chart Name
  * Chart URL
* Tables
  * Table Name
* Lineage
  * Google Data Studio Dashboard <-> Looker Studio Chart
  * Google Data Studio Dashboard <-> Looker Studio Table
  * Google Data Studio Dashboard <-> Tables from other sources

{% hint style="info" %}
To determine lineage from Looker Studio, we use the relationships and dependencies provided from Looker Studio as well as our own Query parser to determine lineage to sources outside of Looker Studio.
{% endhint %}


---

# 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/google-data-studio/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.