v1.1.0

Statnive 1.1.0 — Ask me! Advisor

The headline of 1.1.0 is Ask me! — a new admin tab that flips the dashboard on its head. Instead of asking the owner to find the chart that matters, Ask me! asks them what they want to know. 116 hand-written questions across 10 categories; 63 answer in one click today; the remainder render a Coming soon card on the v1.2 + Growth v2 timeline.

The companion launch post walks through the design and shows the screenshots: Meet Ask me!: 116 questions about your WordPress traffic, answered in seconds.

What’s new

Ask me! Advisor (Statnive → Ask me!)

A new admin page with 11 in-page tabs — one per category (Traffic, Real-time, Pages, Referrers, Campaigns, Geography, Devices, Engagement, Revenue, Events) plus a pinned Home tab. 116 owner-phrased questions in total (59 free-tier, 57 paid-tier); 63 answer-rendering handlers shipped.

The five things Ask me! is not:

1. Not an AI assistant. No LLM.
2. Not a third-party integration. Zero outbound HTTP calls from the Ask me! pathway.
3. Not a tracking layer. Every query reuses the existing v1.0.0 SQL — zero new SQL paths, byte-identical numbers.
4. Not a server-side service. Runs entirely inside your WordPress admin on your MySQL.
5. Not a paid-only feature. 79 of the 117 questions are free-tier; only 38 paid-tier questions render the Growth v2 “Coming soon” card.

Default pinned questions (every fresh install ships these five pins):

1. q2 — How many people visited my site in the last 30 days?
2. q23 — What are my top pages?
3. q41 — Where is my traffic coming from?
4. q72 — What countries are my visitors from?
5. q81 — How much traffic is mobile vs desktop?

Pin preferences are stored per-user in wp_usermeta on your own database.

Question categories shipped:

Tab	Total	Live today	Coming soon (v1.2 free)	Coming soon (Growth v2 paid)
Traffic overview	10	9	0	1
Real-time + tracking health	10	0	0	10
Pages & content	17	11	4	2
Referrers & channels	16	15	0	1
Campaigns & UTM	14	9	1	4
Geography & language	9	4	0	5
Devices & browsers	12	7	1	4
Engagement & quality	8	0	2	6
Revenue	15	0	0	15
Events & privacy	5	0	0	5

New visualization types

• Line chart viz — used by q9 “What is my traffic trend over time?” — Sessions + Visitors on one chart, datepicker-driven.
• Recommendation viz — for advisory cards that flag patterns rather than show a number.
• Yes/No chip on delta viz — q10 “Has my traffic dropped sharply?” and q11 “Has my traffic spiked sharply?” render a clear Yes/No alongside the magnitude.
• Top-X label on KPI tile — q42/q73/q82 now name the top channel/country/device above the number, not below.

New filter hook

statnive_advisor_evergreen_days — the cutoff that q37 “Which old posts still get traffic?” uses to define “old”. Defaults to 90 days; site owners can tune via:

add_filter( 'statnive_advisor_evergreen_days', function() { return 180; } );

Changed

WC Revenue date bucketing

Previously: orders bucketed by date_created_gmt. This put renewal payments + delayed payments on the date the order was placed, not the date it was paid — surprising for revenue reports that want cash-basis bucketing.

Now: bucketed by COALESCE(date_paid_gmt, date_created_gmt). If date_paid_gmt is set, that’s the day’s revenue. If not (e.g. cash-on-delivery, pending orders that never paid), falls back to creation date.

Funnel “Overall %” denominator

Previously: each funnel step’s denominator was the previous step. “Overall conversion” was purchases / viewed_products.

Now: every step uses the widest step as the denominator. Per-step UI shows conversion %, not drop %. This matches the convention WooCommerce Analytics adopted in WC 9.x.

Inventory consolidation: 120 → 116 questions

q1, q5, q25, and q63 were degenerate hard-codes or duplicates of other questions. Removed in 1.1.0. No question IDs renumbered — the rest are stable.

Fixed

• q47 Direct-visits undercount. Direct-channel sessions were being misclassified as Referral when the referrer header was an obvious empty string but the User-Agent matched a known direct-traffic pattern (mail-app, native-app webview). Fixed; q47 numbers now match the dashboard Referrers tab.
• q46 social-network missing platforms. Threads, Bluesky, Mastodon, and Lemmy were being bucketed under “Other Social” instead of getting their own rows. Now break out individually.
• q42 / q73 / q82 top-X tiles. When two values tied at the top, the tile rendered “(tie)” instead of the highest-traffic option. Now picks the one with most recent traffic as the tiebreaker.
• q10 / q11 anomaly Yes/No clarity. Previously the delta viz used colour alone to encode the answer. Now ships an explicit Yes/No chip alongside the magnitude.
• 6 more user-reported card fixes — see the full release notes on GitHub.

Compatibility + housekeeping

• Tested up to: 7.0 (WordPress 7.0 compatibility verified)
• Plugin Check Plugin §18 SuppressFilters violation resolved
• PHP 8.1+ still required; no new minimum bumps
• No dbDelta migration in 1.1.0 — reuses 1.0.0’s schema. (The 16 schema-gap questions blocked on entry_count / exit_count / avg_time_on_page columns land in 1.2.0 with a small additive migration.)

What’s next

• v1.2.0 — entry_count, exit_count, avg_time_on_page columns + the 16 free-tier Coming-soon question handlers (q27, q28, q29, q30, q40, q66, q91, q93, q94, q95, q96, q97, q99, q100, plus the two engagement-by-page derived metrics).
• Statnive Growth v2 — paid tier; unlocks the 38 paid-tier Coming-soon cards (revenue × channel, revenue × campaign, AOV by device, refund rate by product, real-time tracking health diagnostics, advanced engagement, custom events, privacy diagnostics).

The 10-post Ask me! blog series runs from today through 2026-06-19 and walks owners through how to use the headline questions in practice. Each post pairs the GA4 click-path with the one-click Ask me! answer, plus 2026 benchmark anchors and decision rules. See the launch post for the schedule.