◆ Google Looker

Embed Looker analytics in applications

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 taskEmbed the Q3 customer churn dashboard into the sales team's internal portal by Friday, making…+
Embed the Q3 customer churn dashboard into the sales team's internal portal by Friday, making sure it updates daily and requires no extra login for them.
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 embed this customer acquisition report for the marketing team, make sure it's easy to…+
Before I embed this customer acquisition report for the marketing team, make sure it's easy to read on a phone, highlights the top 3 channels, and clearly shows the ROI for each.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe VP of Product just asked why the embedded product usage dashboard is showing stale data for…+
The VP of Product just asked why the embedded product usage dashboard is showing stale data for half the users.
The VP of Product just asked why the embedded product usage dashboard is showing stale data for half the users. I'm afraid this will undermine trust in all our data. I can't tell her yet if it's a caching issue, a data source problem, or something with the embedding setup. What's the most likely cause here, and what's the first thing I should check to diagnose this?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep getting pulled into urgent troubleshooting for embedded dashboards that stop working or…+
I keep getting pulled into urgent troubleshooting for embedded dashboards that stop working or show incorrect data.
I keep getting pulled into urgent troubleshooting for embedded dashboards that stop working or show incorrect data, often because of credential expiry or source changes. This is costing me hours every week. What habit should I change to proactively monitor and prevent these embedding failures before they hit the business users?
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.