Analyze GA4 Landing Pages With Claude Code and Soku CLI
Let Claude Code query GA4 through Soku CLI, rank landing pages by traffic and conversion behavior, find paid-traffic leaks, and save an evidence-backed CRO shortlist.
Best for
Growth and CRO teams that want a reproducible GA4 investigation in the same workspace where they write briefs, experiments, and landing-page code.
Access mode
Read-only analysis
No connected account changes.
The prompt
Read https://soku.ai/cli/skill.md, connect Claude Code to my Soku workspace, and use the GA4 commands for a read-only landing-page analysis covering the last 30 days. Segment paid and organic acquisition, rank high-traffic pages with weak engagement or conversion, and save five CRO opportunities with the exact metrics behind each one. Safety boundary: do not change connected accounts or publish content. Use read commands only, and return proposed actions for a human to review separately.
Paste this into Claude Code, Codex, Cursor, or another shell-based agent. It will pause when browser approval or a human review is required.
What you will get
Claude Code produces a ranked CRO shortlist connecting landing-page traffic, engagement, conversion behavior, and acquisition source without changing GA4 configuration.
- A source-segmented landing-page performance table
- Five prioritized CRO opportunities with evidence and experiment ideas
Before you start
- A GA4 property granted to the selected Soku workspace
- Known primary conversion events or a willingness to label missing conversion mapping
Works with
Run it with Soku CLI
- 1
Discover the GA4 property
List properties and confirm the correct one before querying any report.
soku ga4 list-properties - 2
Pull the landing-page baseline
Retrieve top pages and a custom report that includes source and conversion metrics for the same date range.
soku ga4 list-top-pages --property-id <property_id> --date-start <start> --date-end <end> --limit 50 - 3
Rank opportunities
Prioritize pages with enough traffic to matter and explain when conversion mapping is incomplete.
- 4
Save the CRO shortlist
Write one evidence block and one proposed experiment for each selected page.
Safety boundary
Read onlyThis workflow only reads GA4 reports. It must not edit events, audiences, attribution, or property settings, and it must label conclusions as uncertain when conversion mapping is missing.
Related Soku skills: soku-ga4, soku-landing-page-spy
More Agent Workflows use cases
Audit Google Ads With Claude Code and Soku CLI
Give Claude Code read-only access to Google Ads through Soku CLI, inspect tracking, search terms, creative coverage, budgets, and Quality Score, then save an evidence-backed account audit.
Review Meta Ads Performance With Codex and Soku CLI
Connect Codex to Meta Ads reporting through Soku CLI, compare campaign and creative performance, identify fatigue and CPA changes, and return a read-only optimization brief with evidence.
Build a Weekly Cross-Channel Ads Report With an AI Agent
Use a local AI agent and Soku CLI to combine Google Ads, Meta Ads, and GA4 into one weekly report that explains changes, flags anomalies, and preserves the reporting window.
Analyze a PostHog Funnel With Codex and Soku CLI
Give Codex allowlisted, read-only PostHog access through Soku CLI, inspect the live project schema, measure a conversion funnel, and produce a drop-off diagnosis without exposing provider keys.
