◆ Google Looker

Aggregate dates in Looker Studio

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.

3prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskAggregate the 'Daily Website Traffic' data in the 'Marketing Performance' dashboard to show…+
Aggregate the 'Daily Website Traffic' data in the 'Marketing Performance' dashboard to show weekly and monthly trends, so the marketing team can easily see long-term patterns for the Q4 campaign review on Friday.
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 share this new 'Sales Funnel Analysis' dashboard, make sure the date aggregations are…+
Before I share this new 'Sales Funnel Analysis' dashboard, make sure the date aggregations are intuitive for the sales managers. They need to quickly compare performance across different timeframes – monthly, quarterly, and year-over-year – without getting lost in too many options. Flag anything that looks confusing or redundant.
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 sales director just said the 'Monthly Deal Velocity' chart is off compared to his…+
The sales director just complained that the 'Monthly Deal Velocity' chart on the dashboard isn't showing the same numbers as his internal spreadsheet, even though both are supposed to pull from Salesforce.
The sales director just said the 'Monthly Deal Velocity' chart is off compared to his spreadsheet, both from Salesforce. I'm afraid there's a different date aggregation happening on our end, maybe a timezone issue or a fiscal calendar mismatch, but I can't tell him I'm not sure how our system handles it. What's the most likely reason for this date aggregation discrepancy, and what's my best immediate action to reconcile it?
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.