Helium 10 does not rely on one data source. It blends with
SP-API (Amazon’s official API) which is used for seller-authorized metrics like orders, refunds, PPC, fees.
Proprietary scraping engines. Used for competitor insights like BSR, price, stock, reviews.
Because scraping is very sensitive to Amazon layout updates,Bot-detection rules, Region-specific HTML structures, IP throttling and Captcha challenges. Also,the scraped data is the part most likely to break.
You might see perfect PPC numbers in Adtomic (API-based), but missing review counts in Xray (scraping-based). Users assume the whole tool is broken, but only one data layer is actually affected.
If only competitor data is missing, the scraping layer is down. If PPC, Profit, or order numbers lag, the SP-API link is throttled or expired.
Related: Why does Helium 10 sometimes misfire or freeze on Amazon mobile view?
