Plans and limits

trackagoat enforces per-organization limits based on your plan tier. This page explains what each limit does, how they're enforced, and what happens when you hit one.

Plan tiers#

Limit keys#

Tracked videos#

Your plan keeps a set number of videos up to date. A video counts while trackagoat keeps refreshing its views, likes and comments: posts found on your tracked accounts, posts you included from the Inbox, and videos you added by link. Pending, excluded and expired videos don't count, and neither do videos on deleted accounts.

New posts are always tracked. When your organization goes over its limit, trackagoat keeps your newest videos updated and pauses your oldest ones (by posting date):

• A paused video keeps its last stats and shows a Paused: plan limit badge. Filter Videos by Paused (plan limit) to see them.
• A paused video still counts as posted: for posting goals, compliance, the calendar and Program Health.
• It stays payout-eligible with its last stats. Its views stop growing, so CPM and view-milestone payouts stop counting new views on it. Anything already earned is unaffected.
• Keep tracking on a paused video resumes it and exempts it from the limit, and your oldest other video is paused instead. Exempt videos count toward the limit but are never paused.
• When room opens up (an upgrade, or videos you exclude or that expire), the newest paused videos resume on their own.

Organizations already over the limit when this took effect, and any organization whose plan is downgraded, get 14 days before anything is paused. The Usage page shows how many videos are tracked and paused, and warns you at 80% of the limit.

Adding a video at the limit (by link, from the Inbox, or by resuming one) pauses your oldest video to make room. The request is only refused with 402 limit_reached when every tracked video is set to keep tracking.

How limits are enforced#

Count limits (accounts, projects, members, etc.) are enforced atomically: two concurrent requests cannot both succeed past the cap. You'll see a modal in the UI explaining which limit was hit.

Daily limits (API requests, manual updates) reset at midnight in your org's time zone. If you hit your daily API limit, requests return HTTP 429.

Update frequency floors (min_*_hours) set a minimum interval between scheduled updates. The scheduler runs each update type no more often than the larger of your org's configured interval and the plan minimum, and a configured interval below the minimum is raised to it when saved. On the Free plan (24 / 24 / 24) that means profiles, new-post discovery and video stats each run once a day. These floors do not apply to manual "Update Now" triggers, which are governed instead by max_manual_scrape_triggers_per_day. See How scraping works for a full breakdown of manual vs. automatic data collection.

Stats retention: a daily background job prunes history older than your retention window. Ultra tier has unlimited retention.

When you hit a limit#

In the dashboard: A modal appears with the limit key, your current count, and the cap. If your org is retroactively over a limit (e.g., after a tier downgrade), a banner appears at the top of every page until the org is back within limits.

In the API: Count limits return HTTP 402:

{
  "data": null,
  "error": "Limit reached: max_accounts_per_org",
  "meta": {
    "code": "limit_reached",
    "limitKey": "max_accounts_per_org",
    "current": 5,
    "max": 5
  }
}

Daily rate limits return HTTP 429:

{
  "data": null,
  "error": "Rate limit exceeded",
  "meta": {
    "code": "rate_limit_exceeded",
    "retryAfter": 3421
  }
}

retryAfter is seconds until the counter resets at midnight in your org's time zone.

Per-user limits#

One limit applies per user rather than per org:

The default is 6. If you need to belong to more orgs, contact support.

Requesting a raise#

Limits are adjusted by the trackagoat team. There is no self-serve upgrade path yet.

To request a raise:

1. 1

   Email support

   Email support@trackagoat.com with your org name and which limit you need raised.

2. 2

   Receive your override

   We'll apply a per-org override. Overrides take effect immediately with no restart required.