TikTok Trending Creator Insights Scraper Across Every Country

TikTok Trending Creator Scraper — Creators, Market Rollups and Videos

TikTok Trending Creator Insights Scraper Across Every Country sweeps TikTok's public Creative Center trending board across up to 27 country markets and three trend windows in one run, and returns typed JSON creator rows — each one carrying the hashtag that surfaced it, its rank inside that hashtag, and every market it charted in. Unlike scraping frameworks that hand you raw HTML, this Actor returns typed JSON ready for your model, your database, or your pipeline without any parsing. This guide covers every input and output field, the platform's real result ceiling, and how teams deploy the sweep for influencer discovery, trend monitoring, and multi-market rollups.

---

🧭 What does TikTok Trending Creator Insights Scraper Across Every Country do?

It queries TikTok's public Creative Center trending board once per market × window slice. Each slice returns three trending hashtags, and each hashtag carries the three creators driving it — so every creator row already knows the hashtag that surfaced it and its rank inside that hashtag, at no extra request. No TikTok account, login, cookies or API key is required — every surface this Actor reads (ads.tiktok.com/creative/creativeCenter, www.tiktok.com profile and embed pages) is public.

• Sweeps 1 to 27 country markets in a single run, or a single fallback country
• Charts each market over 7, 30 and/or 90-day trend windows
• De-duplicates creators on their numeric TikTok user ID across the whole sweep
• Records every market and hashtag each creator charted in, with rank
• Flags markets that fall back to another country's board instead of silently mixing data
• Optionally enriches each creator with exact profile totals and real per-video stats
• Writes a per-market coverage rollup to a separate dataset and a key-value record

---

⚡ Features & Capabilities

Three things define what this Actor is built to do: the multi-market sweep itself, the honesty of what it reports back, and the depth of optional enrichment.

Core features

• Multi-market, multi-window sweep in one run — markets[], sweepAllMarkets, and periods[] control the market × window matrix; each slice is fetched independently and merged.
• Cross-sweep de-duplication — creators are merged on ttUID (falling back to handle) so the same creator charted in multiple markets or windows produces one row, not several.
• Free hashtag attribution — every creator row carries sourceHashtag, sourceHashtagId, sourceHashtagRank, creatorRankInHashtag, sourceHashtagViews and sourceHashtagPosts because creators arrive nested inside the hashtag payload.
• Market honesty fields — marketSupported, marketFallbackApplied, requestedMarket and resolvedMarket tell you when a market silently served another country's board instead of pretending the data is local.
• Three enrichment depths — board (fastest, board fields only), profile (adds exact liked_cnt total), and full (adds a real per-video items[] array with views, likes and timestamps).
• Client-side filtering and ordering — followerCount and sortBy operate on the merged, de-duplicated sweep, because TikTok's own board exposes neither a server-side filter nor a server-side sort.
• Per-market coverage rollup — a separate market-coverage dataset and a MARKET_COVERAGE key-value record report creators found, rank distribution, and whether each market returned data at all.

How this scraper compares to other TikTok trending-creator tools

No live Apify Store listing for a directly comparable multi-market TikTok trending-creator sweep was available to cite as of the date this was written (2026-08-04), so the table below compares this Actor's documented behavior against the generic pattern most single-country trending-board tools default to — it does not name or benchmark a specific competing product.

Feature	This Actor	Typical single-country trending scraper
Market coverage per run	Up to 27 markets in one run	One market per run
Cross-market de-duplication	Built in, merges on numeric user ID	Not applicable — one market only
Hashtag attribution	Included on every row at no extra request	Varies by tool
Mirrored-board transparency	marketSupported / marketFallbackApplied flag every fallback	Not applicable
Output format	Typed JSON, stable field names	Varies by tool

If your use case is feeding structured data to an LLM, the output format row is the decision-maker — HTML parsing inside an agent loop is a reliability failure mode, not a feature. The rest of the table is about how much of the market × window matrix a single run actually covers.

When another tool might suit you better

If you need continuous, sub-hourly tracking of one creator's post-by-post performance rather than a periodic cross-market discovery sweep, a dedicated single-profile monitoring tool that polls one account continuously is a better fit than re-running a multi-market board sweep on a schedule. This Actor is built for breadth — discovering who is trending across many markets and windows — not for tight-interval tracking of a single handle. For that job, see the profile- and video-level scraper named below.

