Diagnose a conversion problem with Claude

This is the read-only server. Every tool here carries the workflow:read scope, so you can hand the whole thing to Claude without thinking about blast radius.

Start with whether the numbers are real

The most expensive analysis is a confident one built on broken tracking.

Run a tracking health check for shop your-store.myshopify.com before anything else.

gemboss.get_tracking_health audits the pipeline itself: missing data, broken stitching between purchases and sessions, thin COGS coverage. If it flags something, fix that first. Everything downstream inherits the fault.

Then the funnel

Read the funnel and conversion metrics, then tell me the single largest drop and what you would look at next.

gemboss.get_metrics is the right first call for any performance question: funnel, conversion rate, AOV, per-section engagement, per-variant conversion.

Then cut it until the problem has a shape

A useful habit is to ask for the cut and the conclusion together:

Break the funnel down by device and by channel. Tell me which combination is worst, and whether the gap is big enough to be worth acting on.

Beyond the funnel

Three tools answer questions the funnel cannot:

• gemboss.get_behavior_signals gives top products viewed per SKU, on-site search terms, and video engagement. On-site search is the cheapest demand signal you own.
• gemboss.get_search_performance pulls organic queries, clicks, impressions and position from Google Search Console.
• gemboss.get_market_signals reports tracked competitors' price moves and the price band of your niche.

Get to a hypothesis

Based on all of that, give me ranked CRO hypotheses with the reasoning, and say which one you would test first.

gemboss.get_recommendations returns ranked hypotheses, section-aware when you give it a job id. Then take the winner to a theme edit, which is where the read-only server hands over to the build one.

Next

• Build an offer
• Edit a theme safely