> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/destinations/categories/dashboards/data_studio.md). # Data Studio Send data to Data Studio with scheduled pipelines that automatically refresh your BI dashboards without manual exports via Coupler.io. Data Studio (formerly Google Data Studio) is Google's free business intelligence platform for building interactive dashboards and reports. It connects directly to your data and lets you visualize it with charts, tables, scorecards, and more — then share those reports with your team or clients. Sending data through Coupler.io to Data Studio gives you a reliable, scheduled pipeline that keeps your dashboards fresh without manual exports. ## Why use Data Studio as a Coupler.io destination? * **Any source, one dashboard** — combine data from Airtable, Amazon Ads, BigQuery, Pipedrive, Asana, and dozens of other sources into a single Data Studio report * **Scheduled refreshes** — Coupler.io fetches and prepares your data on a schedule, so Data Studio always has fresh data ready when it auto-refreshes * **Type enforcement** — Coupler.io detects column types automatically, so date, number, and text fields are recognized correctly in Data Studio * **Pre-built dashboard templates** — get started faster with free Data Studio dashboard templates available at coupler.io/dashboard-examples * **No connector limits** — link multiple data flows to a single report or spread data across reports as needed ## Prerequisites * A Google account to authorize Data Studio and Coupler.io * The **same Google account** must be used to log into both Data Studio and to authorize Coupler.io — mixing accounts causes a known connection error ## Quick start {% hint style="success" %} If you already have a Data Studio report you want to connect to, paste its URL into the **Report/data source URL** field in Advanced settings. This links your data flow directly to that report instead of creating a new one. {% endhint %} ## How to connect {% stepper %} {% step %} **Add a source to your data flow.** In Coupler.io, create a new data flow and configure your source — this can be any supported app or service such as Airtable, Amazon Ads, BigQuery, or Asana. You can add multiple sources and use Join, Append, or Aggregate transformations before the data reaches Data Studio. {% endstep %} {% step %} **Select Data Studio as your destination.** In the Destination step of your data flow, choose Data Studio from the list and click **Continue**. {% endstep %} {% step %} **Generate and authorize the data source.** Click **Generate Data Source**. You'll be prompted to authorize Data Studio with your Google account, then authorize Coupler.io with the same Google account. Complete both steps and confirm the connection back in Coupler.io. The data flow you're building will be pre-selected automatically. {% endstep %} {% step %} **Configure destination settings.** Review the detected field types and adjust any that look incorrect — especially date columns, which need to be DATE or DATETIME type for Data Studio's date range controls to work. Optionally set a **Date range dimension** if you want to use date filters in your report. {% endstep %} {% step %} **Run your data flow.** Click **Save and Run**. Wait for the run to complete successfully — you must have at least one successful run before you can create your Data Studio report or access advanced destination settings. {% endstep %} {% step %} **Create your report in Data Studio.** Once the run succeeds, click **Connect** or **View Results** to open Data Studio. Add fields as dimensions and metrics, then build your charts and dashboards. {% endstep %} {% endstepper %} ## Supported features | Feature | Supported | | -------------------- | --------- | | Replace mode | Yes | | Append mode | Yes | | Automatic scheduling | Yes | | Type enforcement | Yes | | Templates | Yes | ## Data Studio common issues ### Connection issues
"Your Data Studio is linked to [email] while Coupler.io is under another email" Data Studio requires the **same Google account** to be used in both Data Studio and to authorize the Coupler.io connector. If these accounts differ, the connection will fail. **Fix:** Log out of Data Studio and sign back in with the same Google account you used to authorize Coupler.io. If you've recently changed your Coupler.io account owner email, you'll need to revoke the old token first: 1. Log in with the old email at Data Studio 2. Go to your Google account's OAuth authorized applications page 3. Revoke access for **Data Studio App** 4. Log back in with the new email and reauthorize the connector {% hint style="warning" %} This is one of the most common setup errors. Always confirm both accounts match before troubleshooting further. {% endhint %}
"Valid data flow ID is required for execution" / Community Connector Error This error appears in Data Studio when the data flow ID it's trying to reference doesn't exist or is invalid — usually because the data flow was deleted after the connector was set up. **Fix:** Create a new data flow in Coupler.io with a proper title, run it successfully, then reconnect the Data Studio data source using the new data flow.
"Failed to fetch data from the underlying data set" / timeout error Data Studio has a 5–6 minute timeout when fetching data. If your data flow is still running or handles a very large dataset, Data Studio may give up waiting. **Fix:** Always run your Coupler.io data flow to completion **before** opening Data Studio to create or refresh your report. If timeouts persist, reduce the data volume by removing unused fields or narrowing the date range in your source configuration.
"No rows or columns returned" in Data Studio This happens when the data flow is connected to Data Studio before it has ever been run successfully, or when the source returned no data. **Fix:** Go back to Coupler.io, verify the source is returning data, and run the data flow manually until it completes successfully. Then return to Data Studio and refresh the data source.
### Data issues
Date columns aren't recognized as dates — date range control doesn't work This is a frequent issue. Data Studio's date range control only works with columns that are typed as DATE or DATETIME. If your date column is coming through as text, Data Studio won't offer it as a valid date range dimension. **Fix:** 1. In your Coupler.io data flow, go to the Destination settings and click **Edit** 2. Check the field type for your date column — it should be DATE or DATETIME 3. If it shows as text, change the type manually 4. Make sure your source data uses ISO date format (YYYY-MM-DD or YYYY-MM-DD HH:mm) 5. Set the **Date range dimension** field to your chosen date column 6. Save and run the data flow again {% hint style="warning" %} Charts that don't use the date dimension as a chart dimension won't respond to date range filters, even if the control is set up correctly. {% endhint %}
Old data is showing in Data Studio even after a successful run Data Studio auto-refreshes its data sources every 12 hours by default. Even if Coupler.io has fetched new data, Data Studio won't display it until its own refresh cycle runs — or until you trigger a manual refresh. **Fix:** After running your Coupler.io data flow, open the Data Studio report, click the three-dot menu, and select **Refresh data**. For ongoing freshness, schedule your Coupler.io data flow to run before Data Studio's 12-hour auto-refresh window.
Date range control shows "Auto" and won't filter data correctly The default "Auto" date range in Data Studio may not align with your data, causing it to appear empty or unfiltered. **Fix:** In your Data Studio report, switch the date range control from **Auto** to **Custom** and set the range manually to match your data.
Exclude filters aren't removing null values as expected Data Studio doesn't automatically include null values in exclude filter conditions. If you exclude a value like "Closed", rows where that field is null will also remain visible unexpectedly. **Fix:** Add an additional filter condition — **OR \[field] is Null** — alongside your exclude condition to explicitly handle null rows.
### Permission errors
"Could not find the requested data flow" This error means Data Studio is referencing a data flow that no longer exists in Coupler.io. **Fix:** Create a new data flow in Coupler.io, run it successfully at least once, then reconnect it in Data Studio by adding a new data source using the Coupler.io connector. {% hint style="danger" %} Deleting a data flow that is actively connected to a Data Studio report will break the report. Always disconnect the data source in Data Studio before deleting a data flow. {% endhint %}
## Data Studio FAQ
What's the best write mode for a Data Studio dashboard? **Replace** is the right choice for most dashboards. It overwrites the dataset on every run, so your report always reflects a clean, current snapshot of your data. Use **Append** only if you specifically need a running log — for example, tracking daily metrics cumulatively over time.
How does data refresh actually work between Coupler.io and Data Studio? The two platforms have independent refresh cycles. Coupler.io fetches your source data and prepares it on whatever schedule you set. Data Studio then pulls from that prepared dataset on its own cycle — by default, every 12 hours. For new data to appear in your report, both must happen: Coupler.io must run first, then Data Studio must refresh. If you need data to appear immediately, run your data flow manually in Coupler.io, then use the **Refresh data** option in Data Studio's three-dot menu.
Can I connect multiple sources to a single Data Studio report? Yes. You can set up multiple data flows in Coupler.io — each with different sources — and connect them all to the same Data Studio report as separate data sources. You can also use Coupler.io's Join or Append transformations to combine multiple sources into a single dataset before it reaches Data Studio.
Can I use an existing Data Studio report instead of creating a new one? Yes. In your Coupler.io data flow, go to the Destination step and open **Advanced settings**. Paste your existing report or data source URL into the **Report/data source URL** field. After that, clicking **View Results** will open your existing report instead of generating a new one.
Why can't I set a schedule or access advanced destination settings? Coupler.io requires at least one successful manual run before scheduling or advanced settings become available. Run the data flow first using **Save and Run**, confirm it completes without errors, and then those options will unlock.
Is there a Data Studio dashboard template I can start from? Yes. Coupler.io offers free pre-built Data Studio dashboard templates for a range of use cases. Browse them at [coupler.io/dashboard-examples](https://www.coupler.io/dashboard-examples?destination=Looker+Studio) and filter by the Data Studio destination.
Should I use Data Studio's "Extract Data" feature instead of Coupler.io? Data Studio's built-in Extract Data is a simpler option but is limited to single sources and basic extraction. Coupler.io gives you multi-source support, transformation options (Join, Append, Aggregate), scheduling control, and the ability to blend data from apps that don't have native Data Studio connectors. If your data comes from multiple tools or needs any shaping before visualization, Coupler.io is the stronger choice.
How do I organize fields in Data Studio when I have many columns? In your Coupler.io destination settings, enable the **Fields grouping** toggle. This lets you name columns using a **\[GroupName]: \[Field Name]** pattern, which creates a hierarchical structure in Data Studio's field panel — making it much easier to navigate large datasets.
What happens if I add new fields to my source after the report is already built? 1. Make sure the new fields appear in your Coupler.io data flow's Transformations step 2. Run the data flow 3. In Data Studio, open your data source and click **Refresh fields** 4. Apply the changes and then refresh the report New fields won't appear automatically — you need to refresh the data source schema in Data Studio after adding them.
{% hint style="info" %} For step-by-step instructions on setting up date range controls, see the **Date Range Control** article in this section. For refresh timing and scheduling guidance, see the **Data Refresh** article. {% 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.coupler.io/destinations/categories/dashboards/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.