Device Birth Date System

A major V10 enhancement to profile authenticity: each device now has a synchronized "digital DNA" where device age determines Chrome version history, cookie ages, and browsing history.

Why Device Age Matters

Google's detection systems look for consistency signals between device age and digital footprint:

Device Age Tiers (GA4 Optimized)

Why These Percentages? These distributions match real-world device age patterns observed in Google Analytics 4 data, making your traffic appear natural.

How It Works

1. Device Birth Date

Each profile gets a birth date based on its age tier, set in the past according to the tier range.

2. Initial Chrome Version

The Chrome version that was available at the device's birth date is assigned as the initial version.

3. Chrome Update History

A complete trail of browser updates from birth to current date is generated, simulating realistic update patterns.

4. Cookie Birth Date

Cookies are created with timestamps shortly after device setup, matching when a real user would first visit sites.

5. Bookmark Ages

Bookmarks are spread across the device lifetime, not all created at once.

6. History Start Date

Browsing history begins at device birth, not before.

Example: Legacy Device (4 Years Old)

{
  "device_age_tier": "legacy_device",
  "device_birth_date": "2022-04-23",
  "device_age_days": 1368,
  "initial_chrome_version": "121.0.6167.85",
  "current_chrome_version": "145.0.7612.55",
  "total_chrome_updates": 26,
  "cookie_birth_date": "2022-04-28",
  "bookmark_creation_dates": ["2022-05-15", "2022-09-03", "2023-02-18"]
}

Dashboard Integration

Viewing Device Age Stats

1. Open the KeLAAX dashboard
2. Navigate to Profiles → Instance Stats
3. View the Device Age Distribution chart

CLI Commands

# View Device Age stats for an instance
python cli.py profiles stats --instance 1

# Output:
#   Device Age Distribution:
#     new_device     :  327 ( 15.6%) ███░░░░░░░░░░░░░░░░░
#     recent_device  :  549 ( 26.1%) █████░░░░░░░░░░░░░░░
#     mature_device  :  596 ( 28.4%) █████░░░░░░░░░░░░░░░
#     aging_device   :  410 ( 19.5%) ███░░░░░░░░░░░░░░░░░
#     legacy_device  :  218 ( 10.4%) ██░░░░░░░░░░░░░░░░░░

API Endpoint

Best Practices

• ✅ Let the system auto-distribute - The GA4-optimized percentages are carefully calibrated
• ✅ Use with Cookie/History Generation - Device Birth Date works best with backdated cookies enabled
• ✅ Monitor distribution - Check your dashboard to ensure natural distribution
• ❌ Don't override tiers manually - This breaks the natural distribution