Looker Studio: Build an Acquisition Dashboard That Helps Decisions

A useful Looker Studio acquisition dashboard does more than display marketing numbers. It gives stakeholders a consistent way to investigate a decision: where performance changed, whether a channel or landing page needs attention, and what should be checked before changing a budget, message, or website journey.

What an acquisition dashboard should do

Acquisition data is normally spread across systems. GA4 describes site sessions and events. Advertising platforms report delivery and spend. A CRM or sales team may add context about the conversations that followed. Looker Studio can make these signals easier to read together. It cannot, by itself, prove that one click caused a sale or that a channel deserves more budget.

The GA4 Traffic acquisition report is a useful starting point. It shows where new and returning visitors come from, using session-scoped cross-channel dimensions such as Session default channel group, Session source / medium, and Session campaign. Google distinguishes it from User acquisition, which concerns where new users came from. Label that scope in the dashboard so readers do not compare unlike measures (Google Analytics documentation).

The primary query for this group, “Looker Studio,” has volume 600; KD 25; TP 300 — Ahrefs Morocco estimate, 22 October 2026. That is a keyword-database estimate, not a traffic, ranking, sales, or lead forecast.

Start with decisions, not connectors

Before adding a connector, agree on the small set of questions the dashboard must answer. For example: Which channels bring engaged sessions? Are campaigns producing tested key events? Which landing pages receive visits but do not support the next action? Who will review the report, and at what rhythm?

For each question, specify the reader, the comparison period, the owner of the data definition, and the decision that may follow. A leadership view can be a monthly summary, while a media team may need campaign, device, or landing-page detail. This avoids a polished report becoming a crowded collection of metrics without an operating purpose.

Write a compact measurement dictionary

Keep definitions close to the dashboard for:

• the session and its scope in the GA4 property;
• the key event, how it fires, and how the team validates it;
• what counts as an enquiry, call, or purchase, without calling every interaction a lead;
• the UTM convention for source, medium, and campaign;
• currency, time zone, comparison window, and ownership of each source.

GA4 defines an engaged session as one lasting at least 10 seconds, or with one or more key events, or with two or more page or screen views. Engagement rate is engaged sessions divided by total sessions. Those definitions describe on-site activity; they do not replace a sales team's assessment of enquiry quality (GA4 metric definitions).

Visual design should follow, not precede, a tracking plan and tested events. That is the foundation of our tracking and analytics service.

Prepare sources and access deliberately

In Looker Studio, a data source structures the fields used in charts and controls. Google's documentation lists connectors for products including Google Analytics, Google Ads, and Google Sheets. Data sources are also where teams can set field types, parameters, and calculated fields (About data sources).

Use a restrained inventory: the relevant GA4 property, a Google Ads account where applicable, a validated cost source when needed, and a CRM or operational sheet only when its definitions and maintenance are sound. Do not add a source because it can be connected. Ask what decision it enables and who can reconcile it with the original system.

Set access with governance in mind

Reusable data sources can preserve a common data model across reports; embedded sources live with the report in which they were created. This is a maintenance and governance choice. With owner's credentials, trusted viewers can see data without access to the underlying dataset. With viewer's credentials, every viewer needs that access.

Sharing changes the risk profile. Google notes that when a report is shared through a public link, embedded data sources in the report are accessible to people with that link. Review the sharing setting and whether a source is embedded or reusable before publishing a dashboard (report-sharing guide).

A four-view dashboard structure

1. Decision summary

Show the date range and a like-for-like comparison, then sessions, engagement rate, and validated key events. Add cost or revenue only when the source, currency, and attribution rules are understood. Annotate material changes to tracking, campaigns, the offer, or the website. The goal is to surface a question worth investigating, not to turn a scorecard into an automatic verdict.

2. Channels and sources

