I spent two weeks building a content pipeline and then found I had no way to tell if it worked

Description and use

The author built a content pipeline with automated checks but could not verify that analytics data could be read back, leading to uncertainty about real traffic and revenue calculations. By adding a read-back verification step and distinguishing between own and external metrics, reliable traffic insight was achieved.

Problem

The author built a content pipeline with automated checks but could not verify that analytics data could be read back, leading to uncertainty about real traffic and revenue calculations.

Outcome

By adding a read-back verification step and distinguishing between own and external metrics, the author gained reliable insight into site traffic, enabling accurate revenue planning.

Workflow

• 1. Deploy content pipeline with automated checks for tag presence and firing.
• 2. Verify GA4 tag on all pages via network interception.
• 3. Attempt to read analytics data via GA4 API (property ID required).
• 4. Discover missing analytics.read permission and property ID. 5. Realize read-back not performed. 6. Add read-back step to installation process. 7. Separate own metrics from external platform metrics. 8. Update revenue planning to use only confirmed metrics. 9. Document metric limitations honestly.

Evidence

I built the write half completely. I never once tried the read half.

Source

I could not. The site runs behind Cloudflare, so request counts are already being recorded. I queried them: Actor does not have permission 'analytics.read' for zone

Source

That verification was thorough, and it verified the wrong half.

Source