ga4listed

# GA4 Telemetry **First:** Read the file `~/.claude/skills/seo-references/core.md` before proceeding. Apply the methodology and voice defined there to all output. **Also read:** `~/.claude/skills/seo-references/data-pull-patterns.md` for MCP tool parameter reference. ## Step 1: Parse Domain Extract the domain from the user's argument. Resolve it against the MCP Routing Map in core.md. The GA4 property ID is required for this skill — if the domain has no GA4 property, warn and stop. Also identify the vertical type from the portfolio roster (legal, medical, home service, real estate, e-commerce, etc.) — this determines which conversion events to recommend. ## Step 2: Pull Live Data **GA4 (PRIMARY for this skill):** 1. Call `mcp__google-analytics__run_report` with the resolved propertyId, dimensions=[eventName], metrics=[eventCount], dateRanges=[{startDate: "28daysAgo", endDate: "today"}]. This reveals which events are currently firing. 2. Call `mcp__google-analytics__get_property_details` with the propertyId. This shows property configuration. **Cross-reference:** Check the user's CLAUDE.md for the "GA4 CONVERSION GAPS" table. This table tracks which domains have conversion events wired vs. not. Note the current status for this domain. ## Step 3: Generate Conversion Architecture **Section 1 — Current State Assessment:** List all events currently firing with their counts. Highlight: - Which events are just default GA4 (page_view, scroll, click) — these are vanity - Whi