TikTok Trending Creator Insights Scraper Across Every Country within the Scrapio data stack

This Actor covers trending creators and per-market coverage. For comments, replies, followers, hashtag videos, music and AI sentiment on a specific TikTok profile, use TikTok Data Scraper: Comments, Replies & AI Sentiment. For TikTok Shop products and seller/business profiles, use TikTok Shop Data Scraper & Seller Profile Scraper. Together the three cover discovery, profile depth, and commerce.

---

Why do developers and data teams scrape TikTok's trending board?

🏢 Influencer marketing and talent agencies

Agencies use the sweep to build a shortlist of trending creators per market before outreach. A run over markets returns handle, nick_name, follower_cnt, tt_link and the sourceHashtag that surfaced each creator, so a campaign brief can be built without opening TikTok manually for each country. marketsChartedIn and marketCount tell you which creators are trending in more than one target market, which is the signal worth prioritizing for a multi-country campaign.

📊 AI training data and RAG indexing

The fields with the most consistent structure across every row — handle, nick_name, sourceHashtag, follower_cnt, engagementRate and marketsChartedIn — are typed primitives requiring no normalization before indexing. TikTok's trending board does not publish creator bios or video captions, so the value here is structured attribution rather than long-form text: use sourceHashtag plus chartEntries[] to enrich a RAG index with "which creators are trending under which topic, where, and when," and use the numeric fields (follower_cnt, engagementRate, sourceHashtagViews) as consistent training features across the whole dataset.

📱 Competitive and market intelligence

Track sourceHashtag, sourceHashtagRank and sourceHashtagViews over repeated scheduled runs to see which topics are pulling creator attention in a given market this week versus last. marketFallbackApplied and marketSupported matter here too — they tell you which of your tracked markets are genuinely reporting local data versus mirroring another country's board.

🔬 Research and academic use

The Actor returns only publicly accessible board, profile and video data — no private accounts, no authenticated surfaces. That makes it suitable for building a public-data research dataset on cross-market trend dynamics, using periodDays and chartEntries[] to compare how the same hashtag performs across the 7/30/90-day windows.

🎥 Product and SaaS development

Teams building a creator-discovery or influencer-monitoring product on top of this data get a stable JSON contract — rowType: "creator" for real rows, rowType: "market_error" for uncharged failure rows — so a downstream pipeline can filter cleanly on rowType instead of guessing at malformed rows.

---

🍚 Input Parameters

Every field this Actor accepts, read directly from .actor/actor.json. countryCode and sortBy are the two schema-required fields (the schema requires sortBy even though it carries a default).

Parameter	Required	Type	Description	Example Value
markets	No	array of string (enum, default [])	Pick every country board to sweep. Empty falls back to countryCode. 27 of 28 codes return their own board; RU mirrors the US board.	["US", "GB", "MX", "BR", "DE"]
sweepAllMarkets	No	boolean (default false)	Overrides markets and countryCode; runs every supported market — 27 real boards (RU skipped as a US mirror) × the selected windows, 9 creator rows per slice.	true
countryCode	Yes	string enum (default "US")	Used when markets is empty and sweepAllMarkets is off. 28 codes selectable, including AR, CO, MX and ZA.	"US"
periods	No	array of "7" / "30" / "90" (default ["7"])	Trend windows in days. Upstream supports exactly these three values.	["7", "30"]
enrichmentLevel	No	string enum: board, profile, full (default "full")	board = board fields only (liked_cnt null, items[] empty). profile adds the exact total-likes figure. full also fills items[] with real per-video views, likes and timestamps.	"full"
maxVideosPerCreator	No	integer, min 0, max 12 (default 3)	Only used at full depth. Each video costs one extra request. The creator video feed returns at most 13 IDs and some accounts return none.	3
requestDelaySeconds	No	number, min 0, max 15 (default 2.5)	Delay between www.tiktok.com profile/video requests. They answer HTTP 503 when hammered; 2.5 s is documented as stable.	2.5
followerCount	No	string enum: 10k-100k, 100k-1m, 1m-10m, >10m (no default)	Client-side follower-bucket filter over the merged sweep, applied before anything is charged. Leave empty for no filter.	"1m-10m"
sortBy	Yes	string enum: follower, engagement, popularity (default "follower")	Orders the merged, de-duplicated set locally — the board itself has no sort parameter. engagement needs full depth.	"follower"
maxItems	No	integer, min 1, max 729 (default 10)	Hard ceiling of the surface: 3 hashtags × 3 creators = 9 rows per market/window slice, no page 2. 27 markets × 3 windows = 729 rows before de-duplication.	50
includeChartEntries	No	boolean (default true)	Adds chartEntries[] to every row — one entry per market/window/hashtag the creator charted in, with its rank.	true
writeMarketRollup	No	boolean (default true)	Writes the per-market coverage rollup to the MARKET_COVERAGE key-value record and an uncharged market-coverage dataset.	true
proxyConfiguration	No	object (Apify proxy editor)	Optional. Your selection is used exactly as given — this Actor never silently upgrades you to a residential group. Only affects profile/video enrichment; the board sweep itself needs no proxy.	{"useApifyProxy": false}

