# Understand the AttribIQ overview dashboard

> Read visitors, pageviews, sessions, engagement, acquisition, content, audience, and optional revenue from the AttribIQ overview.

Canonical page: [https://attribiq.com/guides/overview-dashboard](https://attribiq.com/guides/overview-dashboard)

Category: Web Analytics

Last updated: 2026-09-08

Topics: web analytics, dashboard, visitors, pageviews, sessions

## Summary

Start with the traffic trend, then use the acquisition, content, and audience summaries to decide which detailed report to open. Revenue is an additional outcome when a payment source is connected.

## What this guide covers

- Read the headline traffic metrics
- Switch the trend between visitors and pageviews
- Use acquisition, content, and audience summaries
- Separate web analytics from optional revenue data

The Overview is the starting point for checking what happened on a site during a selected period.

It combines traffic, engagement, acquisition, content, and audience summaries. When payment data is connected, it can also place revenue and paid conversions beside those web analytics metrics.

## Start with the date range

Select the same date range and reporting timezone whenever you compare periods or tools. A day boundary in one timezone can move sessions and events into a different date in another.

For a quick check, use a preset such as 24 hours, 7 days, 30 days, or 90 days. Use a custom range for a launch, campaign, or release window.

## Read the headline metrics

The core web analytics cards include:

- Visitors: distinct visitors represented in the selected period.
- Pageviews: tracked page-view events.
- Sessions: grouped activity within the session rules used by the tracker.
- Bounce rate: the share of sessions that did not continue into additional measured activity.
- Average session duration: average measured time across sessions.

Read [visitors, pageviews, and sessions](https://attribiq.com/guides/visitors-pageviews-sessions) before comparing them as if they were interchangeable.

## Use the trend before the rankings

Switch the main chart between visitors and pageviews to see whether the change is broad traffic growth or deeper browsing by a similar audience.

A total can hide a short spike or a slow decline. The trend helps you locate the date worth investigating in Acquisition, Pages, or Campaigns.

## Choose the next report

Use the overview summaries as routes into deeper questions:

- Acquisition for sources, countries, and devices.
- Pages for content and landing-page performance.
- Campaigns for tagged traffic and optional attributed revenue.
- Realtime for current sessions and incoming events.
- Goals and Funnels for conversion.
- Revenue for matched payment outcomes.

## Treat revenue as additional context

Revenue cards depend on Stripe or Payment API events. Empty revenue does not make the traffic reports incomplete; it means payment data is not connected or no accepted revenue events exist in the selected range.

If payments are connected, compare the traffic trend and revenue trend separately. More visitors do not automatically mean more paid conversions.

## Next steps

Open the [live sample dashboard](https://attribiq.com/demo-dashboard), then learn how to read [traffic sources and referrers](https://attribiq.com/guides/traffic-sources-referrers).

## Frequently asked questions

### Do I need Stripe to use the overview?

No. Visitors, pageviews, sessions, engagement, acquisition, content, and audience reports work without a payment integration.

### Why can two analytics tools show different totals?

Tracking coverage, bot filtering, session rules, timezone, blocked requests, and privacy settings can all change the totals. Align those rules before comparing.