Rumble Creator & Video Signal Monitor

Track public Rumble creators, videos, search results, and current momentum signals for influencer discovery, brand monitoring, media research, and emerging-platform coverage.

This Actor is built for teams that already monitor YouTube, TikTok, Instagram, podcasts, newsletters, or mainstream media, but also need coverage for Rumble. It turns public Rumble pages into structured rows with creator names, channel URLs, video URLs, visible view counts, result ranks, recency signals, and simple momentum scoring.

What It Does

The Actor accepts Rumble channel URLs, Rumble search queries, or both. It then:

• inspects public Rumble channel pages
• searches Rumble for creator names, brand terms, topics, or campaign keywords
• opens each discovered video page to enrich search results with structured video metadata
• extracts visible video cards and channel-level signals
• parses public view, follower, publication-age, duration, thumbnail, description, and comment labels when available
• suppresses video rows when detail-page enrichment fails, so the default dataset avoids half-empty results
• scores each result for momentum and influencer relevance
• writes structured rows that can be scheduled, exported, or joined with other monitoring pipelines

Good Use Cases

• Influencer teams tracking creators who publish on Rumble
• Brand safety teams monitoring niche or emerging-platform mentions
• Media researchers following topics that move outside mainstream platforms
• Agencies building weekly creator intelligence reports
• Growth teams comparing creator momentum across repeat runs

Input

You can use either channels, queries, or both.

Rumble Channel URLs

Use known public Rumble channels:

[
  { "url": "https://rumble.com/c/Reuters", "label": "Reuters on Rumble" }
]

Search Queries

Use creator names, brand terms, topics, campaign keywords, or niche categories:

["technology news", "electric vehicles", "creator name"]

Lookback Days

Controls how strongly recent videos are scored. Older videos may still appear, but the recency component of momentumScore drops as videos fall outside the configured window.

Max Results per Input

Limits the number of enriched video or search-result rows returned per channel or query. The Actor may inspect extra candidates and suppress blocked detail pages so the final dataset stays clean.

Output

The Actor writes rows with entityType:

• channel: one row per channel page inspected
• video: videos detected from a channel page
• search_result: videos detected from Rumble search
• error: structured row explaining an input, network, blocked, not-found, or parse issue

Example row:

{
  "entityType": "search_result",
  "query": "technology news",
  "rank": 1,
  "channelName": "Example Creator",
  "videoTitle": "New technology policy update",
  "videoUrl": "https://rumble.com/v...",
  "views": 18400,
  "publishedText": "2 days ago",
  "momentumScore": 74,
  "influencerRelevanceScore": 61,
  "sourcePageUrl": "https://rumble.com/search/video?q=technology%20news",
  "warnings": null,
  "scrapedAt": "2026-05-18T12:00:00.000Z"
}

Field Notes

momentumScore is a lightweight 0-100 score based on recency, visible views, and comments.

influencerRelevanceScore combines visible channel size, verification, rank, and query-term matches. It is a prioritization signal, not an endorsement or audience-quality guarantee.

publishedAtApprox is approximate when Rumble shows relative labels such as "2 days ago". The original label is preserved in publishedText.

warnings explain remaining public data limitations. By default, video and search-result rows are only returned after successful detail-page enrichment. Rows skipped because detail enrichment failed are summarized in RUN_SUMMARY.suppressedEnrichment.

API Example

curl "https://api.apify.com/v2/acts/trovevault~rumble-creator-video-signal-monitor/runs?waitForFinish=120" \
  -X POST \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "queries": ["technology news"],
    "lookbackDays": 14,
    "maxResults": 1
  }'

Scheduling

Run the Actor daily or weekly with the same channels and queries. Save each run into a long-lived dataset using datasetId if you want one combined export table across scheduled runs.

Limitations

This Actor uses public Rumble pages. It does not log in, bypass access controls, or claim complete platform coverage. Search result completeness depends on Rumble's public search behavior. Some channel or video metrics may be hidden, delayed, localized, or absent from listing pages. When a value is not visible or not reliable enough to parse, the Actor returns null and adds a warning instead of inventing data.

For cloud runs, Residential Apify Proxy is recommended because Rumble may return HTTP 403 to plain datacenter traffic. Keep maxResults focused enough for the workflow you actually need.