DocumentationFeaturesAdSense Safety Intelligence
Features

AdSense Safety Intelligence

Complete guide to the V10 AdSense Safety Intelligence System for account protection

15 min readUpdated January 20, 2026

AdSense Safety Intelligence System

Complete account protection system that prevents AdSense accounts from triggering invalid traffic detection, ads limits, or suspension. Supports multi-VPS coordination through GitHub database synchronization.


Overview

The AdSense Safety Intelligence System consists of 6 interconnected modules:

ModulePurpose
AdSense Profile ManagerAccount registration, multi-VPS tracking
Safe Revenue CalculatorAge-tier based limits, niche benchmarks
Risk Assessment Engine10 risk categories, automatic actions
Metrics NormalizerStatistical distributions for natural patterns
Traffic Throttle ControllerReal-time limit enforcement
AdSense Safety ControllerMain orchestrator

Quick Start

Step 1: Register Your AdSense Account

In the dashboard, navigate to Ads Click and enter:

  • Publisher ID: Your pub-ID (e.g., pub-8435519351667682)
  • Account Age: When your AdSense account was created
  • Niche: Select from 15 supported niches
  • Geographic Tier: Your primary traffic tier

Step 2: Enable Protection

Toggle AdSense Safety Protection to ON. This automatically activates when any Ads Click instance is enabled.

Step 3: Monitor Metrics

The dashboard shows:

  • Today's Revenue vs. Daily Cap
  • Current CTR and RPM
  • Risk Score (NONE → CRITICAL)
  • Remaining safe clicks

Safe Revenue Limits by Account Age

Account AgeMonthly Revenue CapDaily ImpressionsMax CTRMax RPM
0-1 month$50 - $1501,000 - 5,0001.0%$15
1-3 months$150 - $5005,000 - 20,0001.5%$20
3-6 months$500 - $2,00020,000 - 80,0002.0%$25
6-12 months$2,000 - $5,00080,000 - 200,0002.5%$30
12+ months$5,000+200,000+3.0%$35

Warning: These are MAXIMUM safe limits. The system automatically calculates lower limits based on your specific niche and geographic tier.


Supported Niches (15)

NicheTypical CTRTypical RPM
Finance0.5-1.5%$20-50
Technology1.0-2.0%$10-30
Health1.0-2.5%$15-40
Legal0.5-1.5%$30-80
Insurance0.5-1.2%$40-100
Real Estate0.8-1.8%$20-50
Education1.0-2.5%$8-25
Travel1.2-2.8%$5-20
Entertainment2.0-4.0%$2-10
News1.5-3.5%$3-12
Shopping1.5-3.0%$5-20
Automotive0.8-2.0%$10-30
Home & Garden1.2-2.5%$8-25
Sports1.5-3.0%$3-15
Gaming2.0-4.0%$2-10

Risk Assessment Categories

The Risk Assessment Engine monitors 10 categories:

CategoryWhat It DetectsSeverity Range
CTR AnomalyClick rate above niche benchmarkLOW → CRITICAL
RPM AnomalyRevenue per thousand above benchmarkLOW → HIGH
Traffic SpikeSudden traffic increasesMEDIUM → HIGH
Revenue SpikeSudden revenue increasesMEDIUM → CRITICAL
Geographic MismatchTraffic from unexpected regionsLOW → MEDIUM
Session AnomalyUnusual session patternsLOW → HIGH
Pattern DeviationRepetitive behavior patternsMEDIUM → HIGH
Account Age MismatchMetrics don't match account ageLOW → HIGH
Click TimingUnnatural click timing patternsLOW → CRITICAL
Repeat VisitorSame visitors clicking repeatedlyMEDIUM → CRITICAL

Automatic Actions

Based on risk level, the system takes automatic actions:

Risk LevelActionDescription
NONEContinueNormal operation
LOWContinueNormal operation with monitoring
MEDIUMThrottleReduce click probability by 50%
HIGHPauseStop clicking, continue impressions
CRITICALStopStop all traffic, enter cooldown

Multi-VPS Architecture

For users running KeLAAX on multiple VPS instances:

┌─────────────────────────────────────────────────────────────────┐
│                   CENTRALIZED GITHUB DATABASE                    │
│                   (Single Source of Truth via PAT)               │
├─────────────────────────────────────────────────────────────────┤
│  data/adsense/                                                   │
│  ├── accounts/{pub-id}.json         ← Account profiles          │
│  ├── daily_metrics/{date}/{pub-id}  ← Aggregated metrics        │
│  ├── vps_contributions/{date}/{pub-id}/{vps-id}.json            │
│  └── throttle/{date}/{pub-id}/{vps-id}.json                     │
└─────────────────────────────────────────────────────────────────┘
                              ▲
           ┌──────────────────┼──────────────────┐
           │                  │                  │
     ┌─────┴─────┐      ┌─────┴─────┐      ┌─────┴─────┐
     │   VPS 1   │      │   VPS 2   │      │   VPS 3   │
     │  London   │      │  New York │      │  Tokyo    │
     └───────────┘      └───────────┘      └───────────┘

Setting Up Multi-VPS

  1. Create a GitHub Personal Access Token (PAT) with repo scope
  2. In each VPS instance, go to SettingsGitHub Sync
  3. Enter your PAT and repository URL
  4. Enable Auto-Sync

All VPS instances will now coordinate their traffic to stay within safe limits.


Emergency Stop

If you suspect an issue, use Emergency Stop:

  1. Dashboard: Click the red Emergency Stop button
  2. CLI: python cli.py adsense emergency-stop
  3. API: POST to /api/adsense-safety/emergency-stop

This immediately stops all ad clicking across ALL connected VPS instances.


Best Practices

✅ Do This

  • Start with conservative limits (below the maximums)
  • Use the 30-day ramp-up period for new accounts
  • Monitor the Risk Score daily
  • Keep geographic distribution consistent
  • Use residential proxies for ad traffic

❌ Avoid This

  • Pushing to maximum limits immediately
  • Running during unusual hours for your niche
  • Mixing traffic from incompatible geolocations
  • Ignoring HIGH or CRITICAL risk warnings
  • Disabling the safety system manually

API Reference

EndpointMethodDescription
/api/adsense-safety/accountGETGet account configuration
/api/adsense-safety/accountPOSTUpdate account settings
/api/adsense-safety/togglePOSTEnable/disable protection
/api/adsense-safety/metricsGETGet current metrics
/api/adsense-safety/syncPOSTSync with GitHub
/api/adsense-safety/emergency-stopPOSTEmergency stop

Related Documentation

Was this helpful?

Need more help?