Social Media Growth Analyzer — Social Blade Alternative

Analyze Instagram, TikTok, and YouTube audience metrics. Supply earlier snapshots to calculate growth, compare same-platform profiles within a run, and optionally export labeled projections alongside current profile data. For creator agencies, each dataset row is one profile snapshot with any valid baseline comparison and same-platform run ranking.

Workflow: put the results to work

Collect the creator roster once, then supply those rows as baselineSnapshots in a later run. Use stable profile keys to compare audience and content changes under the same definitions. Within-run ranks cover only the selected same-platform profiles, and optional projections are linear calculations rather than forecasts.

What you get

• Current followers or YouTube subscribers, following count, content count, and available lifetime views or likes.
• A stable profileKey and snapshotAt for joining scheduled runs into a time series.
• Audience, content, and lifetime-engagement changes when you provide an earlier Actor row.
• Average audience change per day and audience growth percentage.
• Audience rank and audience share among same-platform profiles in this run.
• An optional 30-day linear audience projection with the calculation method attached.
• JSON, CSV, Excel, API, webhook, schedule, and MCP-friendly output through Apify.

Quick start

Provide one to 100 public profile URLs or tagged handles:

{
  "profileUrls": [
    "https://www.instagram.com/natgeo/",
    "https://www.tiktok.com/@natgeo",
    "youtube:@Apify"
  ],
  "maxProfiles": 3
}

Supported inputs are Instagram profile URLs, TikTok @handle URLs, YouTube @handle URLs, YouTube /channel/CHANNEL_ID URLs, and tagged handles such as instagram:@natgeo. Duplicate profiles are removed.

Track growth between runs

Copy a previous dataset row into baselineSnapshots. The Actor matches it by profileKey and calculates change only when the earlier timestamp and required counts are valid.

{
  "profileUrls": ["youtube:@Apify"],
  "maxProfiles": 1,
  "baselineSnapshots": [
    {
      "profileKey": "youtube:apify",
      "platform": "youtube",
      "handle": "Apify",
      "audienceCount": 100000,
      "contentCount": 300,
      "lifetimeEngagementCount": 5000000,
      "snapshotAt": "2026-08-01T12:00:00.000Z"
    }
  ],
  "includeProjections": true
}

For repeated tracking, save the profile list as an Apify task and run it on a schedule. Store each dataset result in your spreadsheet or warehouse, then pass the previous row back as the next baseline.

Workflow: from creator roster to growth report

A creator agency starts with the public profile URLs for a campaign roster. It runs the Actor after onboarding the creators, exports the resulting rows to its reporting table, and schedules the same input for the next reporting date. On the next run, the agency passes the earlier rows as baselineSnapshots. The Actor then calculates each creator's observed growth and same-platform rank, so the team can decide which profiles need a closer campaign review and feed the structured result into its client report.

Output

One row represents one profile at one collection time:

{
  "recordType": "social-profile-snapshot",
  "profileKey": "youtube:apify",
  "platform": "youtube",
  "profileUrl": "https://www.youtube.com/@Apify",
  "handle": "Apify",
  "displayName": "Apify",
  "audienceCount": 102500,
  "contentCount": 308,
  "lifetimeEngagementCount": 5180000,
  "comparisonStatus": "compared",
  "baselineSnapshotAt": "2026-08-01T12:00:00.000Z",
  "daysSinceBaseline": 30,
  "audienceChange": 2500,
  "audienceGrowthPercent": 2.5,
  "averageAudienceChangePerDay": 83.3333,
  "contentChange": 8,
  "lifetimeEngagementChange": 180000,
  "audienceRankInRun": 1,
  "rankScope": "same-platform-profiles-in-this-run",
  "projectedAudience30Days": 105000,
  "projectionMethod": "linear-from-baseline",
  "snapshotAt": "2026-08-31T12:00:00.000Z"
}

Counts can be null when a platform does not make the corresponding metric public. lifetimeEngagementCount means an available account-level aggregate of views or likes; it is not a recent-post engagement rate.

Field	Meaning
profileKey	Stable platform-and-profile key for joining snapshots across runs.
audienceCount	Current public followers or YouTube subscribers.
audienceChange	Current audience minus the matched earlier audience.
audienceGrowthPercent	Audience change divided by the earlier audience.
averageAudienceChangePerDay	Audience change divided by elapsed days.
audienceRankInRun	Rank among profiles from the same platform in this run only.
projectedAudience30Days	Optional straight-line estimate from two supplied observations; never a guarantee.
snapshotAt	ISO 8601 collection time for freshness and time-series joins.

