◆ Google Looker

Migrate dashboards from UA to GA4

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 taskMove all the dashboards currently pulling from our Universal Analytics property to use the new…+
Move all the dashboards currently pulling from our Universal Analytics property to use the new GA4 data source by end of day Friday, ensuring all historical data comparisons remain accurate.
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 switch these dashboards to GA4, help me identify any custom dimensions or metrics that…+
Before I switch these dashboards to GA4, help me identify any custom dimensions or metrics that won't directly map over, so I can plan for their recreation or deprecation without breaking existing 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 just connected the new GA4 data source for our marketing dashboards, and the user counts are…+
The new GA4 data source for our marketing dashboards is showing significantly lower user counts than I expected, and the marketing director is asking for a quick explanation.
I just connected the new GA4 data source for our marketing dashboards, and the user counts are way off compared to Universal Analytics. The marketing director is asking for an immediate explanation, and I'm worried about losing trust. I can't tell her I don't know why. Is this a common GA4 migration issue, or did I mess up the data connection? What's the fastest way to diagnose this discrepancy and explain it clearly?
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 underestimating how long it takes to validate data after a source migration, especially…+
I keep underestimating the time needed for data source migrations and end up scrambling to fix broken reports last minute.
I keep underestimating how long it takes to validate data after a source migration, especially with the subtle differences between platforms like UA and GA4. This always leads to last-minute fixes and stress. What habit should I change to build in better validation and communication before I commit to a 'done' date?
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.