google / google/site-kit-wp

Format of Y-axis on Page CTR within AdSense chart is incorrect

Open
#8,371 0 comments 0 reactions 0 assignees View on GitHub
Module: AdSense Type: Enhancement
Dominant language
JavaScript
Stars
1.4k
Forks
383
Avg merge
4d 14h
Merged PRs (30d)
77

Description

## Bug Description

On a site with AdSense connected but has zero revenue, the chart for the Y axis of the Page CTR shows data formatted as 2,000%, 4000%, etc. When a site has data, the format is correct, i.e., 10%. It's only a minor issue, but I feel the format of the Y-axis on zero data should be the same as a site with AdSense revenue.

You can see the two screenshots below for an example:

Site with AdSense revenue

![image](https://github.com/google/site-kit-wp/assets/73545194/1d3825a9-30c2-4aac-84b5-3f93faa270c3)

Site with no AdSense revenue

![image](https://github.com/google/site-kit-wp/assets/73545194/833ed3d6-69f0-4b95-9a98-77f3b9edb0ca)

## Steps to reproduce

1. Set up AdSense on a site that has zero data.
2. Go to the chart on the dashboard and click on the Page CTR tab
3. Observe the Y-axis format, i.e 2,000%

---------------

_Do not alter or remove anything below. The following sections will be managed by moderators only._

## Acceptance criteria

*

## Implementation Brief

* [ ]

### Test Coverage

*

## QA Brief

*

## Changelog entry

*

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue by opening the AdSense chart for a site with zero revenue and selecting the Page CTR tab, then compare its Y-axis labels with a site that has revenue. Locate the Page CTR chart entry point and update the formatting so zero-data percentages match the normal display; verify both scenarios manually.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
analytics, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.