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:
| Module | Purpose |
|---|---|
| AdSense Profile Manager | Account registration, multi-VPS tracking |
| Safe Revenue Calculator | Age-tier based limits, niche benchmarks |
| Risk Assessment Engine | 10 risk categories, automatic actions |
| Metrics Normalizer | Statistical distributions for natural patterns |
| Traffic Throttle Controller | Real-time limit enforcement |
| AdSense Safety Controller | Main 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 Age | Monthly Revenue Cap | Daily Impressions | Max CTR | Max RPM |
|---|---|---|---|---|
| 0-1 month | $50 - $150 | 1,000 - 5,000 | 1.0% | $15 |
| 1-3 months | $150 - $500 | 5,000 - 20,000 | 1.5% | $20 |
| 3-6 months | $500 - $2,000 | 20,000 - 80,000 | 2.0% | $25 |
| 6-12 months | $2,000 - $5,000 | 80,000 - 200,000 | 2.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)
| Niche | Typical CTR | Typical RPM |
|---|---|---|
| Finance | 0.5-1.5% | $20-50 |
| Technology | 1.0-2.0% | $10-30 |
| Health | 1.0-2.5% | $15-40 |
| Legal | 0.5-1.5% | $30-80 |
| Insurance | 0.5-1.2% | $40-100 |
| Real Estate | 0.8-1.8% | $20-50 |
| Education | 1.0-2.5% | $8-25 |
| Travel | 1.2-2.8% | $5-20 |
| Entertainment | 2.0-4.0% | $2-10 |
| News | 1.5-3.5% | $3-12 |
| Shopping | 1.5-3.0% | $5-20 |
| Automotive | 0.8-2.0% | $10-30 |
| Home & Garden | 1.2-2.5% | $8-25 |
| Sports | 1.5-3.0% | $3-15 |
| Gaming | 2.0-4.0% | $2-10 |
Risk Assessment Categories
The Risk Assessment Engine monitors 10 categories:
| Category | What It Detects | Severity Range |
|---|---|---|
| CTR Anomaly | Click rate above niche benchmark | LOW → CRITICAL |
| RPM Anomaly | Revenue per thousand above benchmark | LOW → HIGH |
| Traffic Spike | Sudden traffic increases | MEDIUM → HIGH |
| Revenue Spike | Sudden revenue increases | MEDIUM → CRITICAL |
| Geographic Mismatch | Traffic from unexpected regions | LOW → MEDIUM |
| Session Anomaly | Unusual session patterns | LOW → HIGH |
| Pattern Deviation | Repetitive behavior patterns | MEDIUM → HIGH |
| Account Age Mismatch | Metrics don't match account age | LOW → HIGH |
| Click Timing | Unnatural click timing patterns | LOW → CRITICAL |
| Repeat Visitor | Same visitors clicking repeatedly | MEDIUM → CRITICAL |
Automatic Actions
Based on risk level, the system takes automatic actions:
| Risk Level | Action | Description |
|---|---|---|
| NONE | Continue | Normal operation |
| LOW | Continue | Normal operation with monitoring |
| MEDIUM | Throttle | Reduce click probability by 50% |
| HIGH | Pause | Stop clicking, continue impressions |
| CRITICAL | Stop | Stop 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
- Create a GitHub Personal Access Token (PAT) with repo scope
- In each VPS instance, go to Settings → GitHub Sync
- Enter your PAT and repository URL
- 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:
- Dashboard: Click the red Emergency Stop button
- CLI:
python cli.py adsense emergency-stop - 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
| Endpoint | Method | Description |
|---|---|---|
/api/adsense-safety/account | GET | Get account configuration |
/api/adsense-safety/account | POST | Update account settings |
/api/adsense-safety/toggle | POST | Enable/disable protection |
/api/adsense-safety/metrics | GET | Get current metrics |
/api/adsense-safety/sync | POST | Sync with GitHub |
/api/adsense-safety/emergency-stop | POST | Emergency stop |
Related Documentation
- Traffic Generation - Campaign configuration
- Proxy Setup - Proxy configuration
- Device Birth Date System - Profile authenticity