Beardo Multisite Analytics for GA4

1.8.2

• Docs: The Instructions tab now walks through the Google Auth Platform steps needed to connect: fill in Branding (home page, privacy policy link and the site’s authorized domain), then publish the app. Leaving the app in Testing mode blocks sign-in with “Error 403: access_denied” for accounts that are not test users, and sign-ins expire after 7 days.
• Docs: The Instructions tab explains the “Google hasn’t verified this app” screen, with new troubleshooting entries for it and for Google asking for an app domain or privacy policy before publishing.

1.8.1

• Security: A site can only use a GA4 property that has a web stream for the site’s own domain. Before this, a multisite site admin could pick another subsite’s property from the network account and read its analytics. The check runs when the property is saved and again on every report, so properties saved before this release must match too.
• Security: The development-only tools/lint.php script now exits unless it is run from the command line.
• Improvement: The property list only shows properties whose web stream matches the site, on single-site installs as well as multisite. If none match, a notice explains how to add the site’s domain in Google Analytics.
• New: beardo_ga4_require_domain_match, beardo_ga4_site_hosts and beardo_ga4_property_allowed_for_site filters, for staging copies and mapped domains.
• Improvement: The network Properties tab looks up web stream domains for all properties, not just the page on screen, shows progress while it runs, and says when it has finished.
• Fix: With more than 10 GA4 properties, some were skipped when checking web-stream domains, so after a Re-sync a single site could lose its own property from the dropdown.
• Fix: On single site the domain lookup could not run when an admin customizer hid WordPress notices, leaving the property list empty. The lookup status and property box messages no longer use notice markup.
• Fix: The network Subsites tab and its CSV export no longer show a blocked property (for example one saved before this release that belongs to another site) as connected. Those rows now say “Not connected” and why.
• Fix: The subsite settings page no longer shows “No GA4 properties found” beside the domain-match notice when the account has properties but none for this site.

1.8.0

• New: Print / PDF export for the analytics page. A new Print Report button (or Ctrl+P / Cmd+P) produces a branded, light-theme report ready to print or save as PDF: site logo, name and tagline, the active date range, and the generation date. Admin menus, controls, and floating widgets from other plugins (such as chat buttons) are hidden. Designed to fit on one page for the default 30-day view, on paper as well as PDF.
• New: Charts are repainted in the light theme when printing, even when the admin is in dark mode, and restored afterwards.
• New: beardo_ga4_report_footer filter to change or remove the attribution line at the bottom of the printed report.
• Improvement: The site logo now falls back to the site icon when the custom logo image has been deleted (applies to the printed report and to error notification emails).
• Fix: The Traffic Sources chart gave its 7th source (e.g. Paid Search) the same color as the 1st. It now uses all 7 palette colors.
• Fix: Error notification emails for network-level errors no longer look up the site logo from a nonexistent site.

1.7.4

• New: Dark mode support. The settings, instructions, and analytics screens now draw their colors from a plugin-owned CSS custom property layer (--ga4-*) with light defaults, so a dark admin theme can re-color the entire plugin by overriding tokens. In stock WordPress admin nothing changes visually.
• New: Charts are theme-aware. Chart.js now reads its colors from the same token layer at every render, so graph text, gridlines, and series colors follow the active theme instead of being locked to hardcoded values.
• Improvement: The chart series palette was replaced with a 7-color colorblind-validated palette anchored to the WordPress admin blue, readable in both light and dark modes. The previous palette used a legacy blue that matched no current WordPress color scheme.
• Improvement: Status badges on the settings screens now use colors derived from the WordPress admin palette rather than unrelated Bootstrap alert colors.
• Maintenance: Consolidated three duplicate category-chart renderers into one, and moved the remaining inline styles on the settings page into stylesheet classes.

1.7.3

• New: Property sync failures are no longer silent. If listing your GA4 properties fails (e.g. the Google Analytics Admin API is disabled, missing permissions, expired connection, or rate limiting), the settings screens now show an actionable error notice explaining exactly what to fix — including a direct link to enable the Admin API when that is the cause. The stored error is cleared automatically on the next successful sync.
• New: The Re-sync button is now also available on single-site installs (in the Dashboard Property box), so single-site users can refresh their property list without reconnecting.
• Improvement: The empty property list now distinguishes “not synced yet” from “synced, but this Google account has no GA4 properties”, with guidance for each case.
• Docs: Updated the Instructions tab for Google’s current Cloud Console — the “OAuth consent screen” is now “Google Auth Platform”, with new setup steps (test users for apps in Testing mode, client secret shown only at creation) and two new troubleshooting entries (“Access blocked” and refresh tokens expiring after 7 days in Testing mode).
• Compatibility: Tested up to WordPress 7.1. Internal admin screen detection now uses the page hooks WordPress itself returns at menu registration (instead of hardcoded screen IDs), and deprecated patterns were removed for forward compatibility.
• Fix: The security headers (Content-Security-Policy and friends) on the plugin’s admin screens were silently never sent — they were attached to a hook that fires before WordPress identifies the current screen. They are now sent reliably on exactly the plugin’s own screens.
• Fix: The admin Content-Security-Policy now allows data: fonts, which admin icon-font CSS relies on (previously it would have blocked them once the headers actually applied).
• Maintenance: Regenerated the translation template (.pot); it was stale and covered only about a third of the plugin’s translatable strings.

1.7.2

• Fix: The “Clear Cache” button on single-site installs did nothing — its click handler was only bound to the multisite button’s element id. Both buttons are now handled.
• New: Dashboard reports now exclude GA4 ghost/referral spam (fake hits sent with a foreign or blank hostname, e.g. “trafficheap.cc”) by restricting every report to each GA4 property’s real hostnames. Those hostnames are fetched automatically from the property’s GA4 data streams (so it works on single-site and domain-mapped installs); if they can’t be determined, reports are left unfiltered rather than blanked. Overridable via the beardo_ga4_report_hostnames and beardo_ga4_enable_report_hostname_filter filters.