Input example

{
  "markets": ["US", "GB", "MX", "BR", "DE"],
  "sweepAllMarkets": false,
  "countryCode": "US",
  "periods": ["7", "30"],
  "enrichmentLevel": "full",
  "maxVideosPerCreator": 3,
  "requestDelaySeconds": 2.5,
  "followerCount": "",
  "sortBy": "follower",
  "maxItems": 50,
  "includeChartEntries": true,
  "writeMarketRollup": true,
  "proxyConfiguration": { "useApifyProxy": false }
}

Supported market and window selections

There is no URL input on this Actor — selection happens entirely through market codes and window values, resolved in this order: sweepAllMarkets > markets[] > countryCode.

• Single-market fallback — leave markets empty and set countryCode: {"countryCode": "MX", "sortBy": "follower"} sweeps only Mexico's board.
• Named multi-market list — {"markets": ["US", "GB", "MX", "BR", "DE"], "periods": ["7", "30"], "sortBy": "follower"} sweeps five markets over two windows in one run.
• Full sweep — {"sweepAllMarkets": true, "periods": ["7", "30", "90"], "sortBy": "popularity"} sweeps all 27 real markets over all three windows — the largest single run this Actor supports.

---

📦 Output Format

Output is typed, normalized JSON with a stable field set across runs — export it as JSON, CSV, Excel, or any other format the Apify platform's dataset export supports, or pull it programmatically over the Apify API. Charged creator rows carry rowType: "creator"; failed market/window slices are recorded separately as uncharged rows with rowType: "market_error" — filter on rowType == "creator" to keep only billed results.

Output for a creator row

{
  "tcm_id": "7506213105165369387",
  "user_id": "6663294979903422470",
  "nick_name": "ESPN",
  "avatar_url": "https://p19-common-sign.tiktokcdn.com/tos-maliva-avt-0068/example~tplv-tiktokx-cropcenter.jpeg",
  "country_code": "US",
  "follower_cnt": 60053787,
  "liked_cnt": 5754977138,
  "tt_link": "https://www.tiktok.com/@espn",
  "tcm_link": null,
  "items": [
    {
      "item_id": "7663895908026912023",
      "cover_url": "https://p16-common-sign.tiktokcdn.com/tos-no1a-p-0037-no/example~tplv-photomode-zoomcover.jpeg",
      "tt_link": "https://www.tiktok.com/@espn/video/7663895908026912023",
      "vv": 6900000,
      "liked_cnt": 1600000,
      "create_time": 1784649563
    }
  ],
  "rowType": "creator",
  "handle": "espn",
  "marketsChartedIn": ["US"],
  "marketCount": 1,
  "requestedMarketsChartedIn": ["US", "RU"],
  "firstSeenMarket": "US",
  "firstSeenPeriodDays": 7,
  "requestedMarket": "US",
  "resolvedMarket": "US",
  "marketSupported": true,
  "marketFallbackApplied": false,
  "periodDays": 7,
  "periodsChartedIn": [7],
  "sourceHashtag": "sixers",
  "sourceHashtagId": "191352",
  "sourceHashtagRank": 3,
  "creatorRankInHashtag": 2,
  "sourceHashtagViews": 88347771,
  "sourceHashtagPosts": 8669,
  "profileFetched": true,
  "profileStatus": "ok",
  "profile_follower_cnt": 60053805,
  "profile_video_cnt": 6702,
  "sec_uid": "MS4wLjABAAAAbq-1Yqpp1a6u5KbV_sMg93_FK7AN3d6MJeZ3H0Yj3vZXOtqFXXjc2TIkMW7flCxX",
  "is_private": false,
  "itemsFilled": true,
  "itemsCount": 1,
  "videoListStatus": "ok",
  "engagementRate": 0.20137,
  "sortField": "follower",
  "sortValue": 60053787,
  "enrichmentLevel": "full",
  "scrapedAt": "2026-08-01T08:20:18+00:00",
  "runId": "abcd1234efgh5678",
  "chartEntries": [
    {
      "requestedMarket": "US",
      "resolvedMarket": "US",
      "periodDays": 7,
      "hashtag": "sixers",
      "hashtagID": "191352",
      "hashtagRank": 3,
      "creatorRankInHashtag": 2,
      "hashtagViews": 88347771,
      "hashtagPosts": 8669
    }
  ]
}

