Understand the AttribIQ overview dashboard

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 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.

A weekly review in practice

Suppose a weekly report shows 1,200 sessions, up from 1,000 in an equally long period. The 20% increase is a starting point for investigation, not proof that the site improved.

These numbers are illustrative. Use your own report values and a consistent goal denominator. A change in traffic mix can move a site's overall conversion rate even when individual pages behave the same way.

Build a report around a decision

Start with one question: which campaign to repeat, which page to improve, or which funnel step to investigate. Link that question to a traffic report and a measurable action.

For a content site, compare pages and landing pages with newsletter signups. For a lead-generation site, measure form completion as a goal. For a SaaS product, first review signup conversion, then add Stripe attribution if you need paid outcomes.

Next steps

Open the live sample dashboard, then learn how to read traffic sources and referrers.