Reporting and analytics
This domain tests how marketers read HubSpot analytics and turn CMS activity into decisions: traffic sources, page and blog performance, campaign reporting, conversion metrics, and attribution. The exam expects you to choose the right metric and recognize when a comparison is invalid.
Core rules and concepts
- Traffic analytics shows sessions and sources; page analytics shows views, CTAs, and submissions; blog analytics adds post-level engagement; campaign analytics groups assets.
- Conversion rate is submissions divided by sessions, or by visits depending on the report. Page views and sessions are not interchangeable.
- Attribution reports connect contacts or revenue to touchpoints using models such as first touch, last touch, and multi-touch. The model and lookback window change the conclusion.
- A/B tests compare variants with a control; adaptive tests shift traffic toward better performers. Both need enough volume and a clear success metric.
- Segment before concluding: source, device, lifecycle stage, and new versus returning visitors can reverse an aggregate trend.
- Dashboards should tie to a question, not collect every available metric.
Worked example
A landing page’s conversion rate falls from 8% to 5% after a redesign. Sessions are stable, but mobile sessions rose from 30% to 55% and mobile submissions fell sharply. The marketer compares mobile and desktop separately, finds the form’s submit button is below the fold on mobile, fixes it, and reruns the test. Reasoning: the aggregate drop was a mix shift, not necessarily a desktop design failure; segmentation identified the real cause.
Traps that cost marks
Comparing periods with different campaign coverage; treating correlation as causation; ignoring bot or internal traffic; using page views as conversions; reading attribution without stating the model; calling an A/B test early.