Dashboard Features Explained

Simple explanations of what each quoter option means

โ† Back to Quoter

When building a marketing dashboard, there's often more involved than just connecting data sources and displaying charts. This guide explains the key features and add-ons you might need, and why they matter for your reporting.

Quick Navigation

๐Ÿท๏ธ Campaign Classifications

What is it?

Campaign classification adds custom grouping labels to your campaigns that don't exist in the raw data. It lets you categorise campaigns by business logic like division, product line, funnel stage, or any other grouping that makes sense for your reporting.

Why do you need it?

Ad platforms only know what you tell them. If you have 50 campaigns across different business units, the platform doesn't know which belong to "Recruitment" vs "Brand Awareness" vs "Product Sales". Classification adds that intelligence layer.

Example

You run campaigns for both volunteer recruitment and emergency alerts. By adding a "Division" classification, you can filter your dashboard to show only Volunteer campaigns, or compare performance across divisions - even though Google Ads has no idea these categories exist.

How it works

We create a lookup table that maps campaign names (or IDs) to your custom categories. When a campaign matches a pattern, it gets tagged with the appropriate label. These labels become filterable dimensions in your dashboard.

Without Classification 2024_FB_VolunteerRecruit_Perth 2024_FB_FireAlert_Metro 2024_GADS_VolunteerRecruit_Rural
With Classification Volunteer Recruitment โ†’ Perth Emergency Alerts โ†’ Metro Volunteer Recruitment โ†’ Rural

๐ŸŽฏ Conversion / Event Groupings

What is it?

Conversion grouping standardises and consolidates the different conversion actions tracked across your platforms. It ensures consistent naming and allows you to combine related conversions into meaningful totals.

Why do you need it?

Different platforms name things differently. Google Ads might track "Form_Submit_Contact_Page" while Meta tracks "lead" - but they're the same action. Without grouping, your dashboard shows fragmented, hard-to-compare data.

Example

You track 15 different conversion actions across Google and Meta. Some are variations of the same thing (Android app install vs iOS app install). Grouping lets you see "Total App Installs" as one number, while still being able to drill down to platform-specific details.

How it works

We create a naming lookup that:

Raw Platform Names actions_app_site_visit mybushfireplan_visitors Fire Danger Rating Scale - Catastrophic
After Grouping META - App Site Visit META - MyBushFirePlan Visitors GADS - FDRS Catastrophic

๐Ÿ”— Data Unification / Flat Table

What is it?

Data unification combines data from multiple ad platforms into a single, consistent table structure. This "flat table" or "master table" becomes the single source of truth for your dashboard.

Why do you need it?

Each platform structures its data differently. Google Ads exports in one format, Meta in another. Without unification, you'd need separate charts for each platform and couldn't easily compare or total across them.

Example

You want to see "Total Ad Spend" across Google, Meta, LinkedIn, and TikTok. Without a unified table, you'd have to manually add up four different numbers. With unification, it's one metric that automatically totals everything.

How it works

The unification process:

The result is one table where you can filter by platform, compare platforms side-by-side, or see totals across everything.

๐Ÿ“Š Extra Data Sources

What is it?

Additional data structure exports from the same platform type. This is when you need a different table or report format from a platform you already have connected - requiring a separate data source in Looker Studio.

Why do you need it?

Sometimes the standard data export from a platform doesn't contain everything you need. You might require a separate table with different dimensions, a different granularity level, or supplementary data that can't be combined in the same export.

Example

Your Google Ads connection pulls campaign-level data with standard metrics. But you also need ad group-level data with different dimensions, or a separate conversion breakdown table. Each distinct data structure requires its own data source configuration and Looker Studio connection.

Common scenarios

Note: Multiple ad accounts within the same platform are typically handled by the data connector (Power My Analytics) automatically - you don't need extra data sources just because you have multiple accounts.

๐Ÿ“„ Additional Pages

What is it?

Extra pages or views within your dashboard beyond what's included in your package. Each page typically focuses on a specific aspect of your data or a particular audience's needs.

Why do you need it?

Different stakeholders need different views. Executives want high-level summaries, campaign managers want detailed breakdowns, and finance needs budget tracking. More pages means more tailored views.

Example Pages

Executive Summary (KPIs only) โ†’ Campaign Performance (detailed metrics) โ†’ Channel Comparison (platform vs platform) โ†’ Budget Pacing (spend tracking) โ†’ Demographics (audience insights) โ†’ Conversion Analysis (funnel view)

What counts as a page?

๐Ÿ”Œ Custom Integrations

What is it?

A custom-built connection to a data source that doesn't have a standard connector. This involves API development, data transformation, and ongoing maintenance.

Why do you need it?

Not every data source has a plug-and-play connector. Proprietary systems, internal databases, or niche platforms often require custom development to extract and format data for reporting.

Example

You want to include data from your custom CRM, a legacy inventory system, or a specialised industry platform. There's no off-the-shelf connector, so we build one using APIs, database queries, or file imports.

What's involved

๐Ÿงฎ Custom Metrics / Parameters

What are Custom Metrics?

Calculated fields that don't exist in the raw data. These are formulas that compute new values from existing metrics - like conversion rates, cost ratios, weighted scores, or business-specific KPIs.

What are Parameters?

User-selectable controls that change what the dashboard displays. Parameters let viewers switch between different metrics, toggle conversion types, or choose comparison periods without editing the dashboard.

Custom Metric Examples

โ€ข Cost Per Qualified Lead (Spend รท MQLs)
โ€ข Blended ROAS (Revenue รท Total Spend across all platforms)
โ€ข Efficiency Score (Conversions ร— 100 รท Clicks)
โ€ข YoY Growth % ((This Year - Last Year) รท Last Year)

Parameter Examples

โ€ข Conversion selector: "Show me [App Installs / Form Submits / All Conversions]"
โ€ข Platform filter: "Compare [Google vs Meta / All Platforms]"
โ€ข Date granularity: "View by [Day / Week / Month]"
โ€ข Goal toggle: "Show performance vs [Target A / Target B]"

Why do you need them?

Raw platform metrics only tell part of the story. Custom metrics translate data into business language. Parameters make dashboards interactive and self-service, reducing requests for "can you make me a version that shows X?"

๐Ÿ“— Google Sheets Layer

What is it?

An intermediate data processing layer using Google Sheets between your raw data sources and Looker Studio. Data flows through Sheets where it can be transformed, combined, and enriched before reaching your dashboard.

Why do you need it?

Direct connections to Looker Studio are limited. Sheets provides a flexible transformation layer where you can:

When Sheets Layer is Essential

You have conversion data from Meta that needs to be pivoted (transformed from rows to columns), joined with campaign data, enriched with classification labels, and combined with Google Ads data - all before it reaches your dashboard. Sheets makes this possible with formulas that run automatically.

Foundation vs Growth/Transformation

Foundation Package: Uses direct Looker Studio connectors. Simpler setup, but limited transformation capability. Best for straightforward reporting needs.

Growth/Transformation Packages: Include Google Sheets layer by default. Enables advanced data manipulation, cross-platform unification, and complex business logic.