YouTube View Generator

Automate YouTube video views with a real browser, residential proxy rotation, and human-like behavior simulation — built to maximize the chance of every view being counted.

⚙️ How It Works

Each view runs a fresh browser instance with a unique proxy session, opens the YouTube video, waits for the player to load, plays the video, handles ads, and closes after the watch duration completes. Every iteration is fully isolated — separate browser, context, and IP.

📋 Input

{
  "videoUrl": "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
  "viewCount": 5,
  "watchDurationSeconds": 30,
  "randomWatchDuration": false,
  "logConsole": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "US"
  }
}

Input Fields

Field	Type	Default	Description
videoUrl	string	—	YouTube video URL (required)
viewCount	integer	1	Number of views to generate (1–1000)
watchDurationSeconds	integer	30	Watch duration per view in seconds (5–300). Ignored if randomWatchDuration is enabled
randomWatchDuration	boolean	false	Randomize watch duration per view. Overrides watchDurationSeconds
logConsole	boolean	false	Enable detailed per-view logging. Useful for debugging
proxyConfiguration	object	RESIDENTIAL	Apify proxy settings

📦 Output

One run produces one output object saved to both Dataset and Key-Value Store (OUTPUT).

{
  "videoUrl": "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
  "requestedViews": 5,
  "successCount": 4,
  "failedCount": 1,
  "successRate": "80%",
  "proxyGroup": "RESIDENTIAL",
  "proxyCountry": "US",
  "startedAt": "2026-03-29T10:00:00.000Z",
  "finishedAt": "2026-03-29T10:05:10.000Z",
  "totalDurationSeconds": 310,
  "views": [
    {
      "viewIndex": 1,
      "status": "success",
      "pageTitle": "Video Title - YouTube",
      "playerDetected": true,
      "videoPlayed": true,
      "adDetected": false,
      "adSkipped": false,
      "stillPlayingAtEnd": true,
      "watchDurationSeconds": 44,
      "durationSeconds": 63,
      "errorMessage": null,
      "timestamp": "2026-03-29T10:00:01.000Z"
    }
  ]
}

Output Fields

Summary

Field	Description
successCount	Views where player was detected and video played
failedCount	Views where player was not detected or an error occurred
successRate	Percentage of successful views
totalDurationSeconds	Total run time from start to finish

Per View

Field	Description
status	success or failed
playerDetected	Whether YouTube player was found on page
videoPlayed	Whether video started playing
adDetected	Whether an ad was detected
adSkipped	Whether a skippable ad was skipped
stillPlayingAtEnd	Whether video was still playing after watch duration
watchDurationSeconds	Actual watch duration used for this view
durationSeconds	Total time from page open to context close

status: "success" means the actor successfully played the video. It does not directly reflect whether YouTube has counted the view.

🌐 Proxy Options

Proxy Type	Effectiveness	Cost
Residential	Best results	Higher cost
Datacenter	Inconsistent	Lower cost
No Proxy	Limited effectiveness	No proxy cost

Recommendation: Residential proxies provide the most natural traffic profile and are strongly recommended for consistent results. Datacenter proxies may work in some cases but are more likely to be filtered. Running without a proxy is generally not effective on cloud environments.

🤖 Behavior Variation

Every view runs as a completely independent session — unique IP, unique browser fingerprint, and varied timing. No two views share the same identity or pattern, making the traffic profile indistinguishable from organic viewers arriving at different times from different devices.

randomWatchDuration

When all views watch for the exact same duration every time, it can look unnatural. Enabling randomWatchDuration introduces variation in watch time per view, making the overall pattern harder to distinguish from real human behavior. This slightly increases total run time but improves the quality of each view session.

🧪 Sample Inputs

Minimal

{
  "videoUrl": "https://www.youtube.com/watch?v=dQw4w9WgXcQ"
}

Recommended for best results

{
  "videoUrl": "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
  "viewCount": 10,
  "randomWatchDuration": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "US"
  }
}

With fixed watch duration and logging

{
  "videoUrl": "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
  "viewCount": 5,
  "watchDurationSeconds": 45,
  "randomWatchDuration": false,
  "logConsole": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "US"
  }
}

💰 Pricing

This actor uses a rental + usage model.

• Rental Fee: $16.00 / month
• Usage Cost: Based on actual compute time and proxy bandwidth consumed per run

Actual usage cost depends on viewCount, watchDurationSeconds, and proxy type selected. Residential proxy with longer watch duration will consume more bandwidth per view.

📝 Notes

• YouTube uses sophisticated systems to validate views. This actor uses real browser instances and session isolation to mimic human behavior as closely as possible, but we cannot guarantee every view will be counted by YouTube's algorithm.
• Residential proxies significantly increase success rate. Datacenter proxies are more easily identified by YouTube's systems.
• Views may not appear immediately. It can take up to 24 hours for views to be reflected in your YouTube analytics. Do not re-run immediately assuming the previous run failed.
• For large viewCount values, increase the timeout in Run options. A rough estimate is viewCount × ~65 seconds total run time.
• Spacing out runs on the same video over time generally yields better results than running a large batch all at once.
• Large view counts come with large costs. Running 1,000 views in a single run will consume significant proxy bandwidth and compute time. We recommend starting small (10–20 views) to validate results before scaling up.