Client reporting templates in Looker Studio

#01What is in the MASTER?

#02How do parameters help?

Create report parameters:

• client_display_name (text) — drives title text boxes via concatenation fields or manual titles updated at copy time.
• reporting_period_label (text) — "October 2026".
• Optional: show_ai_page (boolean) — hide/show via filters if you build optional modules carefully.

Some teams still change titles manually at copy time — that is fine if parameters feel heavy. Consistency matters more than cleverness.

#03Connector register (Sheet)

Review monthly. Link from the agency ops dashboard, not the client-facing file.

#04Handover when someone leaves

Because free Data Studio assets are user-owned, Pro org ownership is the durable fix (About Data Studio Pro). Until then:

1. Shared agency user owns production sources.
2. Register lists a backup owner.
3. Quarterly access review.
4. Never leave client Ads linked only to an intern's Gmail.

#05Worked example: Ledgerline (agency view)

Ledgerline here is treated as a client of a fictional agency. Details are illustrative.

Walkthrough

1. The agency had 40 one-off reports. Onboarding a new analyst took weeks.
2. MASTER cut build time from two days to three hours (illustrative).
3. A resignation no longer orphaned credentials because the register named backups.
4. Client QBRs used the same page order — stakeholders learned where to look.
5. Competitor agencies sent wall-of-charts PDFs; the template's AI visibility optional page became an upsell.

#06SOW-scoped modules

Sell modules explicitly. Shipping AI pages into every CORE report trains clients to expect unpaid scope.

#07QA script before client send

1. Logo and client name correct
2. Date range matches email subject
3. Conversion definition matches SOW
4. No internal UTM debug charts
5. Footer confidentiality present
6. Compare Ads Cost to UI next morning if same-day build

#08Naming conventions that scale

Sortability matters when you have dozens of clients. Leading _MASTER keeps the template at the top or bottom consistently.

#09When a client wants edit access

1. Offer a Pro personal report link if you have Pro.
2. Or schedule a live walkthrough and keep them on view.
3. Or create a separate "sandbox" copy refreshed weekly — never the contractual deliverable file.

#10Kickoff questionnaire (send before build)

1. Primary conversion definition in Ads and in GA4?
2. Countries / languages in scope?
3. Is AI visibility in the SOW this quarter?
4. Who receives weekly vs monthly?
5. Brand colours (hex) and logo file?
6. Any metrics you explicitly do not want clients to see (margins, partner costs)?
7. Data access: will the agency use MCC / GA4 user access / service account patterns your security allows?

Store answers in the client row of the connector register. Most rebuilds happen because question 1 was vague.

#11Versioning

When you change MASTER, bump MASTER_VERSION in a cover text box (for example 2026.11). Client copies note which MASTER version they were spawned from. That makes "why does Client B lack the AI page?" diagnosable in seconds.

#12Onboarding week plan (agency)

If access tickets stall, do not fake numbers in Sheets to "show progress". Show a cover page with blocked access listed explicitly.

#13Our view

Our view: templates are a product. If your agency cannot name the MASTER version a client copy came from, you do not have a template system yet — you have a folder of similar-looking reports. Fix naming before you buy another connector seat.

#14Handoff email snippet (draft only)

Subject: {Client} monthly dashboard — how to read it

Body outline: link to view-only report; conversion definition; freshness; who to ask; reminder not to forward externally. Do not auto-send from an agent — a human sends.

#15Common mistakes

• Editing MASTER for a rush client.
• Client edit access "so they can explore" without a Pro personal link strategy.
• No register.
• Mixing SOW scopes (AI page included for clients who did not buy it).
• Screenshots with someone else's logo still in the header.

#16Try it yourself

Create MASTER with cover + performance + appendix. Copy it for a sandbox client. Swap one data source. Fill three rows in a connector register.

#17Quick quiz

1. Who should own production data sources at an agency?

Answer: A shared agency user or Pro org-owned project — not a personal intern login.

2. What is the MASTER rule?

Answer: Never edit MASTER for a single client; always copy first.

3. Name two register fields.

Answer: Any two of: client code, property IDs, owners, last audit, report URL, notes.

#18What should you check before the next lesson?

• MASTER exists and is protected.
• Register Sheet started.
• Client share settings are view-only.

Previous: Executive reporting with Looker Studio. Next: Schedule and share Looker Studio reports. Or return to the Looker Studio for Marketers track. Related: Themes and layouts lesson, Governance lesson, About Data Studio Pro.

#19Common questions

How do agencies reuse one Looker Studio report for many clients? Keep a MASTER template with theme, page layout and parameters (client name, logo URL Sheet). Copy the report per client and swap data sources — do not edit MASTER.

Should client reports use viewer credentials? Prefer owner credentials on agency-owned service accounts or shared users so clients do not each burn separate GA4 tokens. Confirm contract and access policies.

What belongs in an agency connector register? Client, property IDs, data source names, credential owner, freshness, last audit date and who can rebuild if someone leaves.