15 Free Data Analyst Dashboard Templates for Tableau (Data Analytics Reports)

What is a data analyst dashboard?

A data analyst dashboard brings data from one or more sources into a single workbook. This enables analysts to join, validate, and compare the data before reporting the results. For example, they might combine GA4 sessions with Search Console clicks by landing page. Once they’ve checked the data, they can share a summary with a marketing lead.

On this page, each dashboard is a Tableau workbook. Windsor.ai pulls the data from GA4, Search Console, and 350+ other sources and delivers it as a CSV file, a Google Sheet, or a BigQuery table, so you don’t export each platform by hand.

Which data analyst dashboard template to pick

The table lists all 15 free templates in this gallery. All of them require a Tableau account.

Data analyst dashboard example: GA4 and Search Console joined by landing page

This example uses Windsor.ai’s GA4 property and Search Console data for Q3 2026 (1 July to 30 September). It checks how well the two sources match before you combine them in a page-level report.

Step 1: Connect GA4 and Search Console. Sign in at onboard.windsor.ai, choose the GA4 connector, and authorize your property. Then add the Search Console connector and select your site.

Step 2: Pull the fields. Pull each source for the quarter as its own CSV file. In GA4, keep the sessions from Google organic search that started on your main domain.

Step 3: Match the page formats. Search Console returns full URLs, and GA4 returns paths without the domain. Reduce both to a lowercase path, remove query strings, and end every path with a slash. The slash step makes a GA4 path such as /pricing match a Search Console URL ending in /pricing/.

Step 4: Join the files in Tableau. Add both CSV files as data sources and join them with a full outer join on the cleaned path, so rows from either side stay in. Then sort each row into one of four groups: the page is in both sources, GA4 shows the landing page as (not set), the landing page is only in GA4, or the page is only in Search Console.

99.8% of Search Console clicks went to a page that GA4 also recorded as a landing page. For 14.2% of Google organic sessions, GA4 recorded the landing page as (not set). Only 5.6% of those sessions were engaged. GA4 shows (not set) as the landing page when a session has no page_view event, as Google’s help page on (not set) explains.

Step 5: Compare sessions with clicks. For the pages in both sources, divide GA4 sessions by Search Console clicks.

GA4 recorded 0.95 sessions for each Search Console click on the matched pages. Among pages with at least 100 clicks, excluding the homepage, 76% of clicks went to pages where sessions were within 20% of clicks. Another 23% went to pages with fewer than 0.8 sessions per click. Check the pages with fewer than 0.8 sessions per click first for a missing GA4 tag or a redirect. The Tableau Google Search Console template in the table shows how to load the Search Console side of this join from a Windsor.ai CSV file.

What KPIs does a data analyst dashboard track?

A data analyst dashboard should track business results and data completeness. Windsor.ai brings in the required fields from GA4, Search Console, and ad platforms. You can then calculate sessions per click, join coverage, and share in Tableau after joining the datasets.

• Engagement rate: engaged sessions divided by sessions. GA4 counts a session as engaged when it lasts longer than 10 seconds (the default, which you can change in the Google tag settings), has a key event, or has two or more page views.
• Key events per session: key events divided by sessions. In Windsor.ai, the conversions field holds GA4’s key events.
• CTR: total clicks divided by total impressions. Calculate it from the totals, because an average of row CTRs gives a row with 10 impressions the same weight as a row with 10,000.
• Average position: the sum of position times impressions, divided by total impressions, so a query shown 40,000 times counts more than one shown once.
• Sessions per click: GA4 sessions from Google organic search divided by Search Console clicks, for the same pages and dates.
• Join coverage: clicks on pages found in both sources divided by all Search Console clicks.
• (not set) share: sessions with the landing page (not set) divided by all sessions.
• Cost per conversion: ad spend divided by conversions, for the templates that include ad platforms.

What to include in a data analyst report

A data analyst report shows what changed, which sources and pages account for the change, and whether the data is complete.

Split the data by date (day, week or month), source and medium or channel group, landing page, device and country. For ad platform data, also split it by campaign.

For example, a weekly report from an analyst to a marketing lead could open with sessions, engagement rate, key events, and Search Console clicks, each next to the previous week.

Below them, add one row per landing page, with clicks, sessions, sessions per click, and engagement rate. At the bottom, list three data checks: join coverage, (not set) share, and the latest complete day in Search Console.

Browse the full template gallery for dashboards by platform and destination, or see the web analytics templates for reports that combine GA4 with other site data. How to use Windsor.ai for web analytics shows how to ask an AI assistant which pages and channels bring key events.

Start with the free forever plan, no credit card, at onboard.windsor.ai. Paid plans from $19/mo.