QUINN REAMS

Case Study

Web / SEO Analytics Lab

A live marketing analytics project built on my portfolio site using Google Analytics 4 and Google Search Console to measure engagement, CTA behavior, and early SEO visibility.

GA4 Search Console Web Analytics SEO Event Tracking
View GitHub Visit Live Site

Executive Summary

After relaunching my portfolio website, I built a measurement framework to understand how visitors interact with the site and which actions indicate meaningful engagement. This project uses Google Analytics 4 and Google Search Console to track traffic sources, engagement behavior, and key calls-to-action such as resume downloads, project exploration, and contact clicks.

The result is a live analytics lab where the site itself becomes a testing environment for marketing analytics techniques including event tracking, KPI definition, baseline reporting, and SEO monitoring.

Business Problem

  • Traffic sources were unknown after the portfolio relaunch.
  • Resume downloads, project clicks, and contact actions were not measurable.
  • It was unclear whether visitors explored deeper portfolio content or exited early.
  • No baseline existed for evaluating future SEO or content improvements.

Measurement Framework

To measure meaningful engagement on the portfolio site, I designed a tracking framework centered around key visitor actions and marketing signals. Events were implemented in Google Analytics 4 and aligned with defined KPIs for evaluating site performance.

Tracked Events

  • Resume downloads
  • Project clicks
  • Contact link clicks
  • Outbound GitHub clicks
  • Scroll depth

Primary KPIs

  • Engaged sessions
  • Average engagement time
  • Resume download rate
  • Project exploration rate
  • Traffic source breakdown

Data Sources

  • Google Analytics 4
  • Google Search Console
  • UTM campaign tracking
  • Custom event instrumentation

Tracking Implementation

The measurement framework was implemented directly on the live portfolio site using Google Analytics 4 event tracking, structured CTA tagging, and consistent naming conventions for meaningful actions.

CTA Events Tracked

  • resume_download
  • email_click
  • github_click
  • project_click

Instrumentation Approach

Key CTA links across the site were given stable identifiers and tracked through shared site logic so event measurement stayed consistent across components and pages.

Validation

Realtime testing in GA4 confirmed that core custom events fired successfully on the live site after implementation.

Baseline Reporting

Because this project is still in its early live phase, the first reporting window is treated as a baseline rather than a mature performance review. The goal is to establish a clean starting point for acquisition, engagement, CTA behavior, and future optimization.

Reporting Scope

  • Traffic acquisition
  • Top pages and page-level engagement
  • Custom and automatic event counts
  • Early CTA behavior

Key Metrics Tracked

  • Users
  • Sessions
  • Engaged sessions
  • Engagement rate
  • Resume downloads
  • Email clicks
  • GitHub clicks
  • Project clicks

What This Baseline Supports

  • Future comparison against new content releases
  • CTA performance analysis by location
  • Homepage-to-project exploration tracking
  • SEO and traffic trend measurement over time

Evidence & Reporting Screens

The screenshots below document the live instrumentation and early reporting structure used in this project. Because the site is still in its launch phase, these visuals focus on validating event tracking, confirming real-time data collection, and establishing baseline engagement reporting.

GA4 event tracking report showing custom events including resume download, email click, github click, and project click

Custom Event Tracking

Google Analytics 4 event reporting confirms that custom events such as resume_download, email_click, github_click, and project_click are successfully firing on the live site.

GA4 realtime analytics showing active users

Realtime Validation

Realtime monitoring was used during implementation to confirm that tracking scripts and event instrumentation were working correctly on the live production site.

GA4 page views report showing baseline page engagement

Baseline Page Engagement

Early reporting highlights which portfolio pages receive the most engagement, establishing a baseline for future content and SEO performance comparisons.

Current Limitations

This project is intentionally being documented during the launch and early data collection phase. Because of that, current findings are directional rather than final.

Known Constraints

  • Traffic volume is still low in the launch phase.
  • Early data may include some internal testing noise.
  • Search Console visibility data will take time to accumulate.
  • Some deeper project pages are still being expanded.

Next Actions

  • Continue collecting week 1 baseline data.
  • Add screenshots from GA4 traffic, pages, and events reports.
  • Mark core custom events as GA4 Key Events once fully processed.
  • Compare CTA performance by placement across the site.
  • Add Search Console data as impressions and clicks accumulate.

Project Outcome

This project transformed the portfolio site into a live analytics environment where marketing measurement techniques can be tested and improved over time.

  • Established a full GA4 measurement framework for site engagement.
  • Implemented consistent CTA event tracking across the portfolio.
  • Created a baseline reporting structure for acquisition and engagement.
  • Connected Search Console data for early SEO visibility tracking.
  • Documented a repeatable analytics workflow for future projects.