chartEntries[] is only present when includeChartEntries is true (the default). Each entry in items[] carries item_id, cover_url, tt_link, vv, liked_cnt and create_time — note that per-video comment and share counts are read internally to compute the creator-level engagementRate but are not exposed as separate fields on each video.

Output for a market coverage rollup

Written to a separate market-coverage dataset (uncharged) when writeMarketRollup is true, one row per requested market:

{
  "requestedMarket": "US",
  "resolvedMarket": "US",
  "marketSupported": true,
  "marketFallbackApplied": false,
  "returnedData": true,
  "creatorRows": 18,
  "uniqueCreators": 15,
  "rankDistributionInHashtag": { "1": 6, "2": 6, "3": 6 },
  "windows": [
    {
      "periodDays": 7,
      "httpStatus": 200,
      "bytes": 48213,
      "hashtagRows": 3,
      "creatorRows": 9,
      "error": null
    },
    {
      "periodDays": 30,
      "httpStatus": 200,
      "bytes": 47990,
      "hashtagRows": 3,
      "creatorRows": 9,
      "error": null
    }
  ],
  "runId": "abcd1234efgh5678",
  "generatedAt": "2026-08-01T08:20:18+00:00"
}

A run-level summary of the same sweep is also written to the MARKET_COVERAGE key-value record, with slicesRequested, slicesWithData, boardRowsTotal, uniqueCreators, creatorsInMultipleResolvedMarkets, profileEnrichment and videoEnrichment coverage counts, plus the same per-market markets[] array.

Schema stability and export options

Field names stay stable across runs regardless of TikTok front-end changes, because every field is read from a JSON payload embedded in the page rather than parsed from rendered HTML — when TikTok's public payload structure changes, the field breaks loudly (returns null or fails the slice) rather than silently. Export the default dataset as JSON, CSV, Excel, XML or JSONL from the Apify Console, or pull it programmatically with the Apify API or apify-client. The market-coverage dataset and MARKET_COVERAGE key-value record are reachable the same way.

---

💡 TikTok Trending Creator Scraper Strategy Guide

🎯 Strategy 1: Real-time enrichment pipeline

Trigger a run whenever your campaign needs a fresh creator list for a market set — via a webhook, a scheduled task, or manually before an outreach sprint. Run the Actor with your target markets[], then read handle, nick_name, follower_cnt, tt_link and sourceHashtag off each row and append them to your CRM or outreach sheet. Because de-duplication happens before charging, re-running the same market set does not double-bill you for creators already in your list.

🎯 Strategy 2: Scheduled monitoring and alerting

Use an Apify schedule to run this Actor daily or weekly against a fixed market list. Diff each run's marketsChartedIn, sourceHashtag and sourceHashtagRank against the previous run's dataset (matching on user_id) to detect new creators entering a market's board or a hashtag's rank climbing. Alert on the delta — a creator appearing in marketsChartedIn for a market it was not in last run is the signal worth acting on.

🎯 Strategy 3: Bulk dataset build

Set sweepAllMarkets: true with all three periods selected for the widest single-run dataset this Actor supports (729 raw rows before de-duplication, capped by maxItems). Export the resulting dataset directly to CSV or JSON from the Apify Console, or pull it via the API into your own database. No run-level concurrency limit is documented for this Actor beyond requestDelaySeconds, which paces only the profile/video enrichment calls — the board sweep itself runs its market/window slices in parallel internally.

Strategy comparison at a glance

