
Understand how organizations, projects, creators, videos, campaigns, and goals fit together in trackagoat.
trackagoat is organized in a hierarchy:
Organization
└── Project(s)
├── Creator(s) — TikTok accounts being tracked
│ └── Video(s) — videos discovered from this creator
├── Video(s) — videos added directly by URL
└── Campaign(s) — named groupings of creators, videos, and sub-campaignsAn organization is the root of your workspace. All creators, projects, campaigns, and API keys belong to an org. Your subscription tier (Free / Starter / Ultra) is set per org and determines your limits.
You can belong to multiple orgs. Roles within an org are admin (can manage members, settings, and API keys) or member.
A project groups creators and campaigns for a specific program or time period. Examples: Q1 Brand Program, Holiday Campaign 2026, Always-On Ambassadors.
Each project has:
pending_review status waiting for your approvalA creator is a TikTok account being tracked. Each creator has:
auto or selective) that controls how newly discovered videos enter the systemA video is an individual TikTok post. Each video has:
view_count, like_count, comment_count, share_count| Status | Meaning |
|---|---|
auto_tracked | Discovered automatically; included in all stats |
pending_review | Discovered but waiting for manual review (selective mode) |
included | Manually approved; included in stats |
excluded | Manually excluded; not counted in stats |
direct_add | Added directly by URL; always included |
A campaign is a named grouping of creators, videos, and/or other campaigns. It has aggregate stats that recursively sum across all items — you don't need to manually aggregate sub-campaigns.
Campaigns can nest: a campaign can contain sub-campaigns. trackagoat resolves the full tree when computing stats, and prevents circular references.
Common uses:
2026 Program → Q1 → January LaunchA goal is a per-creator performance target. Examples:
trackagoat tracks compliance — whether a creator is meeting the goal — and surfaces non-compliant creators in the goals overview.
API keys give programmatic read access to your org's data. Keys are scoped to the organization of the user who created them. A key is shown once at creation and cannot be recovered.
See API keys and the API reference for details.
API reference
Read-only v1 API for programmatic access to your org's data.