Title: Cliredas &#8211; Client Dashboard for Google Analytics (GA4)
Author: vzisis
Published: <strong>20 Tháng 2, 2026</strong>
Last modified: 15 Tháng 11, 2026

---

Tìm kiếm plugin

![](https://ps.w.org/cliredas-analytics-dashboard/assets/banner-772x250.png?rev=
3466117)

![](https://ps.w.org/cliredas-analytics-dashboard/assets/icon-256x256.png?rev=3466117)

# Cliredas – Client Dashboard for Google Analytics (GA4)

 Bởi [vzisis](https://profiles.wordpress.org/vzisis/)

[Tải về](https://downloads.wordpress.org/plugin/cliredas-analytics-dashboard.1.12.0.zip)

 * [Chi tiết](https://vi.wordpress.org/plugins/cliredas-analytics-dashboard/#description)
 * [Đánh giá](https://vi.wordpress.org/plugins/cliredas-analytics-dashboard/#reviews)
 *  [Cài đặt](https://vi.wordpress.org/plugins/cliredas-analytics-dashboard/#installation)
 * [Nhà phát triển](https://vi.wordpress.org/plugins/cliredas-analytics-dashboard/#developers)

 [Hỗ trợ](https://wordpress.org/support/plugin/cliredas-analytics-dashboard/)

## Mô tả

Cliredas adds a clean, client-friendly Google Analytics 4 (GA4) reporting dashboard
directly inside the WordPress admin.

Give clients, editors, marketers, and site owners the GA4 metrics they need without
requiring them to navigate the full Google Analytics interface.

Cliredas is designed for WordPress agencies, freelancers, and site owners who want
simple Google Analytics reporting inside WordPress.

Connect an existing GA4 property through Google OAuth, choose the property you want
to report on, and view important website performance metrics from wp-admin.

#### A simple GA4 dashboard inside WordPress

Cliredas turns key Google Analytics 4 data into a focused WordPress dashboard.

Instead of sending clients or content teams into the full GA4 interface, you can
give them a simpler view of website performance directly inside WordPress.

The dashboard includes:

 * Sessions.
 * Total users.
 * Pageviews.
 * Average engagement time.
 * Previous-period percentage changes.
 * Sessions over time.
 * Total users over time.
 * Top-performing pages.
 * Device breakdown.
 * Traffic-source breakdown.
 * Report freshness status and last-good recovery during temporary outages.
 * An optional unbranded, plain-text weekly owner digest to one recipient.

This makes Cliredas useful when users need to understand website performance without
working through the full Google Analytics reporting interface.

#### Built for client reporting

Cliredas is especially useful for agencies and freelancers that manage WordPress
websites for clients.

Keep reporting inside the same WordPress admin area clients already use to manage
their website.

Use Cliredas to give clients a focused view of:

 * Overall website traffic.
 * Changes compared with the previous period.
 * Most-visited pages.
 * Traffic sources.
 * Desktop, mobile, and tablet usage.
 * Engagement trends.

Administrators can also optionally allow users with the Editor role to view the 
dashboard.

#### Compare performance over time

Dashboard KPI cards include previous-period percentage changes so users can quickly
see whether important metrics increased or decreased.

Available date ranges include:

 * Last 7 days.
 * Last 30 days.
 * This month.
 * Last month.
 * Last 90 days.
 * Year to date.
 * Custom inclusive dates, up to 366 days.

Calendar-based ranges such as This month and Last month use aligned comparison periods.

The main line chart can switch between Sessions over time and Total users over time.

#### See your top-performing pages

The Top Pages report shows up to 25 pages and includes:

 * Sessions.
 * Views.
 * Average engagement time.

Columns can be sorted to make it easier to identify high-traffic and high-engagement
content.

Top Pages sorting is accessible and persists across date-range changes and browser
visits.

#### Understand where visitors come from

Cliredas includes a traffic-source breakdown that groups GA4 traffic into useful
categories such as:

 * Organic Search.
 * Direct.
 * Referral.
 * Social.
 * Other.

Use this alongside the device report to get a quick picture of how visitors discover
and access the website.

#### See desktop, mobile, and tablet traffic

The device breakdown summarizes traffic across:

 * Desktop.
 * Mobile.
 * Tablet.

This gives clients and site owners a simple view of the devices visitors use without
requiring them to build reports in Google Analytics.

#### Export GA4 reports to CSV

Export the current dashboard date range as a CSV file.

The export includes the plugin’s built-in report blocks so analytics data can be
used for:

 * Client reporting.
 * Internal analysis.
 * Spreadsheets.
 * Reporting archives.
 * Further data analysis.

CSV exports identify sample or fallback data when applicable and include protection
against spreadsheet formula injection.

#### Guided GA4 setup

Cliredas includes a rerunnable GA4 Setup Assistant to help administrators configure
and troubleshoot the Google Analytics connection.

The setup flow helps with:

 * Public site URL configuration.
 * Google OAuth configuration.
 * Refresh-token health.
 * GA4 property access.
 * Property selection.

Protected diagnostics help identify common configuration problems without exposing
OAuth credentials, access tokens, refresh tokens, or raw Google API responses.

#### Connect Google Analytics 4 with OAuth

Cliredas connects to Google Analytics 4 through Google OAuth.

No service account is required.

To connect:

 1. Create or use Google OAuth credentials.
 2. Add the Client ID and Client Secret in Settings > Client Report.
 3. Add the Redirect URI shown by Cliredas to the Google Cloud Console.
 4. Connect Google Analytics through the OAuth consent flow.
 5. Select the GA4 property you want to display.
 6. Run the built-in diagnostics to verify token and property access.

After the connection is configured, Cliredas uses the Google Analytics APIs to retrieve
reporting data.

#### Built-in caching for faster reports

Google Analytics report data is cached for 15 minutes by default.

Caching helps:

 * Keep dashboard loading fast.
 * Reduce repeated Google API requests.
 * Avoid unnecessary requests when multiple users view the same reports.

Administrators can use Clear Cache to force fresh data to be fetched on the next
dashboard load.

#### Optional Editor access

By default, analytics configuration remains an administrative task.

Administrators can optionally allow users with the WordPress Editor role to view
the Client Report dashboard.

This can be useful for:

 * Marketing teams.
 * Content editors.
 * Client website managers.
 * Internal reporting teams.

#### Key features

 * Google Analytics 4 dashboard inside WordPress.
 * Client-friendly GA4 reporting.
 * Google OAuth connection.
 * No service account required.
 * Guided GA4 Setup Assistant.
 * OAuth, token, and property diagnostics.
 * GA4 property selection.
 * Sessions KPI.
 * Total users KPI.
 * Pageviews KPI.
 * Average engagement time KPI.
 * Previous-period percentage comparisons.
 * Last 7 days date range.
 * Last 30 days date range.
 * This month date range.
 * Last month date range.
 * Last 90 days date range.
 * Year-to-date and custom inclusive dates covering 1-366 days.
 * Sessions-over-time chart.
 * Total-users-over-time chart.
 * Top Pages report with up to 25 pages.
 * Sortable Top Pages columns.
 * Traffic-source reporting.
 * Device reporting.
 * CSV report export.
 * Built-in report caching.
 * Manual cache clearing.
 * Optional Editor dashboard access.

#### Who is Cliredas for?

**WordPress agencies**

Give clients a simpler way to see website performance without sending them into 
the full GA4 reporting interface.

**Freelancers**

Keep basic client analytics reporting inside the WordPress websites you manage.

**Site owners**

Check important Google Analytics metrics without switching between WordPress and
GA4 for routine reporting.

**Marketing and content teams**

Give eligible WordPress users access to traffic, content, source, device, and engagement
information alongside the site they manage.

#### Reporting dashboard, not a full analytics suite

Cliredas focuses on presenting useful GA4 reporting data inside WordPress.

It is designed for users who want a straightforward client-facing or site-management
dashboard rather than the full set of reports, explorations, configuration tools,
and analysis features available directly in Google Analytics.

Cliredas connects to an existing Google Analytics 4 property to retrieve reporting
data.

### External Services

Cliredas connects to Google services in order to authorize access, list available
Google Analytics properties, and retrieve GA4 reporting data.

Dashboard reporting communicates with Google APIs and your WordPress site. If an
administrator opts into the weekly digest or explicitly requests a test, the summary
and saved recipient are also passed to the site’s configured mail transport for 
delivery to that recipient. No separate Cliredas mail service is used.

When enabled and connected, the plugin sends requests to the following Google services:

 * Google OAuth 2.0 endpoints for authorization and token refresh:
    - https://accounts.google.com/
    - https://oauth2.googleapis.com/
 * Google Analytics Admin API for listing available properties:
    - https://analyticsadmin.googleapis.com/
 * Google Analytics Data API for retrieving reporting data:
    - https://analyticsdata.googleapis.com/

Data sent to Google can include:

 * OAuth Client ID.
 * OAuth Client Secret.
 * Authorization codes.
 * Refresh tokens.
 * Access tokens.
 * Selected GA4 property.
 * Requested date ranges.
 * Requested dimensions and metrics.

These requests are made when an authorized WordPress administrator connects Google
Analytics, explicitly runs connection diagnostics, or when the dashboard needs to
load or refresh analytics data, including WP-Cron background refreshes for reports
previously requested on the dashboard and fresh report retrieval for opt-in digests
or explicit test sends.

Google Privacy Policy:
 https://policies.google.com/privacy

## Ảnh màn hình

[⌊Client-friendly GA4 dashboard showing Sessions, Total users, Pageviews, Average
engagement time, trends, and Top Pages.⌉⌊Client-friendly GA4 dashboard showing Sessions,
Total users, Pageviews, Average engagement time, trends, and Top Pages.⌉[

Client-friendly GA4 dashboard showing Sessions, Total users, Pageviews, Average 
engagement time, trends, and Top Pages.

[⌊Google Analytics traffic-source and device reports showing how visitors discover
and access the website.⌉⌊Google Analytics traffic-source and device reports showing
how visitors discover and access the website.⌉[

Google Analytics traffic-source and device reports showing how visitors discover
and access the website.

[⌊Client Report settings with the GA4 Setup Assistant, OAuth configuration, diagnostics,
and property selection.⌉⌊Client Report settings with the GA4 Setup Assistant, OAuth
configuration, diagnostics, and property selection.⌉[

Client Report settings with the GA4 Setup Assistant, OAuth configuration, diagnostics,
and property selection.

[⌊Guided GA4 Setup Assistant showing successful OAuth, token-health, and property-
access diagnostics.⌉⌊Guided GA4 Setup Assistant showing successful OAuth, token-
health, and property-access diagnostics.⌉[

Guided GA4 Setup Assistant showing successful OAuth, token-health, and property-
access diagnostics.

## Cài đặt

 1.  Install Cliredas from Plugins > Add New, or upload the `cliredas-analytics-dashboard`
     folder to `/wp-content/plugins/`.
 2.  Activate the plugin.
 3.  Go to Client Report in the WordPress admin menu.
 4.  Open Settings > Client Report and launch the GA4 Setup Assistant.
 5.  Add your Google OAuth Client ID and Client Secret.
 6.  If the site is behind a public tunnel or reverse proxy, enter the public site 
     URL in Public OAuth base URL and save the settings.
 7.  In Google Cloud Console, add the Redirect URI shown by Cliredas as an Authorized
     redirect URI.
 8.  Click Connect Google Analytics and complete Google’s OAuth consent flow.
 9.  Select the GA4 property you want to use.
 10. Run the connection diagnostics to verify refresh-token health and property access.
 11. Open Client Report to view your Google Analytics dashboard.

## Hỏi đáp

### How do I compare trends?

Enable Compare with previous period on the Sessions/Users chart to use the comparison
dates shown by the KPI deltas. The chart aligns days from the start of each period
and shows actual dates in tooltips. Gaps indicate missing dates or days beyond a
shorter period. The checkbox resets on reload. The previous-period chart data table
works without JavaScript.

### How do custom dates and year-to-date compare?

Choose Custom dates, enter both dates, then Apply. Both endpoints count, the maximum
is 366 days, and future dates are rejected. Comparison uses the immediately preceding
equal-length period. Year to date includes January 1 through today and compares 
with the same calendar dates last year, clamping February 29 to February 28. The
five original presets keep their existing rules.

Date drafts do not change the displayed report or CSV until Apply succeeds. Current/
comparison dates appear in both dashboard and CSV. AJAX selections reset on reload;
the no-JavaScript form follows normal browser POST resubmission behavior. The Top
pages filter and saved sort continue working across date changes. Weekly digests
stay on Last 7 days.

The WordPress site timezone determines calendar selections. GA4 aggregates daily
data using its property reporting timezone; values are not re-bucketed. Historical
data may be empty or unavailable. Reload an obsolete relative period after midnight
before polling or CSV export. No date preference is stored; requested dates are 
sent to Google as reporting parameters using the existing connection.

### How does Top pages filtering work?

Filter Top pages searches the currently loaded first 25 rows by title or URL using
trimmed, case-insensitive text. It combines with sorting and makes no Google requests.
Clear filter or Escape removes the query; changing the reporting range or completing
a background refresh keeps it. Reloading starts with an empty filter. KPI totals,
report data, CSV contents and email digests are unchanged.

Zero activity, empty results, unmatched filters, unavailable blocks, sample data
and stale reports have distinct explanations. View chart data exposes exact dates,
Sessions and Total users even without JavaScript; traffic-source values remain in
their table. Without JavaScript, the current report remains readable but local filtering
and sorting are unavailable.

### Can I receive a weekly owner summary?

Yes. Under Settings > Client Report, save one recipient and explicitly enable Weekly
owner digest. It is disabled by default, including after upgrades. The initial recipient
defaults to the site admin email; later admin-email changes do not silently redirect
an enabled digest.

The unbranded plain-text email includes the four KPIs and comparisons, top five 
pages, device/source summaries, retrieval time, actual reporting/comparison dates,
and a dashboard link. Last 7 days includes the current day, which Google may still
be processing. No logo, attachments, tracking, or external email integration is 
added.

The schedule is Monday at 08:00 in the WordPress site timezone. Late execution is
allowed only during that Monday; missed Mondays are skipped without a backlog. WP-
Cron needs site requests or a configured cron runner.

Only complete real reports within the configured freshness window are sent. An expired
report is refreshed synchronously; failed, stale, partial, mock, and obsolete reports
are skipped. Settings shows the next run and the last weekly/test outcomes. A successful
outcome means handoff to the configured mail transport, not confirmed inbox delivery.
Uncertain interrupted mail attempts are not retried automatically.

Send test email sends once to the saved recipient even with weekly delivery disabled.
It does not enable or advance the weekly schedule. Save address changes first. Disable
digest removes future events and invalidates work still preparing. Mail already 
handed to a transport cannot be recalled.

The non-autoloaded cliredas_digest_settings option stores consent and recipient;
cliredas_digest_state stores bounded timestamps, scheduling/lease metadata, opaque
identifiers, and allow-listed outcomes. No message bodies, report payloads, recipient
addresses, or raw transport errors are copied into operational history. Digest audit
events share the existing 100-entry limit. Deactivation stops digest work; uninstall
removes owned options and events for each site.

### What does Cliredas do?

Cliredas displays key Google Analytics 4 reporting data inside the WordPress admin.

It provides a simplified GA4 dashboard with traffic KPIs, trends, top pages, traffic
sources, device information, previous-period comparisons, and CSV export.

### Can I view Google Analytics 4 inside WordPress?

Yes.

Cliredas connects an existing Google Analytics 4 property to WordPress and displays
key reporting data directly in wp-admin.

### Is Cliredas suitable for client reporting?

Yes.

Cliredas is designed to provide a simpler, client-friendly view of GA4 data inside
WordPress.

It can be useful for agencies and freelancers that want clients to see important
website metrics without navigating the full Google Analytics interface.

### Is Cliredas useful for WordPress agencies and freelancers?

Yes.

Agencies and freelancers can use Cliredas to keep basic GA4 reporting inside the
WordPress websites they manage for clients.

Administrators can also optionally allow WordPress Editors to view the reporting
dashboard.

### Does Cliredas connect to Google Analytics 4?

Yes.

Use Settings > Client Report to connect GA4 through Google OAuth and select the 
Google Analytics property you want to display.

### Do I need a Google Analytics service account?

No.

Cliredas uses Google OAuth rather than requiring a Google Analytics service account.

### Do I need an existing GA4 property?

Yes.

Cliredas retrieves reporting data from a Google Analytics 4 property. You connect
the plugin to Google through OAuth and then select an available GA4 property.

### Does Cliredas install Google Analytics tracking on my website?

Cliredas is focused on reporting from an existing Google Analytics 4 property.

You should already have GA4 measurement configured for the website whose analytics
you want to display.

### What Google Analytics metrics can I see in WordPress?

The dashboard includes:

 * Sessions.
 * Total users.
 * Pageviews.
 * Average engagement time.
 * Previous-period percentage changes.
 * Sessions or users over time.
 * Top pages.
 * Traffic sources.
 * Device categories.

### Can I compare the current period with the previous period?

Yes.

The main KPI cards display previous-period percentage changes.

Calendar-based ranges such as This month and Last month use aligned comparison periods.

### What date ranges are available?

Cliredas currently includes:

 * Last 7 days.
 * Last 30 days.
 * This month.
 * Last month.
 * Last 90 days.

### Can I see which pages receive the most traffic?

Yes.

The Top Pages table displays up to 25 pages and includes Sessions, Views, and Average
engagement time.

The table can be sorted by its report columns.

### Can I see where website traffic comes from?

Yes.

Cliredas includes a traffic-source report with categories such as Organic Search,
Direct, Referral, Social, and Other.

### Can I see mobile and desktop traffic?

Yes.

The device report shows a breakdown for desktop, mobile, and tablet traffic.

### Can I export GA4 data?

Yes.

Cliredas can export the current dashboard range to CSV, including the plugin’s built-
in reporting blocks.

### Can Editors see the Google Analytics dashboard?

Yes, if an administrator enables Editor access under Settings > Client Report.

### How often does Cliredas fetch Google Analytics data?

Each new GA4 report fetch (including background refreshes) includes one additional
daily trend request for the comparison dates. Cached reports reuse the result. If
the comparison request fails temporarily or the report was cached before 1.12.0,
the current chart remains available and the comparison can return on the next successful
refresh. CSV and weekly digest contents are unchanged.

Report data is fresh for 15 minutes by default. Expired reports display last-good
real data for up to 24 hours from retrieval, only for the same resolved dates and
connection, while one background refresh is pending. Freshness reflects retrieval
time, not Google’s data-processing completeness.

Fresh, Refreshing, and Stale labels include the last successful refresh in your 
site’s timezone. An open dashboard checks pending cached results every five seconds
for up to three minutes, pausing while hidden.

Background refresh depends on WP-Cron. If WP-Cron is disabled, configure a system
cron runner or use Clear Cache for a new synchronous load. Failures retain eligible
last-good data with a five-minute retry cooldown; detected permission or credential
loss hides retained reports.

The non-autoloaded cliredas_report_cache option retains at most 20 contexts. Expired
data is never served; daily cleanup removes inactive records. Clear Cache removes
fresh, retained, and legacy reports plus scheduled refreshes. Connection/access 
changes and deactivation invalidate report data and work; uninstall removes storage
and events per site. CSV metadata includes freshness and resolved dates.

### What is the GA4 Setup Assistant?

The Setup Assistant provides a guided workflow for connecting Cliredas to Google
Analytics.

It includes checks for public URL configuration, OAuth configuration, refresh-token
health, and GA4 property access.

The assistant can be run again later if you need to troubleshoot the connection.

### Why does Google block my redirect URI on a local domain?

Google OAuth redirect URIs must use an acceptable public domain.

For local development, use a public tunnel such as ngrok or a real public domain.

When using a tunnel, enter the tunnel’s public site URL in Public OAuth base URL,
save the settings, and copy the generated Redirect URI into Google Cloud Console.

### What if my WordPress site is behind a reverse proxy or tunnel?

Use the Public OAuth base URL setting to provide the public-facing site URL.

Cliredas uses that URL when generating the OAuth Redirect URI.

### Does Cliredas store Google OAuth credentials or tokens in WordPress?

Yes.

OAuth credentials and tokens are stored in the WordPress options table under the`
cliredas_settings` option.

The plugin does not display the saved Client Secret back in the settings interface.

Client secrets, refresh tokens, and access tokens use Sodium secretbox when available,
falling back to OpenSSL AES-256-GCM. Separate field/site keys are derived from WordPress
auth and secure-auth secret material. Existing plaintext values migrate automatically
during an administrator’s normal admin initialization.

If neither authenticated-encryption backend is available, plaintext compatibility
remains enabled and Settings displays a warning. Enable Sodium or OpenSSL AES-256-
GCM to migrate saved plaintext values.

Changing WordPress security salts or site context can make saved credentials unreadable.
Restore the original secret material and site context, or re-enter the Client Secret
and reconnect. Disconnect clears tokens but preserves credentials; explicit secret
clearing removes all three sensitive fields. Database restores and moves require
compatible secret material and site context.

Encryption protects stored database values, not a compromised WordPress installation,
runtime memory, or backups containing both the database and encryption material.
Keys and plaintext copies are not stored alongside ciphertext.

The latest connection diagnostic result is stored in user meta for the administrator
who ran it. The diagnostic record contains statuses, safe messages, a timestamp,
and a non-sensitive configuration fingerprint.

It does not contain credentials, tokens, or raw Google API responses.

### What do local diagnostics and audit history store?

Local diagnostics show credential-storage status, the available backend, access-
token expiry, refresh-token presence, and the latest retained refresh outcome without
making Google requests. Use Run diagnostics separately for remote health validation.

The non-autoloaded `cliredas_audit_log` option retains the latest 100 connection,
disconnect, secret-clearing, actual token-refresh, cache-clearing, CSV export, weekly
digest, and digest test outcomes. It stores only allow-listed event/outcome codes,
Unix timestamps, and actor IDs. It never stores URLs, report contents, recipients,
credentials, tokens, or raw error messages and sends no external telemetry.

Only administrators can view this history on the settings page. Uninstall removes
audit storage for each site.

### Where can I see release changes?

After an upgrade, administrators see a dismissible release announcement on the plugin
Dashboard and Settings pages only. Fresh installations do not receive an upgrade
announcement. Release notes remain available in a collapsible Settings section.

Dismissal is remembered per administrator, site, and release in `cliredas_dismissed_release_notices`
user meta. The non-autoloaded `cliredas_release_state` option tracks installed and
announced releases. Uninstall removes both records. Dismissing release news never
hides credential-recovery or connection warnings.

### Does Cliredas send my analytics data to another service?

Cliredas communicates with Google APIs and your WordPress site as described in the
External Services section. Administrator opt-in digest delivery and explicit test
sends also pass the saved recipient and summary to the site’s configured mail transport.

It does not send analytics reporting data to a separate Cliredas analytics service.

## Đánh giá

Không có đánh giá nào cho plugin này.

## Người đóng góp & Lập trình viên

“Cliredas – Client Dashboard for Google Analytics (GA4)” là mã nguồn mở. Những người
sau đã đóng góp vào plugin này.

Những người đóng góp

 *   [ vzisis ](https://profiles.wordpress.org/vzisis/)

[Dịch “Cliredas – Client Dashboard for Google Analytics (GA4)” sang ngôn ngữ của bạn.](https://translate.wordpress.org/projects/wp-plugins/cliredas-analytics-dashboard)

### Muốn tham gia phát triển?

[Duyệt code](https://plugins.trac.wordpress.org/browser/cliredas-analytics-dashboard/),
check out [SVN repository](https://plugins.svn.wordpress.org/cliredas-analytics-dashboard/),
hoặc theo dõi [nhật ký phát triển](https://plugins.trac.wordpress.org/log/cliredas-analytics-dashboard/)
qua [RSS](https://plugins.trac.wordpress.org/log/cliredas-analytics-dashboard/?limit=100&mode=stop_on_copy&format=rss).

## Nhật ký thay đổi

#### 1.12.0

 * Added an optional previous-period overlay for Sessions and Total users with actual
   dates in tooltips.
 * Added an accessible previous-period trend table and cached comparison trend data.

#### 1.11.0

 * Added custom inclusive dates covering 1–366 days and year-to-date for existing
   metrics.
 * Added shared date validation, exact current/comparison labels and CSV metadata.
 * Preserved preset comparisons, freshness limits, credentials and weekly digest
   settings.

#### 1.10.0

 * Added local Top pages filtering by title or URL, composing with saved sorting
   without changing report data or CSV exports.
 * Added explicit zero-activity, empty and unavailable states across dashboard blocks.
 * Added an expandable chart data table, keyboard-accessible scrolling, visible 
   focus and screen-reader feedback.
 * Improved loading, recovery and access-change handling while preserving freshness
   and retention limits.

#### 1.9.0

 * Added an administrator opt-in weekly owner digest, disabled by default, for one
   saved recipient.
 * Added an unbranded plain-text summary with KPIs/comparisons, the top five pages,
   devices, sources, and a dashboard link.
 * Added fresh-only GA4 retrieval: incomplete, stale, sample, unavailable, and obsolete
   reports are never emailed.
 * Added local Monday 08:00 scheduling with DST/timezone reconciliation, duplicate
   prevention, and missed-Monday handling.
 * Added protected test-send/disable actions, next-run and outcome status, and bounded
   non-sensitive audit events.
 * Added digest deactivation and per-site uninstall cleanup.

#### 1.8.0

 * Added last-good GA4 report recovery for up to 24 hours while expired data refreshes
   in the background.
 * Added Fresh, Refreshing, and Stale status with the last successful refresh time
   in the site timezone.
 * Added automatic dashboard updates when a pending background refresh completes.
 * Isolated cached reports by site, connection, property, timezone, and resolved
   reporting dates.
 * Added refresh locking, failure cooldowns, bounded storage, and scheduled cleanup.
 * Added freshness and resolved-date metadata to CSV exports, with explicit unavailable
   states for missing data.
 * Extended Clear Cache, connection changes, deactivation, and uninstall to invalidate
   retained reports and scheduled refreshes.

#### 1.7.0

 * Added authenticated encryption for OAuth secrets and tokens with automatic legacy
   migration.
 * Added local storage/token diagnostics and administrator-only audit history capped
   at 100 events.
 * Replaced raw upstream OAuth error feedback with predefined corrective messages.
 * Added dismissible administrator-only release announcements and local release 
   notes.

#### 1.6.0

 * Added a rerunnable GA4 Setup Assistant to the plugin settings page.
 * Added protected diagnostics for OAuth URL configuration, token health, and GA4
   property access.
 * Consolidated settings-page token and property requests through the shared GA4
   API client.

#### 1.5.0

 * Added accessible sorting for every Top Pages column.
 * Top Pages sorting now persists across date-range changes and browser visits.

#### 1.4.0

 * Added protected CSV export for all built-in dashboard report blocks.
 * CSV exports identify sample or fallback data and protect against spreadsheet 
   formula injection.

## Meta

 *  Phiên bản **1.12.0**
 *  Cập nhật lần cuối **2 ngày trước**
 *  Số lượt cài đặt **Ít hơn 10**
 *  Phiên bản WordPress ** 6.0 hoặc cao hơn **
 *  Đã kiểm tra lên đến **7.1.4**
 *  Phiên bản PHP ** 7.4 hoặc cao hơn **
 *  Ngôn ngữ
 * [English (US)](https://wordpress.org/plugins/cliredas-analytics-dashboard/)
 * Thẻ
 * [analytics](https://vi.wordpress.org/plugins/tags/analytics/)[ga4](https://vi.wordpress.org/plugins/tags/ga4/)
   [google analytics](https://vi.wordpress.org/plugins/tags/google-analytics/)[google analytics dashboard](https://vi.wordpress.org/plugins/tags/google-analytics-dashboard/)
   [WordPress analytics](https://vi.wordpress.org/plugins/tags/wordpress-analytics/)
 *  [Nâng cao](https://vi.wordpress.org/plugins/cliredas-analytics-dashboard/advanced/)

## Đánh giá

Chưa có đánh giá nào được gửi.

[Your review](https://wordpress.org/support/plugin/cliredas-analytics-dashboard/reviews/#new-post)

[Xem tất cả đánh giá](https://wordpress.org/support/plugin/cliredas-analytics-dashboard/reviews/)

## Những người đóng góp

 *   [ vzisis ](https://profiles.wordpress.org/vzisis/)

## Hỗ trợ

Có điều gì muốn nói? cần giúp đỡ?

 [Xem diễn đàn hỗ trợ](https://wordpress.org/support/plugin/cliredas-analytics-dashboard/)