A secUid (secuid) is TikTok’s stable, account-level identifier used by analytics APIs to bind Shop, Video, and LIVE metrics to one creator even when the public handle changes. Store it as the primary identity key, resolve it once, and join all fetched snapshots to it so dashboards stay consistent across endpoints and deprecations.
A secUid (often written secuid) is TikTok's account-level identifier for analytics fetches, and it is what keeps Shop, Video, and LIVE metrics attached to the same creator when the public handle changes. If you are building a TikTok Shop analytics dashboard, the first engineering decision is not which chart library to use. It is how you resolve and store identity, because every later request depends on it.
TikTok Analytics API Data Surfaces: Shop, Video, and LIVE
There is no single public endpoint that returns every Shop, Video, and LIVE metric for every account. A compliant pipeline combines public data surfaces, seller-authorized endpoints, and stored snapshots. That distinction matters for anyone evaluating a social media data API or designing a dashboard for sellers, creators, and agencies.
The Shop, Video, and LIVE families answer different business questions. Shop metrics describe catalog movement, price changes, seller activity, and product-level demand signals. Video metrics describe content reach and engagement. LIVE metrics describe session-level audience behavior. A useful dashboard does not blur them together, because each family has different freshness needs and different access rules.
| Metric family | Typical dashboard fields | Where it comes from |
|---|---|---|
| Shop | Product listings, price movement, category rank shifts, seller catalog changes, affiliate attribution where exposed | Public product and seller surfaces plus seller-authorized Shop endpoints; order-level data requires authorization |
| Video | Views, likes, comments, shares, saves, posting cadence, derived engagement and view velocity | Public video and profile surfaces; authorized analytics for owned accounts |
| LIVE | Session length, concurrent and peak viewers, public gift or revenue signals, repeat-session history | Public LIVE surfaces and authorized seller or creator analytics where available |
The fetch pattern is shared across all of them. Resolve an identity with secUid or a shop and product ID, request the metric set for a time window, then normalize the response into a warehouse-friendly schema. This is where Seller Compass field mapping for BI dashboards offers a useful template: if the normalized output uses the same column names for every source, the same chart components can render Shop, Video, and LIVE panels side by side without custom logic for each endpoint.
Set expectations on public-data limits before design begins. Public signals can support product research, creator benchmarking, and trend detection. Order-level revenue, customer details, and private seller back-office fields require seller-authorized access. A dashboard that promises private seller revenue from public data will fail compliance review and product trust. SignalCart's approach is public data only, with clear separation between public signals and authorized seller data.
secUid: The Stable Identifier Every TikTok Fetch Starts With
TikTok exposes more than one identifier. The public handle is for humans and can change. A numeric user ID may appear in URLs or internal records. The secUid is the account-level key that analytics endpoints commonly expect, which is why it is the load-bearing identifier in the TikTok data model. Store all of them, but join on secUid.
The resolution step in a fetch pipeline looks like this: handle to secUid to profile, video list, LIVE sessions, and any shop or creator attribution attached to that account. If a creator renames their handle, a dashboard keyed only on the handle will break joins, duplicate rows, and split historical charts into two unrelated records. A dashboard keyed on secUid preserves continuity and keeps creator GMV, engagement history, and content performance in one timeline.
Operational failure modes are predictable. Cache secUid mappings with a source timestamp and status flag so repeated lookups do not hit rate limits. Handle deleted or private accounts by preserving historical rows and marking the account as unavailable rather than erasing it. De-duplicate creator records when the same person appears across TikTok Shop, Instagram, and YouTube in a cross-platform dataset. There is no universal person-level ID across those platforms, so use deterministic links where available and review probabilistic matches before merging records.
Shop Metrics for Seller and Product Dashboards
Shop-facing fields worth modeling include product-level sales velocity, price movement, per-seller catalog changes, category ranking shifts, and affiliate or creator attribution where public signals expose it. Not every field is available for every product or seller. A mature schema records availability alongside the value, so a missing field is treated as unknown rather than zero.
Raw pulls become useful when they feed the first charts sellers ask for: a product trend line over a configurable window, a category leaderboard, and a seller catalog delta period over period. The trend line shows whether demand is accelerating or fading. The leaderboard shows which products are gaining rank. The catalog delta shows whether a seller is expanding, pruning, or repricing their assortment.
The same Shop schema can support Amazon product research. A merchant tracking one SKU across marketplaces should not rebuild the metric layer twice. Use a shared product entity, a marketplace dimension, and a consistent metric naming convention. SignalCart API is designed around that pattern: e-commerce and social media data across Amazon, TikTok Shop, Instagram, and YouTube through a single API, using public data only.
Video and LIVE Metrics for Creator and Campaign Dashboards
The Video metric set includes views, likes, comments, shares, saves, watch-time proxies, and posting cadence. Derived rates make cross-creator comparison fair. Engagement rate must use the same denominator across creators. View velocity in the early window after posting helps distinguish a durable hit from a short spike. Posting cadence shows whether growth comes from consistent output or a single viral item.
The LIVE metric set includes session length, concurrent and peak viewers, gift and revenue signals where public, and the repeat-session pattern that separates consistent sellers from one-off spikes. A creator who peaks once may be a campaign risk. A creator who runs repeat sessions with stable audience retention is a safer partner for a TikTok Shop launch.
Creator GMV and engagement should roll up into a single creator scorecard so agencies can rank partners without manually opening each profile. Label estimated GMV clearly, separate public signals from seller-authorized data, and avoid blending fields with different reliability. A scorecard that mixes a verified order total with a modeled estimate without disclosure is not competitive intelligence. It is noise with a chart around it.
Endpoint Deprecation, Rate Limits, and Keeping Dashboards Alive
TikTok Shop API changes and their impact on data intelligence platforms ripple through third-party dashboards. An endpoint that disappears or changes shape can silently blank a panel. A dashboard that shows zero is worse than one that shows an error, because zero looks like a business signal while an error looks like a data problem. SignalCart's published guidance on TikTok Shop Open Platform breaking changes in 2026 recommends versioning and early deprecation alerts. Notes on TikTok Shop Affiliate API deprecation make the same point: third-party seller dashboards need a continuity plan.
Defensive engineering starts with TikTok Shop Open Platform versioning practices such as version-pinned adapters per endpoint. Add schema validation on ingest so a changed field type fails loudly. Keep raw responses for backfill when a normalized table is corrupted or a field mapping changes. Add freshness badges in the UI that tell the viewer when a metric was last successfully fetched. If a panel is stale, say so.
Rate limits require a refresh strategy rather than a polling habit. LIVE sessions and launch-day video velocity justify near-real-time polling because audience behavior changes during the broadcast or campaign. Catalog and category rankings can refresh daily because they move more slowly. Queue requests, use backoff, and cache identity lookups. For teams comparing scraping with official access, review court rulings, official API terms, compliance requirements, and platform risk before choosing a bridge strategy.
Assembling the Dashboard: Schema, Cadence, and Tools
A minimal star schema keeps the build manageable. Accounts are keyed by secUid. Content items link to accounts. LIVE sessions link to accounts. Daily metric snapshots link to content items and sessions. That structure supports Shop, Video, and LIVE panels without collapsing unrelated entities into one wide table.
| Entity | Primary key | Why it matters |
|---|---|---|
| Accounts | secUid | Preserves identity across handle changes and cross-platform matching |
| Content items | Video ID plus secUid | Keeps video history attached to the right creator |
| LIVE sessions | Session ID plus secUid | Separates repeat sessions from one-off broadcasts |
| Metric snapshots | Entity ID plus timestamp | Supports trend lines, audits, and backfill |
| Metric family | Refresh cadence | Reason |
|---|---|---|
| LIVE sessions | Near-real-time while live | Viewer peaks and session revenue move during broadcast |
| Video early velocity | Frequent during launch window | Trending products and campaigns need early signals |
| Shop catalog and category rankings | Daily | Rankings move slowly enough for batch refresh |
| Historical snapshots | Daily or weekly | Supports trend lines and audits |
When comparing native and third-party TikTok dashboards, the build-versus-buy decision is really a maintenance decision. Maintaining your own scrapers and endpoint adapters against a moving target gives control but consumes engineering time on identity resolution, schema drift, and deprecation alerts. Pulling normalized Shop, Video, and LIVE metrics from a single API shifts that burden to the vendor. SignalCart API and SignalCart Trends are built for that trade-off, with product and creator intelligence for teams that need marketplace trends and seller insights without building every adapter. A hybrid approach is common: buy the normalized metric layer, then build proprietary scoring on top.
Before shipping, run a validation checklist. Spot-check a small sample of creators against the native app and record discrepancies. Confirm secUid stability after a handle change and verify that historical joins do not duplicate. Simulate an endpoint failure and check that alarms, freshness badges, and backfill work. Confirm that private or deleted accounts are tombstoned rather than erased. A TikTok analytics dashboard is only as trustworthy as its identity layer and its honesty about data accuracy.
FAQ
What metrics can be extracted using the TikTok Shop Analytics API?
Depending on access, Shop endpoints can expose product listings, price movement, category rank shifts, seller catalog changes, and affiliate attribution where available. Order-level metrics require seller authorization.
How does API endpoint deprecation impact third-party seller dashboards?
Deprecation breaks live calls, so dashboards must version endpoints, monitor changes, and rely on stored snapshots to avoid data gaps. Identity keys such as secUid help preserve continuity when endpoints change.
How do TikTok Shop API changes affect ecommerce analytics platforms?
They force platforms to update connectors, revalidate metric definitions, and maintain stable identity mapping so historical comparisons remain valid. Platforms that store snapshots can recover faster from breaking changes.
by Alejandro Martín Vega, Technology & Ecommerce Intelligence Journalist
Alejandro Martín Vega is a Spanish technology journalist specializing in ecommerce intelligence, digital marketplaces, and competitive research. Based in Madrid, he explores Amazon seller strategies, TikTok Shop ecosystems, advertising intelligence, and emerging retail technologies. His writing focuses on turning complex marketplace data and industry developments into practical insights that help businesses, marketers, and online sellers make informed decisions.
