Schedule and share Looker Studio reports

#01How should you share reports?

Avoid "anyone with the link" for anything with spend or PII-adjacent dimensions. Prefer Google Group recipients so joiner/leaver automation works.

#02How does scheduled delivery work?

1. Open the report > schedule delivery (UI label may say Schedule email or Manage schedules).
2. Choose cadence (daily/weekly/monthly), time zone (use Europe/Berlin for Dipuck's team context when relevant; otherwise the stakeholder zone).
3. Select pages to include.
4. Add recipients who already have at least view access.
5. Send a test to yourself.
6. Document the schedule in the connector register.

Pro enhancements (per Google's About Data Studio Pro page): up to 200 delivery schedules per report, delivery to Google Chat, and alerts when a chart meets criteria you set.

#03What about Gemini → Slides?

With Gemini in Data Studio enabled on Pro (preview, no extra cost for a limited time per Google's Gemini overview), you can generate or update Slides from report visuals. Treat that as board-deck assembly, not as a substitute for the live dashboard. Validate AI summaries before the meeting.

#04Access review checklist (monthly)

• [ ] Editors list still correct
• [ ] Client links still needed
• [ ] Scheduled recipients still employed / still on the account
• [ ] Data source owners still valid
• [ ] Public links: none unexpected

#05Worked example: Ledgerline

Ledgerline is a fictional accounts-payable software company. Details are illustrative.

Walkthrough

1. Someone shared edit to "all of sales". A rep broke a chart; rollback took an hour.
2. Ops switched sales to view + scheduled PDF.
3. Pro trial added a Chat ping when CPA > target for three days (illustrative alert).
4. Personal report links let the CFO explore filters without cloning chaos.
5. Quarterly access review removed two ex-agency logins.

#06Free vs Pro delivery features (summary)

Confirm exact free-tier schedule caps in your UI when you set production cadences — Google adjusts product limits over time.

#07Time zone discipline

Pick the stakeholder zone for send time. For a Europe/Berlin leadership team, Monday 07:30 CET beats Sunday night UTC surprises. State the zone in the schedule name.

#08Recipient hygiene

• Prefer Google Groups (marketing-leadership@) over 15 individual addresses.
• When someone leaves, group membership drops them automatically if IT runs offboarding well — still verify.
• For clients, use aliases that your agency controls forwarding for, not personal Gmail when avoidable.

#09Alert design (Pro)

Good alerts fire on durable conditions, not noise:

Bad alerts fire every night on normal variance. Start with one alert. Tune for two weeks before adding more. Alerts are not a substitute for the weekly one-pager.

#10PDF page selection

Schedule only the pages each audience needs. Leadership gets Cover + Exec. SEO gets GSC. Sending the full 12-page PDF trains people to ignore the email.

#11Confidentiality footer (copy)

Confidential — {Company}. Not for forwarding outside the recipient list.
Data freshness: Ads & Search Console every 12 hours; GA4 {setting}; Sheets {setting}.
Questions: {owner email}

Scheduled PDFs travel. Footers travel with them. Missing footers are how screenshots appear in the wrong Slack workspace.

#12Our view

Our view: distribution is part of accuracy. A correct dashboard that arrives after the meeting is operationally wrong. Name schedules clearly, test them, and revoke access with the same seriousness you revoke Ads login rights.

#13Link rotation after incidents

If a report link leaked externally, rotate sharing (remove public/anyone links, re-share to groups), note the incident in the register, and regenerate scheduled deliveries if recipients looked wrong. Treat dashboard links like document links with spend data inside.

#14Failure monitoring

Once a month, open the schedule manager and confirm last successful send times. Bounced recipients and revoked Google accounts show up here before stakeholders complain that "the dashboard died".

Document the Google Group addresses that own view access next to each schedule name in the connector register so future ops can tell who should still receive PDFs.

Test every new schedule once before you call the rollout done.

#15Common mistakes

• Edit for everyone.
• Schedules without tests.
• Recipients who lack view access (delivery fails silently from their perspective).
• Public links on Ads cost pages.
• Assuming free-tier schedule limits match Pro.

#16Try it yourself

Schedule a one-page PDF to yourself for tomorrow morning. Revoke one stale viewer. Write the schedule name into your register.

#17Quick quiz

1. What Pro schedule cap does Google document per report?

Answer: Up to 200 delivery schedules.

2. What does a personal report link do?

Answer: Opens a private copy for the clicker to explore without changing the master.

3. Should clients get edit by default?

Answer: No. View (or Pro personal link) is the default.

#18What should you check before the next lesson?

• At least one tested schedule.
• Editors list reviewed.
• Footer present on scheduled pages.

Previous: Client reporting templates in Looker Studio. Next: Fix Looker Studio performance and GA4 quota errors. Or return to the Looker Studio for Marketers track. Related: About Data Studio Pro, Gemini in Data Studio overview, GA4 Looker Studio reporting.

#19Common questions

Can I schedule Looker Studio email delivery on the free tier? Yes, scheduled email delivery exists on standard Data Studio, with limits. Data Studio Pro raises the cap to as many as 200 delivery schedules per report and adds Google Chat delivery plus threshold alerts.

What is a personal report link in Data Studio Pro? A link that opens a private copy of the report for the person who clicks it, so they can explore without editing your master.

Should I share data sources the same way I share reports? Manage data source access deliberately. Owner credentials mean viewers can see data through the report without each needing connector access; still control who can edit the source.