Troubleshooting Looker Studio Destination
When integrating Looker Studio with Coupler.io, you may encounter some blockers. Here’s a breakdown of common problems and how to overcome them.
Most common issues with setting up Looker Studio as a destination:
2. Connecting a Source Without Data
3. Importer wasn't run or the last run failed
4.Import failed due to timeout
6. Looker Studio filters working unexpectedly
7.Importer was deleted before establishing the connection
8.Old Data appears in Looker Studio instead of the last imported data.
1. Different account in Looker Studio
Error: Your Looker Studio is linked to______ while Couplerio is under another email. Please ensure you sign into both Looker Studio and Coupler.io with the same email address.
If you are logged into different accounts for Looker Studio and Coupler.io, you may face issues during the data import process.
To fix this, ensure that you are logged into the same account for both Coupler.io and Looker Studio. If you need to switch accounts, you can easily do so by clicking the corresponding option on the Looker Studio account page:
2.Connecting a Source Without Data
Error: No rows or columns are returned in Looker Studio.
Solution:
Check that the data source in Coupler.io contains valid data and that the importer has been successfully run.
To do so go back to Coupler.io's Transformation wizard of your connected importer to check that your importer in indeed fetching data, it is working it should look something like this:
3.Importer Wasn't Run or the Last Run Failed
Error:
Importer execution has finished with an error. Please open importer and fix the issue following this url:
Solution:
Go back to Coupler.io importers page and make sure the importer in Coupler.io has been successfully run before connecting to Looker Studio. Check Coupler.io for any errors in the last run and retry.
4.Import Failed Due to Timeout
Error: Failed to fetch data from the underlying data set
The import process takes longer than expected, resulting in a timeout error in Looker Studio.
Solution:
Please run the importer, wait until it finishes successfully, and then create the Looker Studio report (destination → generate data source →) since Looker Studio has a 5-6 minute timeout limit, compared to Coupler.io's 9-minute limit. Adjust the data accordingly (remove uneeded fields and time ranges) so that it can move across all app timely.
Date Range Control Issue
Error: Old data may not appear in reports due to Looker Studio’s default "Auto" date range setting.
Solution:
Switch the "Auto" date range setting in Looker Studio to "Custom" and specify the date range you need for your report.
6. Looker Studio Filters Working Unexpectedly
Error:
Exclude filters don’t process null
values correctly in Looker Studio, leading to incomplete filtering.
- Include filter shows records that have value from filter
- Excude filter hides record that have value from filter - BUT Looker Studio has issue in processing
null
values:
Solution: If you use just Exclude some value -> Looker Studio will show you records that have value not equal to defined in filter, BUT will not show records withnull
values.
To exclude some value and return all other values andnull
-> filter should be adjusted with OR Include status is Null, as shown below:
7.Importer was deleted before establishing the connection
Error:Could not find the requested importer. Please check the Importer Id and try again
Original Importer was removed between adding it on Looker side and clicking on "Connect".
Solution:
Go back to Coupler.io and make sure to create a new importer with the proper title and link it to the data source in the dropdown:
8.Old Data is Shown (after "Import Failed Due to Timeout")
Error: Old data appears in Looker Studio instead of the latest imported data.
Solution:
- Run the importer in Coupler.io first, then update the data in Looker Studio.
- If using a scheduled importer, ensure it runs before a manual update from Looker Studio's side.
- If relying on Looker Studio’s auto-update, remember that it updates every 12 hours, even if Coupler.io has a more frequent schedule these timeframes need to be considered.