# Parameters, filters and controls in Looker Studio

> Add filter controls, date ranges, advanced filters and parameters so marketers can explore without breaking the report.

Source: https://mentionx.ai/learn/looker-studio/looker-studio-parameters-filters-controls  
Author: Dipuck Jones, founder of MentionX  
Updated: 5 November 2026  
Level: Practitioner

**Filters and controls turn a static dashboard into something a marketer can explore without asking ops for a new PDF. Parameters go further: they hold viewer input for what-if models, BigQuery SQL and template reports. This lesson shows which control to use, how to avoid filters that silently break totals, and how agencies use parameters for client-ready templates.**

> **Key takeaways**
>
> - Put a **date range control** on every marketing page.
> - Use **dropdown / fixed-size list** controls for channel, campaign, country and brand.
> - **Parameters** power what-if metrics, BigQuery SQL and client templates.
> - Chart-level filters are for exceptions; report-level and group-level filters keep pages consistent.
> - Tell viewers what a control does in a one-line caption.

*Checked 5 November 2026 (CET) against Google Cloud Data Studio documentation, the Data Studio product page, the Looker Studio-is-Data-Studio blog post, connector help pages and the Analytics Help pages cited in Sources. Google renames and moves features often, so confirm labels and limits in your own account. "Our view" marks MentionX opinion. Ledgerline is a fictional company used for illustration.*

## Controls marketers actually need

| Control | Use |
|---|---|
| Date range | Always |
| Drop-down list | Channel, country, brand, campaign |
| Advanced filter | Search inside page titles or queries |
| Checkbox / slider | Less common; good for parameter toggles |
| Data source control | Only when one page must switch properties carefully |

Group related charts, then apply a control to the group so one dropdown filters the whole block.

## Filter levels

1. **Report-level filter** — applies everywhere unless a chart opts out.
2. **Page-level filter** — one page (for example "UK only").
3. **Chart-level filter** — one visualisation.
4. **Filter control** — viewer-driven.

*Our view:* keep report-level filters rare. A forgotten "device = desktop" report filter has ruined more QBR slides than bad design.

## Parameters: three jobs

Google's parameters documentation lists three primary uses:

1. Use in **calculated fields** (for example a forecast multiplier).
2. Pass into **BigQuery custom SQL**.
3. Pass into a **community connector**.

### Forecast multiplier example

1. Edit the data source > Add a parameter > Number > default 1.
2. Create calculated field `Forecast leads = Key events * Forecast multiplier`.
3. Add an input box control linked to the parameter.
4. Label it clearly: "What-if multiplier (does not change GA4)".

### Agency brand parameter

