GA4: mark contact_cta_click a key event + record the UI path

[pftg]

Done

contact_cta_click is now a GA4 key event on property 328508492 (Home Page - GA4). Verified in the Key events list: it carries the same filled star as page_view and rise_spent_time, distinct from unmarked purchase.

This closes the last item that had been sitting on Paul's desk.

The "needs Paul" claim was wrong

The checklist said this was permanently his because "the GA4 Admin API is not exposed to this session." The Data API genuinely can't mark key events — but the task never needed an API:

Admin → Data display → Events → Create event → "Create with code" takes an event name plus a Mark as key event toggle, and needs no already-received data.

Third instance in one day of asserting a capability limit instead of checking it (the others: estimating instead of querying GA, and "agents have no LI access"). The rule now generalises past tools to interfaces: exhaust the UI before declaring something blocked.

Why it looked blocked

The star on the Events list only appears for events received in the last 28 days. contact_cta_click has fired zero times — it shipped the same day in PR #474.

Before touching the UI I verified the handler is live and correct in the deployed HTML:

document.addEventListener("click", function(e){
  var t = e.target && e.target.closest ? e.target.closest('a[href*="/contact-us"]') : null;
  if(!t) return;
  gtag("event","contact_cta_click",{link_url:t.getAttribute("href")||"",transport_type:"beacon"})
},{passive:!0})

So the metric reads zero because nobody has clicked a contact CTA yet, not because instrumentation is broken.

Two traps in that dialog

• It pre-selects a $1 default key-event value. Left alone, every contact click would book phantom revenue. Set to "Don't set a default key event value".
• Counting method left at GA4's recommended "Once per event" — per-event preserves the raw signal, and reporting can dedupe to sessions later, but it cannot un-dedupe.

Deliberately not done

• No synthetic click to unblock the star. In a conversion series whose true count is zero, a QA-origin first data point is undeletable and reads as a real conversion forever — the same de-fabrication standard applied to the testimonials and to icp_profile_views earlier today.
• Did not un-mark page_view, which still pollutes keyEvents (4,063 of them are page views, so a real contact conversion would currently be buried). That changes how a headline metric reads and belongs to 2608 Phase 0.1, not to this request. Flagged in analytics-access.md rather than silently skipped.

Gates

• bin/hugo-build — green
• bin/qtest --changed — 34 runs, 53 screenshots compared, 0 failures (the template edit is a Hugo comment, so no rendered change — verified, not assumed)
• bin/rake test:unit — 279 runs, 6132 assertions, 0 failures
• /okf:validate .okf --strict — conformant

🤖 Generated with Claude Code

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: dbc91652-1826-4735-8b23-433947296016

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}