Live delivery
Source-managed portfolio and downloadable recruiting documents deployed on Cloudflare Pages.
Case Study · Cloud Infrastructure / Analytics / Operational Delivery
I turned a static professional portfolio into an instrumented recruiting channel: Cloudflare Pages delivery, consent-aware analytics, documented campaign attribution, and verified résumé/impact-sheet interactions. The goal was not a more elaborate website. It was reliable evidence about whether outreach leads to engagement.
My role: End-to-end technical owner—defined measurement requirements, implemented event instrumentation, configured analytics and consent controls, diagnosed reporting issues, and validated the resulting data.
Outcome at a glance
Source-managed portfolio and downloadable recruiting documents deployed on Cloudflare Pages.
Cloudflare Web Analytics traffic plus confirmed GA4 pageviews, custom document-click events and campaign landing events.
Analytics consent choices tested; campaign parameters constrained; no claim to identify individual visitors.
Business objective
The professional portfolio needed to support a targeted job-search strategy—not simply display a résumé. The core questions were practical: Which channels bring visitors? What material do visitors explore? Are recruiter campaign links being used? Do visitors click to download the résumé or executive impact sheet? And can these measurements work without attempting to identify individual visitors?
Host a professional portfolio, leadership case studies and downloadable recruiter documents with static-site deployment through Cloudflare Pages and GitHub.
Capture pageviews, document-download clicks, contact and outbound interactions, and campaign-tagged arrivals.
Use an Analytics purpose in Cloudflare Zaraz Consent Management to gate GA4 reporting based on visitor choice.
Architecture
GitHub repository → Cloudflare Pages → public static site, downloadable PDFs and a small shared JavaScript event module.
Cloudflare Web Analytics for site-level traffic, alongside Cloudflare Zaraz forwarding pageviews and custom engagement events to Google Analytics 4.
Allowlisted UTM campaign parameters, named events, and an event-scoped GA4 custom dimension (`kind`) to distinguish résumé and impact-sheet clicks.
The event module uses explicit names such as portfolio_document_download, portfolio_campaign_landing, portfolio_contact_click and portfolio_outbound_click. Events represent observed clicks or arrivals—not proof that a file was read, a contact was completed, or a recruiter was identified.
Engineering judgments
Kept hosting and primary traffic visibility in Cloudflare rather than introducing a separate application backend just to track recruiter engagement.
Used explicit event names and document categories, rather than assuming every PDF link or UTM-tagged visit would automatically appear in reports.
Distinguished clicks from completed downloads and campaign attribution from proven recruiter conversion; allowed for analytics reporting delay.
Implementation and validation
Deployed shared site-wide code for document and outbound-link interactions, plus campaign landing events with constrained source, medium and campaign values.
Configured the Zaraz Analytics purpose, verified consent acceptance and rejection state, and checked traffic behavior during privacy tests.
Confirmed pageviews, a custom document-download event and campaign-attribution events in GA4. Initial Realtime delays were diagnosed before concluding delivery had failed.
Verified outcome
The project reached a functioning two-level analytics setup: Cloudflare Web Analytics displayed site traffic, and GA4 received pageviews and custom events via Zaraz. Campaign events were confirmed after reporting latency, and the site owner verified PDF access and consent choices. The website now has the instrumentation to evaluate recruiting outreach over time.
Measurement boundaries: There are no asserted increases in recruiter responses, hiring outcomes, conversion rates, or identified visitors. A separate automatic file_download event was not observed during final checks; we use the named custom download event for this workflow. Any future effectiveness claims should be supported by sufficient production data.
Leadership takeaway
This is a compact example of how I approach technology operations: translate a business question into measurable signals, choose a maintainable architecture, account for privacy and failure modes, and verify results across services rather than trusting configuration screens. The same discipline supports enterprise service delivery, infrastructure visibility, cross-platform integration, and operational automation.
Skills demonstrated: Cloudflare Pages, Web Analytics, Zaraz, GA4, consent configuration, JavaScript event instrumentation, UTM attribution, GitHub-based deployment, troubleshooting, and acceptance testing.
← Back to all case studies