Polish new Stats Traffic tab defaults and UTM card headers

[adalpari]

Description

Two small polish changes to the new stats screen:

1. Reduce default Traffic tab cards — Show only 4 cards by default (Today's Stats, Views, Most Viewed Posts & Pages, Locations) instead of 8, so the initial experience is less overwhelming.

2. Clean up UTM card column headers — Remove the redundant left column title (already visible in the category dropdown selector) and hide column headers entirely during loading state.

Testing instructions

Default cards:

1. Clear app data or log in to a site that has never configured stats cards
2. Navigate to Stats > Traffic tab

• Verify only 4 cards are shown: Today's Stats, Views, Most Viewed Posts & Pages, Locations
• Verify the remaining cards (Referrers, Authors, Clicks, etc.) can still be added via card configuration

UTM card headers:

1. Navigate to Stats > Traffic tab and add the UTM card if not visible
2. Observe the UTM card while it loads

• Verify no column headers are shown during the loading/shimmer state

[dangermattic]

	1 Warning
⚠️	PR is not assigned to a milestone.

Generated by 🚫 Danger

[adalpari]

@claude

[claude]

Claude finished @adalpari's task in 1m 32s —— View job

---

Code Review

• Gather context from PR description and changed files
• Review StatsCardType.kt changes
• Review UtmCard.kt changes
• Post review feedback

---

Clean, focused PR. Two small concerns worth flagging:

UtmCard.kt — Reusing stats_countries_views_header string

In LoadedContent, the right-aligned column header now directly uses R.string.stats_countries_views_header (line 199):

Text(
    text = stringResource(R.string.stats_countries_views_header),
    ...
)

This string is named after the Locations/Countries card. While the text value is just "Views" and is semantically correct for UTM too, borrowing a country-specific string creates a hidden coupling — if the Locations card ever renames or rephrases that string, the UTM card's header would silently change. A dedicated R.string.stats_utm_views_header (or a more generic R.string.stats_views_column_header) would be safer. That said, since the string value is generic ("Views"), this is a minor concern. Fix this →

StatsCardsConfigurationTest.kt — No explicit assertion on defaultCards() contents

StatsCardsConfigurationTest only checks that the default config's visibleCards equals defaultCards() — it doesn't assert which specific cards are in that list. A regression test that explicitly asserts the 4-card default set would make future changes to defaultCards() more visible and intentional. This is low priority but worth considering.

Everything else looks good

• Trimming defaultCards() from 8 → 4 cards is a clean, minimal change.
• Removing StatsListHeader from the loading/shimmer state is correct — column labels during loading are noise.
• The StatsListHeader import is properly cleaned up.
• Existing tests don't need updates since the affected test uses defaultCards() dynamically.
  | Branch

[adalpari]

UtmCard.kt — Reusing stats_countries_views_header string

In LoadedContent, the right-aligned column header now directly uses R.string.stats_countries_views_header (line 199):

Text(
    text = stringResource(R.string.stats_countries_views_header),
    ...
)

This string is named after the Locations/Countries card. While the text value is just "Views" and is semantically correct for UTM too, borrowing a country-specific string creates a hidden coupling — if the Locations card ever renames or rephrases that string, the UTM card's header would silently change. A dedicated R.string.stats_utm_views_header (or a more generic R.string.stats_views_column_header) would be safer. That said, since the string value is generic ("Views"), this is a minor concern. Fix this →

StatsCardsConfigurationTest.kt — No explicit assertion on defaultCards() contents

StatsCardsConfigurationTest only checks that the default config's visibleCards equals defaultCards() — it doesn't assert which specific cards are in that list. A regression test that explicitly asserts the 4-card default set would make future changes to defaultCards() more visible and intentional. This is low priority but worth considering.

These suggestions are not applicable

[wpmobilebot]

📲 You can test the changes from this Pull Request in Jetpack Android by scanning the QR code below to install the corresponding build.

	App Name	Jetpack Android
	Build Type	Debug
	Version	pr22789-f8008a7
	Build Number	1488
	Application ID	com.jetpack.android.prealpha
	Commit	f8008a7
	Installation URL	72mr7qdvhcnm8

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[wpmobilebot]

📲 You can test the changes from this Pull Request in WordPress Android by scanning the QR code below to install the corresponding build.

	App Name	WordPress Android
	Build Type	Debug
	Version	pr22789-f8008a7
	Build Number	1488
	Application ID	org.wordpress.android.prealpha
	Commit	f8008a7
	Installation URL	6nr5bko5an7a0

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[codecov]

Codecov Report

❌ Patch coverage is 12.50000% with 7 lines in your changes missing coverage. Please review.
✅ Project coverage is 37.34%. Comparing base (cf81ab8) to head (f8008a7).
⚠️ Report is 3 commits behind head on trunk.

Files with missing lines	Patch %	Lines
...a/org/wordpress/android/ui/newstats/utm/UtmCard.kt	0.00%	7 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##            trunk   #22789      +/-   ##
==========================================
- Coverage   37.34%   37.34%   -0.01%     
==========================================
  Files        2327     2327              
  Lines      124639   124637       -2     
  Branches    16892    16892              
==========================================
- Hits        46551    46547       -4     
- Misses      74351    74353       +2     
  Partials     3737     3737              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[nbradbury]

Looks good!