Split projects into tags
Connect the MCP, paste the prompt, review the plan your agent proposes, and approve the writes.
API changes
Project filters and assignment endpoints stop working on December 1, 2026. See what replaces them.
Split overloaded projects into a product, country tags and custom tags without losing which accounts belong where.
Before tags existed, a project name often carried several things at once: the product, a market, a creator group, a video hook. Tags let you keep each of those as its own label and combine them in any filter.
This guide is for workspaces that still have such projects. For tags in general, read Tags.
Connect the MCP, paste the prompt, review the plan your agent proposes, and approve the writes.
Project filters and assignment endpoints stop working on December 1, 2026. See what replaces them.
Every former project is now a product: a tag you can filter by, with the same id and the same accounts as before. You don't have to migrate anything to keep filtering in the dashboard.
Splitting is still worth it when a name holds more than the product:
AppName · Hook A · Italy becomes the product AppName, the custom tag Hook A, and the country tag 🇮🇹 Italy. You can then compare Italy across all products, or Hook A across all markets.The prompt below lets an agent plan the split and, after you approve, write it. Any agent that supports MCP works.
In the dashboard, open API, then Agents, and follow the setup for the agent you use.
Start a new agent chat with the prompt below. The agent reads your tags, products and account assignments and stops with a plan.
Check which tags it reuses, which it creates, and which product maps to which tags. Change what you disagree with.
After your approval the agent creates the missing tags and assigns them to the same accounts. Open Tags and an analytics filter to confirm.
Use the viral.app MCP to split my products (formerly called projects) into tags.
Goal
A product should stand for one thing I sell: an app, a site or a brand. Anything else packed into a product name (a market, a creator group, a video hook, a channel) becomes its own tag, assigned to the same tracked accounts. Countries use the built-in country tags.
Step 1: read, do not write
- Call list_tags for the scopes system, org and product. Product-scope tags are my products (a response may still label that scope "project"); system-scope tags include every country; org-scope tags are my custom tags.
- Call list_projects for the products, and list_account_tag_rules for which accounts carry which tag.
- Use large page sizes so you make few calls.
Step 2: show me a plan and stop
For every product that has accounts assigned, show one row:
- the product name today
- the product it stays or becomes (name only what I sell, in normal brand casing)
- the custom tags to reuse (with their ids) or to create
- the country tags to assign (existing system tags only)
- the product description, and the tag it should move to, if any
List separately every product you are unsure about, with your options. Wait for my approval or changes.
Step 3: after I approve, write
- Create missing custom tags with create_tag.
- Assign tags to accounts with add_tracked_account_tags_bulk. Use set_tracked_account_tags only when an account's whole tag list must be replaced.
- Report what you created and assigned, with counts.
Examples
- "FitTrack - Ambassadors - Italy": keep the product FitTrack. Reuse or create the custom tag "Ambassadors". Assign "Ambassadors" and the country tag Italy to the accounts of that product.
- "ITA": no product. Assign the country tag Italy to its accounts.
- "FITTRACK" and "FitTrack Ambassadors": both map to the product "FitTrack", not to two products.
Rules
- Never create a country tag and never create an "All" or "World" tag. A broad group like "all countries except X" is a filter, not a tag.
- Assign tags to accounts, never to single videos.
- Do not delete or rename products or tags. I remove what I no longer need myself.
- Tag references are { scope, tagId }. Use the id from list_tags as tagId, with scope "org", "product" or "system".
- If a product is not clearly something I sell but has accounts, do not drop it silently: put it in the unsure list.
Your products stay in place after the migration, so you can compare the old grouping with the new tags before you remove anything.
Two parts of the API were replaced by tags. Both were announced on July 2, 2026, have been marked deprecated in the API reference since July 29, and stop working on December 1, 2026 at 09:00 UTC.
A product id is also a tag id, so in most calls this is a rename of the parameter:
| Old | New |
|---|---|
GET /analytics/kpis?projects=orgproj_… | GET /analytics/kpis?tags=orgproj_… |
GET /analytics/metrics, /top-videos, /top-accounts, /top-creators, /views-by-country with projects | The same routes with tags |
GET /accounts, /accounts/tracked, /videos, /videos/activity with projects | The same routes with tags |
POST /accounts/export, /videos/export, /analytics/video-daily-gains/export with { "projects": [...] } | The same routes with { "tags": [...] } |
One difference: tags matches rows that carry all listed tags, while projects matched any of them. For "any of these products", send tagGroups=any:<id>,<id>.
| Old | New |
|---|---|
POST /projects/{id}/accounts/{accountId} and …/accounts/bulk | POST /accounts/tracked/tags/bulk with the product as a tag |
DELETE /projects/{id}/accounts/{accountId} and …/accounts/bulk | PUT /accounts/tracked/{orgAccountId}/tags with the account's tags, minus the product |
The two hashtag filter endpoints (PUT /accounts/tracked/{id}/hashtags and …/project-hashtags) were retired in September 2026 and answer 410. A tag workflow with a hashtag or caption condition and the Excluded action does the same job.
| MCP tool | API endpoint | Use it to |
|---|---|---|
list_tags | GET /api/v1/tags | Read tags, products and country tags |
create_tag | POST /api/v1/tags | Create a custom tag |
list_account_tag_rules | GET /api/v1/tags/account-rules | See which accounts carry which tag |
add_tracked_account_tags_bulk | POST /api/v1/accounts/tracked/tags/bulk | Add tags to several accounts |
set_tracked_account_tags | PUT /api/v1/accounts/tracked/{orgAccountId}/tags | Replace one account's whole tag list |
To update the code that calls these endpoints, use the agent prompt in Projects are now products. It covers the filters, the assignment endpoints and the rename in one pass.