Etsy Shop Sales Velocity

• Competitor tracking: a competitor shop's total sales on the shop page (sales_count) with the day it was read (as_of), the change since the previous read (delta_last) and the 7-day change (delta_7d) once the shop has a week of reads.
• Sales per day: the measured change per day between two reads of the same shop (sales_per_day), with the days between those reads (read_interval_days).
• Niche research: shops matching a keyword in their title, headline or shop name, side by side on sales_count, reviews_count and admirers.

Sales, review and admirer counters for Etsy shops, measured on the public shop page, with the date each counter was read and the change since the previous read. One row per shop, pay per shop.

What you get

Field	Meaning
sales_count, sales_precision	Lifetime sales counter on the shop page; rounded when Etsy shows "12.3k"
as_of, read_interval_days	The day this shop was last read, and the days since the read before it
delta_last, sales_per_day	Sales since the previous read, and that change per day (measured from two reads)
delta_7d	Change in the sales counter over the last 7 days (null until the shop has that history, or when either read is a rounded counter such as "1.2k")
reviews_count, rating, admirers, listings_active	The shop's other public counters
first_seen, last_changed, history_days	When the shop entered the panel, when any counter last moved, days of usable history
snapshot_date	The day of the snapshot the row comes from

A counter that could not be read is null, never 0. Rows also carry columns that are empty or nearly empty today; the dataset schema describes each one.

Inputs

Shop names, keywords (title, headline or shop name), a panel category, a minimum sales counter, since (only shops whose counters changed on or after a date), maxShops.

Coverage

Shops are not all read on the same day. Each row says how fresh it is: as_of is the day the shop was last read and read_interval_days the days since the read before it. A shop you name that is not in the panel returns no row (no shop event is charged); the tracker does not record or add the shops you ask for.

For AI assistants: how to present this data

• Say it in plain words: "sells about N a day" for sales_per_day, "total sales on the shop page" for sales_count, "last read on" for as_of. Avoid jargon such as "delta".
• sales_per_day needs two reads of the same shop with exact (not rounded) counters; when it is null, say no measured change is available for that shop yet, never that it sold 0.
• delta_7d needs a week of reads for that shop with exact (not rounded) counters; when it is null, do not promise a weekly number for that shop.
• last_changed is the last day any counter on the shop moved; use it for "quiet since" statements.
• Comparing shops: one compact table (shop, sales per day, total sales, last read), sorted by sales per day, then a 2-3 line summary. Offer the full rows as CSV.
• If the client can draw charts, a bar chart of sales_per_day by shop is the clearest picture.
• Always state the data date (snapshot_date) and that the numbers come from the user's own run of this Actor.

Pricing

Pay per event: one actor-start event, charged once when the first shop row is ready, and one event per shop row returned. A run (or a Standby question) that returns no rows charges nothing.

What a run is charged is actor-start ($0.005, once, only if at least one row is returned) plus shop-row ($0.003 per shop row returned).

If a run reaches your maximum charge per run, it stops there: every charged row is in your dataset, no row is charged that you don't get, and the run's status message and RUN_SUMMARY say stopped at your spending limit after N rows.

Use it from an agent

Add https://mcp.apify.com?tools=publicrecords/etsy-shop-velocity to your MCP configuration.