Cliredas – Client Dashboard for Google Analytics (GA4)

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.

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.

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.

Yes.

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

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.

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.

Yes.

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

No.

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

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.

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.

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.

Yes.

The main KPI cards display previous-period percentage changes.

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

Cliredas currently includes:

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

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.

Yes.

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

Yes.

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

Yes.

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

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

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.

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.

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.

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

Cliredas uses that URL when generating the OAuth Redirect URI.

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.

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-a