Skip to content

no-code-guide.md

Latest commit

 

History

History
49 lines (35 loc) · 2.31 KB

no-code-guide.md

File metadata and controls

49 lines (35 loc) · 2.31 KB
Raw

Run Social Blade Multi-Platform Analytics Scraper without code

Use Apify's web interface to collect public Social Blade creator analytics without installing Python or managing credentials for the underlying source.

Step by step

  1. Open Social Blade Multi-Platform Analytics Scraper on Apify.
  2. Select the Input tab.
  3. Add public Social Blade URLs or bare handles under Profiles.
  4. Leave the defaults enabled for a complete first snapshot, or disable history/estimates if you only need current profile data.
  5. Click Start.
  6. Open the Dataset tab after the run succeeds.
  7. Inspect recordType and status before using the results, then export JSON, CSV, Excel or JSONL.

First test

Use one known public profile to keep the first run bounded:

{
  "profiles": [
    "https://socialblade.com/youtube/handle/mrbeast"
  ]
}

The checked-in sample input uses this exact request.

Optional settings

  • defaultPlatform determines the platform for bare handles and defaults to YouTube.
  • includeDailyHistory and historyDays control daily rows; the maximum requested window is 31 days.
  • includeWeeklyHistory and includeMonthlyHistory control the corresponding history records.
  • includeGrowthMetrics and includeEarningsEstimates control optional current metrics.
  • maxProfiles limits attempted inputs; 0 means all submitted profiles up to 1,000.

Interpret the result

  • recordType: "profile" is the normalized current snapshot.
  • recordType: "dailyStat", "weeklyStat" and "monthlyStat" are available history rows.
  • status: "ok" means the usable profile snapshot was delivered.
  • status: "partial" means a valid profile was delivered but an attempted endpoint failed.
  • Error records preserve the submitted input, stable error code and collection metadata.

Missing values are not treated as zero. Check dataQuality to distinguish unavailable source coverage from a failed attempted endpoint.

Cost control

The Actor charges one profile event only for a successfully delivered profile snapshot. Invalid, duplicate, failed, partial and skipped records are not charged, and history rows do not create separate events. Start with one profile, review the Dataset, then increase the batch.