◆ Google Looker

Connect Looker Studio to data sources

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskConnect the new Shopify sales data to the existing e-commerce dashboard so we can see the…+
Connect the new Shopify sales data to the existing e-commerce dashboard so we can see the latest product performance metrics by end of day today.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I connect this new Shopify data to the e-commerce dashboard, ensure the connection is…+
Before I connect this new Shopify data to the e-commerce dashboard, ensure the connection is stable, handles large volumes, and automatically refreshes daily. I need it to be reliable for the finance team's weekly reports.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm trying to connect the new CRM data for the sales team's pipeline dashboard, but the source…+
I'm trying to connect the new CRM data, but it's not showing up in the available sources, and the project manager is asking for updates.
I'm trying to connect the new CRM data for the sales team's pipeline dashboard, but the source isn't appearing as an option, and I've already tried the usual steps. The project manager is pushing for an update by lunch, and I'm worried I'm missing something fundamental or that there's a permissions issue I can't see. What's the likely problem, and what's my best next step to get this connected quickly?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternConnecting new data sources always seems to take longer than I anticipate, leading to delays in…+
Connecting new data sources often takes longer than expected, delaying critical reporting.
Connecting new data sources always seems to take longer than I anticipate, leading to delays in getting new dashboards live for teams like sales and marketing. This impacts our agility and my reputation for delivering on time. What habit can I change to streamline this process and ensure I'm setting up connections efficiently and correctly from the start?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Google Looker's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.