Amazon Ads HTML Report

What it does

The original GGRN source Skill is named amazon-ads-analyzer; this directory entry names its offline report use case. It transforms seller-supplied Amazon advertising exports into a reviewable, self-contained HTML report. The workflow separates observed rows from calculated metrics, assumptions, and confidence notes. It is designed for offline ACOS, TACOS, ROAS, CTR, CVR, CPC, CPM, and break-even ACOS review, followed by controlled report sharing. It does not log in to Amazon, retrieve a seller's Ads Console or Business Reports, change bids, launch campaigns, or publish content.

When to use

Use it when a report already exists locally and a team needs a repeatable weekly or monthly readout, finance handoff, pre/post comparison, or shareable decision artifact. It is deliberately broader than a short search-term CSV PPC diagnosis: it summarizes account or campaign evidence together with unit economics. For current report retrieval, start with Amazon Ads Report Downloader; for an existing search-term CSV, use Amazon PPC Analyzer, then use this skill for the offline artifact.

Inputs

Provide an Amazon XLSX or CSV export, screenshot, or pasted metrics. Record site or marketplace, Seller or Vendor type, report name, date range and time zone, currency, campaign/SKU/ASIN scope, objective, target ACOS, price, COGS, FBA or fulfillment cost, referral fee, refunds or returns, and total sales. Mark each value as observed, derived, or assumed. Screenshots and pasted values need manual transcription and reconciliation.

Outputs

The source workflow names two local artifacts: report-data.json for normalized data and AMAZON-ADS-REPORT.html for the generated self-contained view. A useful report includes formula inputs, ACOS/TACOS/ROAS, efficiency metrics, break-even ACOS, date and marketplace scope, confidence labels, and notes for missing denominators. The HTML can be opened offline and shared only after redacting account IDs, ASINs, campaign names, and other sensitive details. This catalog entry has not generated these files.

Example workflow

Demonstration only; not run. The following de-identified values are invented for arithmetic demonstration, not an Amazon export, API response, or execution record:

seller_ads:
  marketplace: US
  period: 2026-08-01/2026-08-31
  impressions: 500000
  clicks: 10000
  orders: 400
  ad_sales_usd: 10000
  spend_usd: 2000
  total_sales_usd: 20000
unit_economics:
  price_usd: 40
  cogs_usd: 12
  fulfillment_usd: 7
  referral_fee_usd: 6
market_report_context:
  source: hypothetical market-side report context
  keyword: insulated bottle
  estimated_searches: 120000
  sponsored_traffic_share: 0.08

From those assumptions, ACOS is 2,000 / 10,000 = 20%, ROAS is 10,000 / 2,000 = 5.0, and TACOS is 2,000 / 20,000 = 10%. CTR is 10,000 / 500,000 = 2%, CVR is 400 / 10,000 = 4%, CPC is $2,000 / 10,000 = $0.20, and CPM is $2,000 / 500,000 * 1,000 = $4.00. Break-even ACOS is ($40 - $12 - $7 - $6) / $40 = 37.5%. The market context remains a separate annotation; it does not prove seller performance or fill a missing seller field. No report-data.json, HTML file, or market API response was produced here.

The source documents this command; it is reproduced for reference and was not run in this review:

python scripts/build_report.py --data report-data.json --out AMAZON-ADS-REPORT.html

Supported agents and setup

The pinned source names Claude Code, Codex, Cursor, Windsurf, Gemini, and Goose. Evidence reviewed on 2026-09-15: the immutable SKILL.md, its commit, the MIT LICENSE, and the skills.sh directory entry. The LICENSE also carries an Amazon non-affiliation and trademark notice. Installation is manual: review the pinned source, then follow the author's README. This page is source-reviewed, not install-tested, and exposes no install command.

Account, API, and permission requirements

The offline path needs local filesystem read/write and shell execution for the documented report script. It does not require an Amazon account or API key in this entry. If an operator obtained an export from an authenticated seller account, that authentication happened outside the skill. Any Ecommerce Data API call has separate account and credential requirements and must be approved independently.

Limits and human review boundary

Ratios are meaningful only when date range, currency, marketplace, attribution window, and scope align. ACOS uses ad spend divided by ad-attributed sales; TACOS uses ad spend divided by total sales; break-even ACOS depends on which variable costs, refunds, taxes, and discounts are included. Seller and Vendor reports may use different fields, while reporting lag and missing denominators can change a decision. Screenshot or pasted data is not automatically validated. Confidence is a traceability label, not statistical proof or a security verification. Review calculations and redact sensitive fields before sharing; do not infer guaranteed profitability or authorize bid changes from the HTML alone.

Pair with Ecommerce Data API

When separately approved, amazon.keywords.research can add keyword demand, growth, competition, conversion, or PPC context; amazon.traffic.sources can add traffic-source composition; and amazon.keywords.traffic-stats can add aggregate traffic keyword statistics for an ASIN. See the canonical keyword research docs and traffic source docs before using those supplementary calls. For that optional live context, create an Ecommerce Data API key; the key is not needed for the offline report. These are market-side context interfaces. They do not read the seller's private advertising console, seller advertising reports, or Business Reports. Keep API response time, marketplace, and source beside the seller export, and never treat a market estimate as actual ad performance.