Use a time series followed by a table for channel grouping, source / medium, and campaign. Keep dimension scope consistent with metric scope: session dimensions are usually appropriate for a traffic-acquisition view. Let readers filter by channel, campaign, or device instead of repeating nearly identical charts.

This view can identify a question for a Google Ads review when paid campaigns change, or for SEO in Morocco when organic discovery needs examination. It identifies where to investigate; it does not diagnose the channel alone.

3. Campaign, landing page, and action

Read campaign or source alongside landing page and key events. A page with visits but few actions is not automatically the cause. Search intent, ad promise, offer clarity, form friction, page performance, and incomplete measurement can all matter. Use the pattern to frame a testable hypothesis. A review of landing pages may be appropriate after the evidence is checked.

4. Data quality and context

Reserve a compact area for the last validation date, UTM coverage, key events pending review, active filters, and known changes. Later readers can then understand what a number describes rather than treating the dashboard as a universal record of reality.

Configure, reconcile, and test

1. Set a default date range that matches the decision cycle.
2. Add a date control and only useful channel, campaign, or device filters.
3. Explicitly choose the date-range dimension for every chart.
4. Reconcile totals against the source after building the report and after material changes.
5. Ask a non-editor to test whether labels are clear and expected data is visible.

A date-range control affects only charts using data sources with a date dimension. If a chart has several date fields, it uses the selected date-range dimension for that chart; its default scope is the page. Check this behaviour before comparing sources (date-range control documentation).

Calculated fields create derived metrics and dimensions. Calculate ratios at a consistent grain, for example SUM(Key events) / SUM(Sessions) when the numerator and denominator share the same scope. Data-source calculated fields can be used by reports using that source; chart-level fields exist only in that chart. Name formulas clearly and retain their definitions near the report (calculated fields documentation).

Limitations an honest dashboard should show

A dashboard reflects what was measured, not necessarily everything that happened. Consent choices, browser restrictions, ad blockers, and incomplete tagging can alter observable data. Attribution follows each platform's rules; it should not be presented as proof that a single channel caused a commercial outcome.

Cross-source blends need special care. Looker Studio supports a blend of up to five data sources, but its tables are aggregated before joining. If selected dimensions do not include a unique identifier, identical rows can collapse and affect the result. Validate the join key, date logic, currency, and aggregation level before using a combined total (how blends work).

GA4 can also apply data thresholds to prevent viewers from inferring an individual's identity or sensitive information. Thresholds are system-defined and can withhold values, especially with small volumes or sensitive dimensions. A missing row is not automatically evidence of no activity; inspect the data-quality indicator first (GA4 data thresholds).

FAQ — Looker Studio acquisition dashboards

Which KPIs belong at the top?

Choose measures attached to a real decision: sessions and engagement for traffic quality, tested key events for important on-site actions, and cost or revenue only when source, currency, and attribution are understood. More scorecards do not make a dashboard more useful.

Must GA4 and Google Ads be blended into one chart?

No. A side-by-side view is often sufficient initially. A blend can answer a specific question, but it needs a defensible join key, granularity, and filters. Compare its result with the original sources before using it in a budget discussion.

Why might dashboard numbers differ from an ad platform?

Platforms can use different attribution rules, time zones, conversion windows, session definitions, and consent handling. Compare the date range, currency, dimension, and measurement model before assuming a source is wrong.

How often should the dashboard be reviewed?

Match the rhythm to the decision cycle and data volume. A weekly review may reveal a tracking issue or sudden change; a monthly review offers more context. In either case, compare similar periods and log campaign, site, and measurement changes.

Sources

• Google Analytics — GA4 Traffic acquisition report
• Google Cloud — About Looker Studio data sources
• Google Cloud — Date range control
• Google Cloud — About calculated fields
• Google Cloud — How blends work
• Google Analytics — About GA4 data thresholds
• Planning data: “Looker Studio” — volume 600; KD 25; TP 300 — Ahrefs Morocco estimate, 22 October 2026.