ecommerce-analysis

ecommerce-analysis is a skill for Claude Code from surendranb/google-analytics-mcp. It costs 22 tokens per session (622 once invoked), scanned A, original, MIT.

A guide to analysing online-shop activity in Google Analytics 4, including revenue, purchases, average order value, and the steps from viewing a product to buying it.

In plain words
What is it for?
Use it to report sales results, calculate conversion and average order value, and find drop-offs between product views, carts, checkout, and purchases.
Why use it?
It shows which standard GA4 field names to use and helps reveal where shoppers leave the purchase process.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the google-analytics-mcp plugin — 16 skills, 1 MCP server shipped together

Good fit Use it to report sales results, calculate conversion and average order value…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/surendranb/google-analytics-mcp/ecommerce-analysis
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add surendranb/google-analytics-mcp --skill ecommerce-analysis
Clone the repo
git clone --depth 1 https://github.com/surendranb/google-analytics-mcp

Made for: Claude Code.

Or install google-analytics-mcp, the plugin that ships this one along with the rest of its 16 skills, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ecommerce-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/surendranb/google-analytics-mcp/ecommerce-analysis.svg)](https://agentmods.dev/skills/surendranb/google-analytics-mcp/ecommerce-analysis)
Your own site
<a href="https://agentmods.dev/skills/surendranb/google-analytics-mcp/ecommerce-analysis"><img src="https://agentmods.dev/badge/skills/surendranb/google-analytics-mcp/ecommerce-analysis.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 622 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.00622
Opus 5 $0.00011 $0.00311
Sonnet 5 $0.00004 $0.00124
Haiku 4.5 $0.00002 $0.00062

Measured 7d ago against content hash d3ec2ccb84c9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

ecommerce-analysis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/ecommerce-analysis/SKILL.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ecommerce Analysis

Revenue, conversion rate, AOV, and funnel drop-off using GA4 ecommerce events.

When to use

  • You have purchase, add_to_cart, begin_checkout events in GA4
  • You want to measure revenue, conversion rate, or average order value
  • You want to find where users drop off in the purchase funnel

Correct metric and dimension names

GA4 ecommerce uses specific API names — do not guess:

Concept GA4 API name
Revenue purchaseRevenue
Transactions ecommercePurchases
AOV averagePurchaseRevenue
Add to cart addToCarts
Checkout started checkouts
Cart-to-view rate cartToViewRate
Purchase-to-view rate purchaseToViewRate
Item views itemsViewed
Item revenue itemRevenue
Items purchased itemsPurchased
Product name itemName
Product category itemCategory
Transaction ID transactionId

Step 1 — Revenue overview

dimensions: ["date"]
metrics: ["ecommercePurchases", "purchaseRevenue", "averagePurchaseRevenue"]
date_range: last 30 days
order_by: date ASC

Step 2 — Funnel: views → cart → checkout → purchase

dimensions: ["sessionDefaultChannelGroup"]
metrics: ["itemsViewed", "addToCarts", "checkouts", "ecommercePurchases",
          "cartToViewRate", "purchaseToViewRate"]
date_range: last 30 days
order_by: ecommercePurchases DESC

Drop-off between stages = 1 - (next_stage / current_stage). The biggest drop-off is the highest-leverage fix.

Step 3 — Top products

dimensions: ["itemName", "itemCategory"]
metrics: ["itemsViewed", "addToCarts", "itemsPurchased", "itemRevenue"]
date_range: last 30 days
order_by: itemRevenue DESC

Step 4 — Revenue by channel

dimensions: ["sessionDefaultChannelGroup"]
metrics: ["ecommercePurchases", "purchaseRevenue", "averagePurchaseRevenue"]
date_range: last 30 days
order_by: purchaseRevenue DESC

Incompatible combinations to avoid

  • itemId or itemSku cannot be combined with session-level metrics
  • ecommercePurchases cannot be combined with eventCount in the same query
  • Use separate queries for item-level and session-level analysis

Read the full file on GitHub · 79 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 79 lines · 22 tokens per session scan A d3ec2ccb84c9

Subscribe to this mod's changes

ecommerce-analysis is a skill published in the GitHub repository surendranb/google-analytics-mcp (241 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 622 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

seo-ecommerce

E-commerce SEO analysis: Google Shopping visibility, Amazon marketplace intelligence, product schema validation, competitor pricing analysis, and marketplace keyword gaps. Combines on-page product SEO with marketplace data from DataForSEO Merchant API. Use when user says "ecommerce SEO", "product SEO", "Google…

georgekhananaev/claude-skills-vault · 89 tokens

ecommerce-funnel-optimizer

This skill should be used when the user asks to "build an e-commerce ad funnel", "optimize retargeting windows", "set ROAS targets by funnel stage", "recover abandoned carts with ads", or mentions "dynamic product ads", "Advantage+ Catalog Ads", or "seasonal ad strategy". Do NOT use for: single-platform campaign…

Ad-Superpowers/ad-superpowers-plugin · 106 tokens

google-credentials

Configure local Google Search Console and GA4 credentials for SEO Google Suite. Use when the user asks to connect, configure, add, or verify GSC or GA4 credentials.

powehi-eu/google-suite-seo-mcp · 39 tokens

tracking-shopify

Use when the platform is Shopify or the run needs the Shopify-specific schema, sync, install, or verification branch.

jtrackingai/analytics-tracking-automation · 27 tokens

seo-data

Direct access to Google Search Console, Google Analytics 4, and Bing Webmaster Tools data via OAuth/API key. Use whenever the user asks SEO, search performance, organic traffic, ranking, impressions, clicks, CTR, conversions, traffic source, landing page, or analytics questions and wants real numbers from their own…

anthonylee991/seo-data · 140 tokens

google-seo-audit

Use Google Search Console, GA4, and CrUX evidence for SEO audits from Codex.

powehi-eu/google-suite-seo-mcp · 25 tokens