Rumble Creator & Video Signal Monitor

Rumble Creator & Video Signal Monitor turns public Rumble channels and search queries into structured creator, video, and momentum rows. It is built for influencer discovery, brand monitoring, media research, emerging-platform coverage, and weekly reporting workflows that already track YouTube, TikTok, Instagram, podcasts, newsletters, or mainstream media but also need Rumble coverage.

Give the actor Rumble channel URLs, Rumble search queries, or both. It returns rows with entityType, channelName, videoTitle, videoUrl, visible view and follower signals, search result ranks, recency labels, momentumScore, influencerRelevanceScore, warnings, and timestamps.

Why use this actor

• Monitor Rumble creators and topic searches without manual page checks.
• Convert public channel and video pages into exportable Apify dataset rows.
• Rank videos and search results with lightweight momentum and influencer relevance scores.
• Keep warning fields and RUN_SUMMARY diagnostics so missing public values are explicit.
• Schedule repeat runs for the same channels or keywords and append results with datasetId.
• Use runId to connect Rumble monitoring with wider creator, media, or brand-safety workflows.

What it collects

Output	Meaning
entityType	channel, video, search_result, or error.
query / rank	Search query and rank for search-result rows.
channelName / channelUrl	Public channel identity when visible.
videoTitle / videoUrl	Public video metadata and URL.
views, publishedText, durationText	Visible video signals when available.
momentumScore	0-100 prioritization score based on recency, views, and comments.
influencerRelevanceScore	0-100 signal based on channel size, verification, rank, and query match.
sourcePageUrl	Public page used for the row.
warnings	Missing, blocked, or approximate data notes.
scrapedAt	Timestamp when the row was created.

Use cases

• Influencer discovery: track creators who publish on Rumble and compare repeat-run momentum.
• Brand monitoring: watch brand, product, executive, or campaign keywords on an emerging video platform.
• Media research: follow topics that may move outside mainstream social platforms.
• Agency reporting: produce weekly rows for creator intelligence, niche coverage, and content trend reports.
• Brand safety review: identify videos or channels that deserve manual inspection before sponsorship or placement decisions.

How to use it

1. Add one or more Rumble channel URLs in channelUrls, search queries, or both.
2. Set lookbackDays to shape the recency component of momentumScore.
3. Keep maxResults focused for the workflow you actually need.
4. Enable Apify Proxy if Rumble blocks plain datacenter traffic.
5. Review rows together with warnings and the run-level RUN_SUMMARY.

Input examples

Channel monitoring

{
  "channelUrls": [
    { "url": "https://rumble.com/c/Reuters", "label": "Reuters on Rumble" }
  ],
  "lookbackDays": 14,
  "maxResults": 10,
  "runId": "weekly-rumble-channel-watch"
}

Search monitoring

{
  "queries": ["technology news", "electric vehicles"],
  "lookbackDays": 14,
  "maxResults": 20
}

Input reference

Field	Required	Description
channelUrls	No	Public Rumble channel URLs to inspect.
queries	No	Creator names, brand terms, topics, campaign keywords, or niche categories to search.
lookbackDays	No	Recency window used for momentum scoring.
maxResults	No	Maximum enriched rows per input.
proxyConfiguration	No	Apify Proxy settings for blocked or rate-limited public pages.
datasetId	No	Existing dataset to append rows into.
runId	No	Workflow identifier copied into run metadata.

Output example

{
  "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"
}

API usage

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

How scoring works

momentumScore is a lightweight 0-100 prioritization score based on recency, visible views, and comments. influencerRelevanceScore combines visible channel size, verification, result rank, and query-term matches. These fields help sort review queues; they are not endorsements, audience-quality guarantees, or brand-safety certifications.

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

Limitations

• The actor uses public Rumble pages only. It does not log in or bypass access controls.
• Search completeness depends on Rumble's public search behavior at run time.
• Some channel, video, follower, comment, or view metrics may be hidden, delayed, localized, or absent.
• When a value is not visible or reliable enough to parse, the actor returns null and warnings instead of inventing data.
• Video and search-result rows are normally returned after successful detail-page enrichment so the default dataset avoids half-empty rows.
• Residential Apify Proxy is recommended for cloud runs because Rumble may return HTTP 403 to plain datacenter traffic.

Troubleshooting

Problem	What to try
HTTP 403 or many blocked rows	Enable Apify Proxy, preferably residential, and keep maxResults focused.
Search returns fewer rows than expected	Try broader or alternate query wording and check Rumble search manually.
Video rows are missing	Detail-page enrichment may have failed; check RUN_SUMMARY.suppressedEnrichment.
Scores look low	Increase lookbackDays or use more specific creator/topic queries.
Repeated monitoring is hard to compare	Schedule the same input and append rows with datasetId or a stable runId.

FAQ

Does this actor scrape private Rumble data?
No. It uses public pages only.

Can I monitor both channels and searches?
Yes. Provide channelUrls, queries, or both in the same run.

Why are some metrics null?
The metric was not visible or parseable with enough confidence on the public page.

Are the momentum scores authoritative?
No. They are sorting signals for review, not proof of influence or brand safety.

Can I schedule weekly reports?
Yes. Use Apify schedules and keep input stable across runs.

Should I use a proxy?
For cloud runs, yes if you see blocked pages or HTTP 403 responses.

Can I export rows to BI or Sheets?
Yes. Use Apify dataset exports, API, integrations, or webhooks.

Related actors

• Influencer Pricing Calculator for rate benchmarking after creator discovery.
• Mobile Apps Reviews, Downloads and Data for app-market signal monitoring.
• Competitor Ad Angle Analyzer for paid creative intelligence workflows.

Changelog

• 0.1: Initial TroveVault release with Rumble channel/search inputs, video enrichment, momentum scoring, proxy support, datasetId, and runId.

Feedback and support

Open an issue on the actor page with the input JSON, run ID, blocked URL or query, and the row you expected to see.