Reports

Web analytics carries three report views beyond Overview, Realtime, Form funnels, and Goals: Paid campaigns, Performance, and Errors. All three read events directly, with no rollup dependency, and none require any setup beyond the tracking snippet already being installed.

Paid campaigns

Paid campaigns attributes traffic to the ad platform that sent it, using the click identifiers the tracking snippet already captures: gclid (Google), fbclid (Meta), msclkid (Microsoft), ttclid (TikTok), and li_fat_id (LinkedIn). Run ads with those parameters and the traffic appears here automatically; there is nothing to connect or configure.

The tiles show Paid clicks, Paid visitors, and Paid sessions for the period. If your workspace has at least one active goal, three more appear: Conversions, Conversion rate, and, once a goal carries a value, Revenue. Without an active goal, a link below the tiles points you to set one up.

The table below breaks the totals out per platform, with each platform's top landing page shown alongside its clicks, visitors, sessions, and (when goals exist) conversions and revenue.

Performance

Performance reports Core Web Vitals at the 75th percentile (p75) for the period, computed from the web_vitals events the snippet already collects on modern browsers. Five tiles cover the three Core Web Vitals, Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS), plus two supporting metrics, First Contentful Paint (FCP) and Time to First Byte (TTFB).

Each tile carries a rating badge using Google's standard thresholds: Good, Needs work, or Poor. Below the tiles, a Slowest pages table ranks paths by LCP p75; a path needs at least 3 LCP samples in the period to appear.

Errors

Errors reports uncaught JavaScript errors and unhandled promise rejections, grouped by message, for the period. Two tiles head the page: Total errors and Affected sessions. A clean report here means visitors are not hitting script errors; there is no configuration required to start collecting them.

The table below lists each distinct error message with its sample location, occurrence count, affected sessions, and when it was last seen.

Sampling, in one place

If your workspace is being sampled (see Overview for when that happens), every report that counts occurrences, page loads, error occurrences, goal conversions, treats each sampled row as 10 events to estimate the true total. Anything counted as distinct people or sessions, visitors, sessions, affected sessions, is always observed directly and never multiplied. Server-captured data, like the click identifiers behind Paid campaigns, is never sampled at all.