Analytics Setup Checklist — GA4, GTM, Ahrefs Integration

Overview

When a new client site goes live, analytics infrastructure should be in place as quickly as possible. Data collection takes time to accumulate, so even a few weeks of lead time before a client review call makes a meaningful difference in what you can show.

This checklist was formalized after the ^[1] site launched without analytics in place, with a client call scheduled for March 16. The goal: have GA4, GTM, and Ahrefs configured well before that call so at least some baseline data is available.

Rule of thumb: Set up analytics on the day the site goes live, or as soon as it moves to the production domain — not when the first client call is scheduled.

Setup Checklist

1. Google Tag Manager (GTM)

[ ] Create a new GTM container for the client (or confirm an existing one)
[ ] Add the GTM snippet to the site <head> and <body> (or via CMS plugin)
[ ] Publish the container with at least a basic Page View trigger active
[ ] Verify the container is firing using GTM Preview mode

2. Google Analytics 4 (GA4)

[ ] Create a new GA4 property in the client's Google Analytics account (or agency account with client access granted)
[ ] Create a GA4 Configuration Tag in GTM, pointing to the new Measurement ID
[ ] Set trigger to "All Pages"
[ ] Publish GTM container
[ ] Verify data is flowing in GA4 → Reports → Realtime

Optional but recommended at launch:
- [ ] Enable Enhanced Measurement (scrolls, outbound clicks, file downloads, form interactions)
- [ ] Set up a basic Conversion event (e.g., contact form submission, phone click)
- [ ] Link GA4 to Google Search Console if the site is indexed

3. Ahrefs

[ ] Add the site to Ahrefs Site Explorer (verify ownership if needed)
[ ] Add the site to Ahrefs Site Audit and run an initial crawl
[ ] Note baseline metrics at launch: Domain Rating, organic traffic estimate, indexed keywords
[ ] Schedule recurring crawl (weekly recommended for active sites)

Timeline Guidance

Time Before Client Call	What You Can Show
4+ weeks	Meaningful trend data; crawl health baseline; early keyword movement
2–3 weeks	Initial traffic data; crawl issues identified and (ideally) resolved
1 week	Realtime verification only; very limited trend data
Day of call	Setup confirmation only — no useful data yet

For Fenwell U, setup was initiated approximately 3 weeks before the March 16 call. This is workable but not ideal — aim for setup at or before launch.

What to Present at the First Analytics Review Call

Even with limited data, you can present:

Proof of setup — Show the GA4 property is live and collecting data
Ahrefs baseline — Domain Rating, current organic traffic estimate, keyword count
Crawl health — Site Audit score and any critical issues found
What to watch — Set expectations: "Here's what we'll be tracking and what good looks like in 60–90 days"

Avoid over-promising on traffic numbers when the site is brand new. Frame the first call as establishing the baseline, not reporting results.

^[2]
^[3]
^[4]