Decodo's Google Trends product is a named scrape target inside Web Scraping API. The product page (checked 27 Aug 2026) posts to https://scraper-api.decodo.com/v2/scrape with target google_trends_explore, query, and Basic auth (base64 credentials). The SERP examples repo lists that target next to google_search and shopping. Output is HTML or structured JSON. Billing is successful scrapes. Trends API does not have targets. It has source strings. The list is on the sources reference.
target is not source
target: google_trends_explore tells Decodo which parser to run. source: google search tells Trends API which series to return. Same English word, two contracts.
Decodo's page says the scraper is now part of Web Scraping API, not a standalone Trends SKU. The caller still owns whatever schema that target emits after the next Google change. Trends API owns the envelope. Parse the body string. Rows are date plus value.
Formerly Smartproxy
Public pages still say "formerly smartproxy.com." Gists that post to scraper-api.smartproxy.com are the old host. Recheck Decodo's Trends product page for the live URL. This article does not copy a per-thousand scrape price.
Trends API auth is a Bearer key on POST https://api.trendsapi.ai/api. There is no proxy username.
Structured scrape, still Explore
Samples include search_type web_search and a date pair. That is Google Explore. It is not get_top_trends with type Google Trends. It is not source=youtube keyword history.
{
"mode": "get_time_series",
"source": "google search",
"keyword": "pizza"
}
keyword here is Trends API. Decodo's field is query. Do not mix the names.
One POST that is not a scrape target
Keep Decodo when SERP credits are already budgeted and Explore is one more target. Leave when the same function must accept steam or wikipedia tomorrow. A URL-through-zone fetch is Bright Data. A URL-plus-selectors fetch is ScrapingBee.