The OUTPUT record also includes a compact reportSummary with profiles returned, comparisons completed, projections created, platform totals, and the largest audience in each platform group.

Best fit

• Creator agencies tracking a known roster across YouTube, Instagram, and TikTok.
• Brand teams comparing campaign creators or ambassadors.
• Analysts building weekly or monthly growth reports.
• Automations that need structured profile analytics instead of dashboard screenshots.
• AI agents that need a bounded profile-metrics tool with explicit output semantics.

API and automation

Start a run through the Apify API:

curl -X POST \
  "https://api.apify.com/v2/acts/khadinakbar~socialblade-alternative/runs?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"profileUrls":["https://www.youtube.com/@Apify"],"maxProfiles":1}'

Read the default dataset URL returned by the run for analytics rows. Use OUTPUT for the terminal outcome and compact report summary, and RUN_SUMMARY for lifecycle and charge reconciliation.

Agent prompt

Analyze these public Instagram, TikTok, and YouTube profiles. Return current audience metrics, changes from the supplied earlier snapshots, same-platform ranks within this run, collection times, and the terminal outcome.

The agent should read the default dataset for the profile rows and OUTPUT for the terminal outcome and compact summary. The tool's scope is known-profile analytics; discovery of new creators is a separate upstream workflow.

How it compares with Social Blade

This Actor covers a focused Social Blade-style workflow: current public profile analytics, buyer-owned scheduled history, two-snapshot growth calculations, batch comparison, and automation-ready output.

Social Blade remains the better choice when you need its broader dashboard, global databases, long historical series already collected by Social Blade, global ranks, grades, top lists, live-count experiences, or estimated earnings. This Actor does not invent those fields.

Decision	This Actor	Social Blade
Starting point	Your known Instagram, TikTok, or YouTube profiles	Its supported website and product surfaces
Current metrics	Structured rows for automation and exports	Dashboard and documented API responses
Growth history	You own the snapshots; compare an earlier Actor row	Broader pre-collected historical features are available in Social Blade products
Ranking	Explicitly limited to same-platform profiles in this run	Broader ranking products are part of Social Blade
Projections	Optional linear estimate from two supplied observations	Broader projection experiences are available in Social Blade products
Billing and same-job cost	Pay per event for each persisted analytics row; use the live Pricing tab for current cost	Uses its own product and API pricing models
Effective efficiency	One bounded API run returns usable rows for a supplied roster and downstream automation	Its suite supports a broader dashboard-led research workflow
Integrations and automation	Apify API, schedules, webhooks, dataset exports, and MCP workflows	Website products and a documented Business API
Bounded scope	Replaces the known-profile tracking and comparison workflow	Broader suite features remain the better fit for global research
Best fit	Scheduled roster monitoring, API workflows, and custom reports	Historical discovery, global comparisons, and dashboard-led research

Data quality and responsible use

The Actor accepts public profile identities, not social-account passwords, cookies, or login details. Every terminal path writes OUTPUT and RUN_SUMMARY with one of COMPLETE, PARTIAL, VALID_EMPTY, INVALID_INPUT, UPSTREAM_FAILED, or CONFIG_ERROR.

Growth calculations are made only from the counts and timestamps present in two snapshots. Projections require at least one elapsed day and are labeled linear-from-baseline. Run-local ranks are never presented as global platform ranks. Use this Actor only for public data you are authorized to collect and process under applicable laws and platform terms.

Builder's note

I built the comparison layer around an earlier Actor row because current public profile totals and historical analytics are different evidence. I found that a stable profileKey, explicit collection time, and transparent two-point math produce a more useful automation contract than expanding the row into grades or global ranks. My goal is to make every derived number reproducible from fields in the same dataset.

Pricing and run costs

This Actor uses Pay per event plus Apify platform usage. The Pricing tab lists the current event rates and billing terms.

Event	Billing unit	When it applies
apify-actor-start	Actor Start	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
social-profile-snapshot	Social profile snapshot	Charged for each validated, normalized public profile snapshot saved to the dataset.

Run cost combines the charged events and Apify platform usage. Review the run charge limit and requested result count before starting.

Independent alternative

This Actor provides the specific workflow described above. It is not affiliated with or endorsed by Social Blade; the named product and its trademarks belong to their respective owners.

Connect an AI agent

Use the Apify MCP configurator to choose an available client connection. Inspect this Actor’s current input schema and required credentials before running it.