Strategy	Best for	Run pattern	Output format
Real-time enrichment	Outreach and lead lists	On-demand or webhook-triggered run	Dataset rows appended to CRM/sheet
Scheduled monitoring	Trend and rank tracking	Apify schedule, diffed run-over-run	Dataset diff by user_id / sourceHashtag
Bulk dataset build	Research and training data	Single large sweep (sweepAllMarkets: true)	Full dataset export to CSV/JSON

---

🌴 Related TikTok Scrapers & Tools

Scraper	What it extracts
TikTok Data Scraper: Comments, Replies & AI Sentiment	Profiles, videos, followers, comments & replies, hashtags, music and playlists for a specific TikTok account, with optional AI sentiment classification
TikTok Shop Data Scraper & Seller Profile Scraper	TikTok Shop products plus seller/shop profiles — rating, followers, product and sold count, registered business details
YouTube Channel Scraper (with Comments)	A YouTube channel's profile, videos, Shorts, live streams, community posts and comment threads — the same creator/profile entity type on a different platform
Threads Search Post Scraper With Engagement Analytics	Public Threads posts with engagement analytics — a complementary social-listening surface for cross-platform trend monitoring

---

How to integrate TikTok Trending Creator Insights Scraper Across Every Country with your stack

TikTok Trending Creator Insights Scraper Across Every Country works with any language or tool that can make an HTTP request — the Apify API and its client libraries wrap that request for you.

Python

from apify_client import ApifyClient
import csv

client = ApifyClient("<YOUR_APIFY_API_TOKEN>")

run_input = {
    "markets": ["US", "GB", "MX", "BR", "DE"],
    "periods": ["7", "30"],
    "enrichmentLevel": "full",
    "sortBy": "follower",
    "maxItems": 50,
}

run = client.actor("YOUR_USERNAME/tiktok-trending-creator-insights-scraper-across-every-country").call(
    run_input=run_input
)

rows = []
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    if item.get("rowType") == "creator":
        rows.append(item)

with open("tiktok_trending_creators.csv", "w", newline="", encoding="utf-8") as f:
    writer = csv.DictWriter(f, fieldnames=list(rows[0].keys()))
    writer.writeheader()
    writer.writerows(rows)

print(f"Saved {len(rows)} creator rows.")

Node.js

import { ApifyClient } from "apify-client";

const client = new ApifyClient({ token: "<YOUR_APIFY_API_TOKEN>" });

