Automattic / Automattic/jetpack

Feature Request: Jetpack Stats - Exclude Chrome Lighthouse insights visits

Open
#40,374 0 comments 0 reactions 0 assignees View on GitHub
[Feature] Stats Data [Plugin] Jetpack [Pri] Normal Customer Report [LEGACY] Enhancement Triaged
Dominant language
PHP
Stars
1.8k
Forks
898
Avg merge
1d 18h
Merged PRs (30d)
774

Description

### Impacted plugin

Jetpack

### What

Exclude Chrome Lighthouse insights visits from Jetpack Stats

### How

"Chrome Lighthouse" is no longer included in the user agent, see https://github.com/GoogleChrome/lighthouse/issues/14917#issuecomment-1480328571, so we can't rely on it to filter out traffic.

@kangzj suggested creating some sort of bot detecting feature to exclude Chrome Lighthouse.
Internal reference: [9303-gh-Automattic/jpop-issues/](https://github.com/Automattic/jpop-issues/issues/9303)

Contributor guide

Open the contributing guide

Research direction

Start by locating the Jetpack Stats traffic-filtering entry point and review the linked Chrome Lighthouse discussion and internal reference. Done means Lighthouse insights visits are reliably excluded despite the missing user-agent marker, with the detection approach and validation criteria established.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
analytics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.