> 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.md).
# Looker Studio
An overview of the Looker Studio integration with Secoda
{% content-ref url="/pages/lIsAe8QD7zAicWLBNxZ6" %}
[Looker Studio Metadata Extracted](/integrations/data-visualization-tools/google-data-studio/metadata-extracted.md)
{% endcontent-ref %}
Secoda has two methods of integrating with Looker Studio: retrieving a session cookie and using Google OAuth
**NOTE:** *Using the Google OAuth method does not extract upstream (datasources) and downstream (charts) lineage due to the limitations of the Looker Studio API*
**NOTE:** *The session cookies expire after 12 hours and you need to re-retrieve the cookie each time you wish to run the extraction.*
## Getting Started with Google OAuth
There are two steps to get started using Looker Studio with Secoda through Google OAuth:
1. Authorize Secoda for your Organization
2. Connect Looker Studio to Secoda
### Authorize Secoda on Google Admin
1. Sign in to your Google Admin console and navigate to [domain wide delegation](https://admin.google.com/ac/owl/domainwidedelegation).
2. In `API clients`, click **Add new**.
3. Enter the Client ID: `884425733446-7lao52vmjg9k7hovpgba2qd5b7qeo8l2.apps.googleusercontent.com`
4. Enter the following OAuth scopes:
* `https://www.googleapis.com/auth/datastudio`
* `https://www.googleapis.com/auth/userinfo.profile`
5. Click **Authorize**.
### Connect to Looker Studio
1. In Secoda, head to the **Integrations** page and click **New integration**
2. Select **Looker** **Studio** and click on the **OAuth** tab
3. Click the `Connect with OAuth` button and login using your Google account
4. Head to the **History** tab on the side bar and click **Run extraction**
## Getting Started with Session Cookies
There are two steps to get started using Looker Studio with Secoda through session cookies:
1. Retrieve a Looker Studio session cookie
2. Connect Looker Studio to Secoda
### Retrieve Session Cookie
*Secoda uses a series of REST APIs that Looker Studio uses for its platform, which requires a session cookie. To get a session cookie follow these steps:*
1. Login to [Looker Studio](https://datastudio.google.com) and open the developer tools by *right-clicking* and selecting **Inspect**
2\. Click on the **Network** tab and put `https://lookerstudio.google.com` in the **filter** field
3\. Refresh the page and you should see some requests populate
4\. Click on the `getShareableList` network request and then navigate to the **Headers** tab
5\. In the **Headers** tab, scroll down to the **Request Headers** section and copy the `cookie` header.
### Connect to Looker Studio
*After retrieving the session cookie, you can connect Looker Studio to Secoda by following these steps:*
1. In Secoda, head to the **Integrations** page and click **New integration**
2. Select **Looker Studio**
3. Paste the cookie into the **Cookie** text input field and submit
4. Head to the **Sync History** tab on the side bar and click **Run sync**
### Troubleshooting
#### Invalid authentication
Looker Studio uses session cookies for authentication, which often expire. In order to resolve this error, you’ll have to generate a new session cookie and add it to your Secoda workspace. The way to do this is outlined in the Looker Studio docs, found [here](https://docs.secoda.co/integrations/google-data-studio#h_21e27f5a15-1).
---
# 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.secoda.co/integrations/data-visualization-tools/google-data-studio.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.