TikTok Shop Trending Products & Sales Velocity avatar

TikTok Shop Trending Products & Sales Velocity

Pricing

from $9.00 / 1,000 tracked product results

Go to Apify Store
TikTok Shop Trending Products & Sales Velocity

TikTok Shop Trending Products & Sales Velocity

Track TikTok Shop products by keyword or URL. Measure sold-count growth, estimated daily sales, price changes, review growth, and opportunity-rank movement across recurring runs. Export verified results to JSON, CSV, Excel, or API—no external data provider required.

Pricing

from $9.00 / 1,000 tracked product results

Rating

0.0

(0)

Developer

Scout

Scout

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

21 days ago

Last modified

Share

Track TikTok Shop product trends, sold-count growth, estimated daily sales, price changes, review growth, and opportunity-rank movement across recurring observations. Use this TikTok Shop trend tracker to separate current bestsellers from products that are actually gaining momentum.

Search a niche or monitor specific product URLs. The first run creates a baseline; a later run with the same tracker scope measures changes only after the configured minimum interval. Immediate repeats return TOO_SOON with movement fields null, preventing tiny live ticks from being presented as sales velocity.

One paid result = one current tracked product row. Pricing is $0.009 per product ($9 per 1,000), with platform usage included.

What can you do with it?

  • Build daily TikTok Shop trend and winning-product watchlists.
  • Measure public sold-count changes and estimate units/day.
  • Detect price changes, review growth, and opportunity-rank movement.
  • Distinguish a high lifetime sold count from current momentum.
  • Monitor a niche, selected URLs, or both through API, schedules, webhooks, Make, Zapier, and n8n.

What one result contains

  • Current product identity, URL, image, seller, price, discount, sold count, rating, and reviews
  • Product viralScore plus tracking-aware trendScore and readable signals
  • Tracking group, state, confidence, observation count, and comparison window
  • Previous and current sold count, reviews, price, and opportunity rank
  • salesDelta, estimatedUnitsPerDay, reviewDelta, priceChange, and rankChange when measured
  • Source provenance and quality state

Quick start

{
"searchQueries": ["portable car jump starter"],
"productUrls": [],
"trackerName": "us-jump-starter-daily",
"trackingEnabled": true,
"resetHistory": false,
"minimumTrackingHours": 6,
"retainMissingDays": 30,
"region": "US",
"maxProductsPerQuery": 10,
"sortBy": "TREND_SCORE",
"maxConcurrency": 2,
"includeRawData": false,
"includeSearchFallbacks": false
}

Keep the tracker name, queries, URLs, region, and limits identical across runs. Daily schedules are recommended.

Real baseline result

This abbreviated result was captured from the public US TikTok Shop on August 26, 2026. It was the first observation, so no velocity claim was made.

{
"productId": "1730749598688448629",
"productName": "Hieha 4000A Jump Starter with 150 PSI Air Compressor",
"price": 45.99,
"salesTotal": 171935,
"rating": 4.5,
"reviewCount": 17684,
"viralScore": 87.6,
"trendScore": 56.9,
"trackingState": "BASELINE",
"trendConfidence": "BASELINE",
"salesDelta": null,
"estimatedUnitsPerDay": null,
"rankChange": null,
"qualityState": "verified_success"
}

The large sold count proves historical demand, not current growth. A later sufficiently spaced run is required for measured momentum.

Tracking states

StateMeaning
BASELINEFirst comparable observation. Movement fields are null.
TOO_SOONPrevious observation is newer than minimumTrackingHours. Movement fields remain null and the original anchor is preserved.
MEASUREDThe tracking window is long enough to calculate public changes.

Do not launch parallel or immediate repeat runs to infer momentum. A second scrape after a few minutes is directional noise, not defensible daily velocity.

Trend score

trendScore combines current product strength with measured movement when available. Baseline products can still be ranked as candidates, but the output explicitly separates public demand from tracked acceleration. Scores are research signals—not sales forecasts.

Owned extraction and private history

The Actor requests public TikTok Shop pages directly, parses embedded and network JSON, and uses a bounded Playwright fallback. It stores tracker snapshots in the caller's private Apify key-value store and does not call another Actor or external TikTok data API.

Pricing

  • Tracked product result: $0.009 each ($9 per 1,000)
  • Actor start: $0.00005
  • Platform usage: included
  • Nested external Actors/data APIs: none

Each current product row is billable even on a baseline run because the Actor still discovers, validates, normalizes, scores, and stores the product observation.

FAQ

How many runs do I need for sales velocity?

At least two comparable observations separated by minimumTrackingHours. Daily observations are more defensible than short-interval checks.

Does sold count equal sales in the last 30 days?

No. salesTotal is the public accumulated counter. salesDelta is the change between valid observations; estimatedUnitsPerDay annualizes that observed change to a daily rate.

Why are delta fields null?

The product is new to the tracker, the repeat was too soon, a prior value was unavailable, or TikTok's counter moved backward/inconsistently.

Can I monitor direct product URLs?

Yes. Add URLs alongside or instead of keyword queries, and reuse the exact scope on later runs.

Use Product & Viral Radar when you need only a current snapshot. Use this Actor when recurring comparison is the goal.

NexaScout TikTok Shop Intelligence Suite

Limitations and responsible use

  • US TikTok Shop only in this release
  • Public counters may be delayed, rounded, region-specific, or changed by TikTok
  • Missing products can reflect extraction availability, not confirmed delisting
  • Use public data lawfully; do not defeat access controls or collect private information

For support, include the run ID, tracker name, complete input scope, failed stage, and trackingState. Never post credentials, cookies, or tokens.