const run = await client.actor("YOUR_USERNAME/tiktok-trending-creator-insights-scraper-across-every-country").call({
    markets: ["US", "GB", "MX", "BR", "DE"],
    periods: ["7", "30"],
    enrichmentLevel: "full",
    sortBy: "follower",
    maxItems: 50,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
const creators = items.filter((row) => row.rowType === "creator");

console.log(`Fetched ${creators.length} creator rows.`);

Async and scheduled pipelines

For fire-and-forget large sweeps, start the run with client.actor(...).start() instead of .call() and poll the run status, or configure an Apify webhook on the run to fire when the dataset is ready. For recurring sweeps, set up an Apify schedule in the Console to re-run the Actor on a cron interval — this Actor has no built-in scheduler of its own, so recurring monitoring relies on the platform's schedule feature.

---

🎯 Who needs TikTok Trending Creator Insights Scraper Across Every Country? (Use cases & industries)

🏢 Influencer marketing and talent agencies

Build a multi-country creator shortlist in a single run instead of stitching together 27 separate country reports. marketsChartedIn, follower_cnt and sourceHashtag give an agency a ranked, market-tagged candidate list ready for outreach.

📊 Data and growth teams

Feed handle, follower_cnt, profile_follower_cnt and engagementRate into an internal creator-scoring model, using scrapedAt to track how a creator's board presence changes run over run.

📱 Brand and competitive intelligence teams

Watch sourceHashtag and sourceHashtagRank across your category's key markets to see which topics and creators are currently pulling attention, and use marketFallbackApplied to know which markets in your tracking list are genuinely local versus mirrored.

🔬 Researchers

Academic and market researchers use the public board, profile and video data to study cross-market trend dynamics — for example, comparing which hashtags surface different creators across the 7/30/90-day windows in periodDays. Public data only; no private accounts are accessed.

🎥 Product and SaaS builders

Build a creator-discovery dashboard, influencer database, or monitoring alert product on top of the stable JSON contract, filtering on rowType to separate billed creator rows from uncharged market_error accounting rows.

---

Is it legal to scrape TikTok's trending creator board?

Scraping publicly accessible data is generally lawful — in hiQ Labs v. LinkedIn (9th Cir. 2019), the court held that accessing public web data does not violate the U.S. Computer Fraud and Abuse Act. This Actor reads only public surfaces: the Creative Center trending board, public profile pages, and public video pages — it never logs in and never accesses private accounts. Separately, scraping may still breach a platform's Terms of Service, which is a civil contract matter between you and TikTok, not a criminal one, and is a distinct question from whether the data itself is public. Because the output includes personal data about identifiable creators — nicknames, handles, avatar images and follower counts — storing or reusing it can trigger GDPR or CCPA obligations depending on your jurisdiction and how you use it. TikTok Trending Creator Insights Scraper Across Every Country returns only publicly accessible data. What you do with that data is your responsibility — consult legal counsel for commercial applications involving personal data.

---

❓ Frequently asked questions

Does it work without a TikTok account?

Yes. Every surface this Actor reads — the Creative Center trending board, public profile pages and public video pages — is unauthenticated. No login, cookies or API key are used or required.

How does it handle TikTok's anti-scraping measures?

Requests go through curl_cffi with a real Chrome TLS fingerprint (impersonate="chrome131" or "chrome99_android" depending on the surface), which is what these endpoints actually check rather than headers. Failed or undersized responses are retried up to 3 times with growing backoff, and www.tiktok.com requests are serialized through a pacer that enforces requestDelaySeconds between calls. A 200-status response with a suspiciously small body is treated as a WAF shell or rate-limit stub, never as data.

Can I run it at scale without getting blocked?

The board sweep runs its market/window slices with limited internal concurrency and retries; enrichment requests to www.tiktok.com are paced at requestDelaySeconds (2.5 s by default) because that surface answers HTTP 503 when hammered. No uptime or success-rate figure is published for this Actor — lowering the delay below the documented default raises the chance of empty items[] or failed profile fetches.

How fresh is the data?

Every run fetches TikTok's current trending board live — nothing is cached between runs. The board itself reflects TikTok's present trending window at the time you run the Actor, not a historical snapshot.

Which fields work best for AI training and RAG indexing?

For RAG, use sourceHashtag together with chartEntries[] to enrich an index with which creators are trending under which topic, in which market, and when. For training data, the numeric and categorical fields — follower_cnt, engagementRate, marketCount, sourceHashtagViews — are the most structurally consistent across every row. TikTok's trending board does not publish creator bios or video captions, so there is no long-form text field to index here; every field returns as a typed primitive requiring no normalization.

Does storing this data trigger data protection obligations?

Yes, potentially. nick_name, handle, avatar_url and follower counts are personal data about identifiable creators. This Actor returns only publicly available data; the lawful basis for storing and using it — including any GDPR or CCPA obligations in your jurisdiction — sits with you as the operator, not with the Actor.

Does it work with Claude, ChatGPT, and other AI agent tools?

This Actor has no MCP server integration. It is callable as an HTTP endpoint through the Apify API by any agent framework that can make a request — every response is typed JSON, so an agent can consume it directly without an HTML-parsing step.

Why only 9 creators per market and window slice?

That is TikTok's own cap on the trending board, not a limit this Actor imposes: 3 hashtags × 3 creators per slice, and the upstream pagination object reports no further pages. Get more creators by adding markets and windows, not by raising maxItems past what the sweep can actually produce.

What happens if I select RU?

RU is the one code in the list without its own board — TikTok's loader serves it the United States board and echoes US back as the resolved country. You still get rows, but marketSupported reads false and marketFallbackApplied reads true, so you can identify and handle mirrored rows explicitly instead of TikTok silently substituting data.

How does this scraper compare to other TikTok creator scrapers?

No competing Apify Store listing for a directly comparable multi-market trending-creator sweep was verified as of 2026-08-04, so this is not a head-to-head claim against a named product. What this Actor's own architecture provides is a single run covering up to 27 markets with cross-market de-duplication and fallback transparency — a task that would otherwise require one run per country stitched together manually.

---

ℹ️ Disclaimer

TikTok Trending Creator Insights Scraper Across Every Country extracts only publicly available data from TikTok. This tool is intended for lawful use cases only. Users are responsible for complying with TikTok's terms of service and applicable data protection laws in their jurisdiction.