Build a Google Ads dashboard in Looker Studio

#01Connect Google Ads

1. Create a reusable data source > Google Ads connector.
2. Authorise an account with access to the customer or MCC.
3. Select the customer. For MCC rollups, select sub-accounts (max 50 per source per Google's docs).
4. Choose Overall Account Fields unless you know you need a single legacy report type.
5. Connect, set owner credentials, accept 12-hour freshness.
6. Name it Google Ads — Brand (owner).

#02Page plan

For AI Max / AI Overviews ads context, link stakeholders to Google Ads in AI Overviews and AI Mode rather than forcing every concept into one chart.

#03Conversion honesty

Pick one primary conversion column and write it on the cover:

• Google Ads conversion action "Lead - GA4"
• Or Ads-only offline import
• Or revenue for ecommerce

If leadership also watches GA4 key events, put both on a blend page later (lesson 12) instead of pretending they are identical on this page.

#04Calculated fields worth adding

• CPA = Cost / Conversions (NULLIF guarded)
• ROAS = Conversion value / Cost
• CPC = Cost / Clicks
• Search vs non-Search CASE on Campaign type / Channel type fields available in your field list (confirm names in your source)

#05Campaign table columns

Sort by Cost descending for weekly reviews; by Cost / Conv ascending when hunting efficiency.

#06Worked example: Ledgerline

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

Walkthrough

1. Finance compared Ads UI at 11:40 with Data Studio and saw a spend gap. Footer explained 12-hour freshness.
2. They standardised on "Lead - GA4" as the dashboard conversion.
3. Search page excluded PMax to stop CTR arguments.
4. Weekly review used this report beside the Google Ads monthly review routine.
5. Competitor A reported ROAS without naming the conversion; Ledgerline's labelled ROAS held up in diligence.

#07Search terms and assets

The Ads connector field list may not expose every UI report you love. Common pattern:

1. Keep account and campaign tables on the connector.
2. Export Search terms weekly to Sheets for a diagnostic page.
3. Export asset policy / disapproval counts similarly if needed.

Label those pages "Sheet export — not live Ads API".

#08Impression share and diagnosis

If impression share fields are available in Overall Account Fields for your account type, add them on the Search page only. Do not average IS across PMax and Search.

#09Alignment with Google Ads Academy

• Google Ads for Marketers
• GA4 key events import
• Monthly review routine
• Ads in AI Overviews and AI Mode

Use the dashboard in the monthly review meeting; do not reinvent the routine inside Data Studio.

#10Daily vs weekly use

Daily users should not fight average position metaphors from SEO on this Ads board — keep vocabularies separate.

#11Conversion action hygiene table

Publish this table on the Diagnostics page. When someone adds a new conversion action in Ads, the dashboard stays intentional instead of silently shifting CPA.

#12MCC rollup pattern

If you manage many accounts under an MCC:

1. Respect the 50 sub-account cap per Google Ads data source.
2. Split brands across multiple data sources when you exceed 50.
3. Name sources Ads — Region EU (owner) not Ads — all.
4. Keep brand-level reports on brand sources; use MCC rollups for leadership only when definitions match.

Mixing vastly different margin businesses into one ROAS table creates politics, not insight.

#13Our view

Our view: an Ads dashboard that hides the conversion definition is a liability. Label the action on the cover even if it feels redundant. Redundancy is cheaper than a wrong budget cut.

#14Common mistakes

• ROAS with no conversion definition.
• Mixing Search CTR with PMax in one average.
• Expecting real-time Ads numbers.
• Connecting 80 MCC children in one source (cap is 50).
• Personal login as owner on a client Ads source.

#15Try it yourself

Connect Google Ads with Overall Account Fields. Build overview scorecards and a campaign table. Write the conversion definition on the cover. Compare Cost to the Ads UI the next morning, not the same hour.

#16Quick quiz

1. Can you set Google Ads freshness to 1 hour?

Answer: No. It is fixed at 12 hours.

2. What is the MCC sub-account cap per data source?

Answer: 50.

3. Why separate Search and PMax tables?

Answer: To avoid mixing channel inventories and misleading CTR or efficiency averages.

#17What should you check before the next lesson?

• Ads data source on owner credentials.
• Conversion labelled.
• Freshness note in footer.

Previous: Build a GA4 marketing dashboard in Looker Studio. Next: Build a Search Console dashboard in Looker Studio. Or return to the Looker Studio for Marketers track. Related: Google Ads for Marketers, Google Ads GA4 key events import, Google Ads monthly review routine.

#18Common questions

How many Google Ads sub-accounts can one data source cover? Google documents that manager (MCC) accounts can connect and report on up to 50 sub-accounts per data source.

Why is Ads data in Data Studio not identical to the Ads UI at noon? Google Ads freshness in Data Studio is fixed at every 12 hours. The live Ads UI can move faster. State that in the footer.

Should conversion columns match GA4 key events? Not automatically. Align conversion actions in Google Ads with imported GA4 key events where that is your source of truth, and label which conversion column the dashboard uses.