Create a text parameter `Client brand` and a calculated field that flags rows matching that brand in a multi-client Sheet. Pair with [lesson 15](https://mentionx.ai/learn/looker-studio/looker-studio-client-reporting-templates).

## Filters that fight blends and GA4

- Filtering a GA4 table by a calculated field can make summary-row totals show null; Google documents this connector limitation.
- On blends, apply table filters in the blend editor when you need to restrict one side before the join ([lesson 7](https://mentionx.ai/learn/looker-studio/looker-studio-blending-data-sources)).
- Do not stack five overlapping controls that all filter Campaign. Viewers will create empty charts and blame Data Studio.

## Accessibility and training

Add a text box: "Use the date control first. Channel dropdown filters all charts on this page." Record a 60-second Loom once; link it from the cover page. Controls without guidance become unused chrome.

## Worked example: Ledgerline

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

| Control | Applies to | Default |
|---|---|---|
| Date range | Whole report | Last 28 days |
| Channel dropdown | Performance group | All |
| Country dropdown | Performance group | All |
| Forecast multiplier parameter | Planning page only | 1.0 |

### Walkthrough

1. Leadership used the date control; nobody asked for a new PDF that week.
2. The country control exposed that AI Assistant sessions were almost all US desktop (illustrative).
3. A leftover report-level filter from a test (`medium = cpc`) shipped once. They added a cover-page "active filters" checklist after that incident.
4. The forecast parameter lived only on the planning page so weekly ops numbers stayed factual.
5. Agency partners later copied the brand-parameter pattern for clients.

> **Pro move:** add a scorecard that shows `COUNT_DISTINCT(Session source)` or sessions next to heavy filters. When the number collapses to near zero, viewers see they over-filtered.

## Control types and when to use them

| Control | Best for | Watch-outs |
|---|---|---|---|
| Date range | Almost every marketing report | Default range too wide burns quota |
| Drop-down list | Channel, country, brand | High-cardinality dimensions become unusable |
| Advanced filter | Power users | Confuses executives |
| Slider | Numeric thresholds | Rare in exec packs |
| Checkbox / boolean parameter | Optional modules | Document what it hides |

## Filter vs data-source filter

- **Chart filter:** affects one chart.
- **Page / report filter control:** affects group of charts.
- **Data-source filter:** always-on (for example exclude internal traffic dimension if present). Prefer always-on filters for definitions you never want viewers to remove.

## Parameters for client templates

Text parameters for client display name and period label keep cover pages consistent across agency copies. Boolean parameters can flag whether the AI visibility page is in scope for that SOW. See [client reporting templates](https://mentionx.ai/learn/looker-studio/looker-studio-client-reporting-templates).

## Performance tip

Every control that triggers a GA4 refetch costs tokens. Do not put five unused controls on the exec page "for later". Add them on the ops page instead.

## Date range defaults that reduce quota pain

| Audience | Default range |
|---|---|
| Exec | Last 28 days |
| Ops Monday standup | Last 7 days |
| SEO deep dive | Last 28 days (GSC also lags) |
| Forensic incident | Custom — set deliberately |

Avoid "last 365 days" as the default on GA4-heavy pages. People can widen the range when they need history.

## Cross-filtering behaviour

When charts cross-filter each other, a click on a channel bar can silently filter the whole page. That is powerful for analysts and confusing for executives. On exec pages, disable unnecessary cross-filtering interactions. On ops pages, teach the behaviour once in a footnote: "Click a bar to filter; use Reset to clear."

## Teaching viewers in one footnote

```
Filters apply to charts on this page unless a chart is marked "unfiltered".
Reset filters from the control panel if numbers look too small.
Date range defaults to last 28 days — widen deliberately.
```

Put that on ops pages. Exec pages should need almost no filter literacy.

## Our view

Our view: every control is a teaching burden. Exec pages earn constraints; ops pages earn flexibility. If you need both audiences, split the reports instead of compromising the canvas.

## Common mistakes

- **Report-level filters left on after testing.**
- **Parameters that silently rewrite "official" KPIs.**
- **No date control.**
- **Advanced filter with case-sensitive mismatch.**
- **Ten controls on a page** nobody understands.

## Try it yourself

Add a date range control and a Session default channel group dropdown to your first dashboard. Apply them to a chart group. Confirm a viewer can change both without edit access.

## Quick quiz

**1. Name one valid use of a parameter.**

*Answer:* Calculated-field input, BigQuery SQL argument, or community connector argument.

**2. Why are leftover report-level filters dangerous?**

*Answer:* They silently restrict every chart and are easy to forget before sharing.

**3. Do parameters raise GA4 API quotas by themselves?**

*Answer:* No. They do not change native GA4 connector quota behaviour.

## What should you check before the next lesson?

- Date control on the production report.
- At least one dimension dropdown on a chart group.
- No forgotten report-level filters.

Previous: [Calculated fields, CASE, groups and bins in Looker Studio](https://mentionx.ai/learn/looker-studio/looker-studio-calculated-fields). Next: [Blend data sources in Looker Studio (up to five tables)](https://mentionx.ai/learn/looker-studio/looker-studio-blending-data-sources). Or return to the [Looker Studio for Marketers track](https://mentionx.ai/learn/looker-studio/looker-studio-for-marketers). Related: [GA4 free-form explorations](https://mentionx.ai/learn/ga4/ga4-free-form-explorations-segments), [Google Ads monthly review routine](https://mentionx.ai/learn/google-ads/google-ads-monthly-review-routine), [Executive GEO dashboard template](https://mentionx.ai/learn/templates/executive-geo-dashboard-1-page-kpi).

## Common questions

**What is a parameter in Looker Studio?** A field that holds a user-provided value. You can use it in calculated fields, pass it into BigQuery custom SQL, or pass it to a community connector.

**What is the difference between a filter and a control?** A filter restricts data behind the scenes. A control is a UI widget (dropdown, date range, advanced filter) that lets viewers change filters or parameters.

**Can parameters change how the GA4 connector behaves?** Parameters do not bypass GA4 quotas or rewrite the native GA4 connector. They shine with calculated fields, BigQuery SQL and community connectors.
## Sources

- Google Help, [Parameters](https://support.google.com/looker-studio/answer/9002005?hl=en)
- Google Cloud, [About calculated fields](https://docs.cloud.google.com/data-studio/about-calculated-fields)
- Google Cloud, [Connect to Google Analytics](https://cloud.google.com/looker/docs/studio/connect-to-google-analytics)
- All accessed 5 Nov 2026.

## Frequently asked questions

### What is a parameter in Looker Studio?

A field that holds a user-provided value. You can use it in calculated fields, pass it into BigQuery custom SQL, or pass it to a community connector.

### What is the difference between a filter and a control?

A filter restricts data behind the scenes. A control is a UI widget (dropdown, date range, advanced filter) that lets viewers change filters or parameters.

### Can parameters change how the GA4 connector behaves?

Parameters do not bypass GA4 quotas or rewrite the native GA4 connector. They shine with calculated fields, BigQuery SQL and community connectors.

---

Written and reviewed by Dipuck Jones for MentionX Learn. The HTML version of this page: https://mentionx.ai/learn/looker-studio/looker-studio-parameters-filters-controls