How to Migrate From MonsterInsights to Asteris Insights

This walkthrough covers the recommended way to switch your WordPress analytics from MonsterInsights to Asteris Insights without losing data confidence or interrupting any reporting you currently rely on.

The migration looks different from the Yoast → Asteris one because the products store data in different places. MonsterInsights doesn’t keep analytics data in your WordPress database — it sends pageviews to Google Analytics 4, where the data lives. Asteris Insights writes to its own tables on your server. There’s nothing to “import” between the two in the way a Yoast importer carries titles + meta descriptions.

What you actually need to do is: install Asteris, run both for 14-30 days so you can sanity-check the numbers, then turn MonsterInsights off when you’re confident.

Before you start

Things to confirm:

Your GA4 historical data stays in Google. Removing MonsterInsights doesn’t delete your GA4 property. GA4 retains data per Google’s retention settings (typically 14 months for free, 50 months for Pro on a 360 account). Don’t delete the GA4 property unless you’re sure you won’t need that history.
Asteris Insights starts at zero. Whatever date you enable it is day-one for your first-party data. Plan around that — for year-over-year comparison, you’ll need 12 months of Asteris data first.
You don’t have to drop GA4 entirely. If your team needs GA4 for ads attribution, BigQuery export, or Looker Studio, the Asteris Analytics + Pixels module can keep injecting the GA4 pixel after MonsterInsights is gone. Asteris Insights replaces MonsterInsights’ WP-admin dashboard, not necessarily your entire GA4 setup.

If those points work for you, proceed.

Step-by-step

1. Install Asteris for WordPress

Buy or activate your Asteris subscription, install the plugin, and activate your license. (Standard plugin install — Plugins → Add New → Upload.)

2. Enable the Insights module

WP Admin → ★ Asteris → ⚙ Insights Settings → General

Tick Enable Asteris Insights tracking → Save settings.

The beacon now enqueues on every front-end page render. The hourly rollup cron and daily retention cron schedule themselves. The first visit you record after this moment is day-zero of your first-party data.

3. Verify the beacon is firing

Open your homepage in an incognito window (or log out — admins are excluded by default).

Open browser DevTools → Network tab → filter by collect → you should see:

POST /?asteris_collect=1 (Drop-In mu-plugin path) → returns 204, OR
POST /wp-json/asteris-wp/v1/collect (REST fallback path) → returns 204

Both work. The Drop-In is faster (<5ms) and is used when wp-content/mu-plugins/ is writable; REST is the fallback when it isn’t.

4. Trigger the first rollup

WP Admin → ★ Asteris → 📊 Insights → in the 🔧 Collection pipeline QA strip at the top → click ⚡ Run rollup now.

The dashboard badge flips from Preview · waiting for first visit to LIVE. Every tile populates with your fresh data.

5. Parallel-run for 14-30 days

Leave MonsterInsights installed and active during this phase. Both will track in parallel:

MonsterInsights → GA4 (client-side, via cookies)
Asteris Insights → your DB (cookieless beacon)

The numbers won’t match perfectly — and that’s fine. Asteris’s numbers will typically be higher because:

Asteris isn’t blocked by uBlock Origin, Brave Shields, Firefox Strict Mode (which block GA4)
Asteris counts visitors who decline GA4 consent banners
Asteris tracks even when a visitor’s browser sends Do Not Track (we honor localStorage.asteris_optout=1 instead — fewer people set it)

A 15-30% difference between the two during parallel-run is normal and validates that Asteris is doing what it’s supposed to.

Pick one key metric you care about (visitors, top pages, or conversions) and watch how the trend lines compare day-over-day. If the trends move together (both up on Tuesday, both down on Wednesday), you’re confident the new tracker is working. The absolute numbers don’t need to match — only the shape.

6. (Optional) Set up Search Console under Analytics + Pixels

If you used MonsterInsights’ Search Console integration, you’ll want the equivalent on Asteris.

WP Admin → ★ Asteris → 📊 Analytics + Pixels → 🔌 Data sources tab → 🔎 Google Search Console → Connect

OAuth flow + property picker. First sync runs immediately. The 🔎 Search Console tile on the Insights dashboard populates within a few minutes.

7. (Optional) Decide GA4’s future

You have three options at this point:

Option A — Keep GA4, drop MonsterInsights. If you still need GA4 (ads attribution, BigQuery, marketing team workflows), keep the pixel injected via Analytics + Pixels module → Pixels tab. Paste your GA4 Measurement ID. The pixel fires, GA4 keeps receiving data. You just don’t need MonsterInsights’ wrapper anymore.

Option B — Drop GA4 entirely. If MonsterInsights was your only reason to be on GA4, you can leave the GA4 property running (don’t delete it; the historical data is yours forever) but stop injecting the tag. New pageviews stop reaching GA4, but the past is preserved.

Option C — Keep GA4 + MonsterInsights. Unusual but valid. Some teams keep MonsterInsights for the GA4 dashboard surface and use Asteris Insights for the cookieless + cross-module-annotations workflow. They don’t conflict.

8. Deactivate MonsterInsights

When you’re confident (typically 14-30 days of parallel-run with matching trend lines):

WP Admin → Plugins → MonsterInsights → Deactivate (and optionally delete).

If you chose Option A above, double-check the GA4 Measurement ID is still configured in ★ Asteris → 📊 Analytics + Pixels → Pixels tab before deactivating MonsterInsights — once it’s gone, that’s the only place injecting the tag.

9. (Optional) Opt into the weekly digest

Insights Settings → General → Weekly digest email → tick Send me a weekly summary email → recipient defaults to admin_email. Click Send test digest now to preview it immediately.

Sent every Monday at 09:00 UTC. The email summarizes 4 hero KPIs + top 5 pages + top 3 countries + the highest-severity annotation of the week.

Frequently asked questions

Will my MonsterInsights historical data disappear when I deactivate it?

No — and Asteris doesn’t have access to it in the first place. That data lives in Google Analytics 4, in your GA4 property. Deactivating MonsterInsights doesn’t touch the GA4 property. Your historical data is preserved in GA4 for as long as you keep that property active.

Can I import my MonsterInsights data into Asteris’s tables?

No — and not because Asteris is missing a feature. There’s no MonsterInsights-side data to import. MonsterInsights doesn’t store analytics rows in WordPress; it just relays your pageviews to GA4. The data you’d want to import lives in Google’s servers, queryable only via the GA4 reporting API. (Pulling GA4 historical data into Asteris’s tables is on our roadmap — see the GA4 Data API roadmap card under Analytics + Pixels → Data sources.)

Will my numbers match between MonsterInsights and Asteris?

No, and that’s expected. Asteris’s numbers will typically be 15-30% higher because Asteris isn’t blocked by ad-blockers, Brave Shields, or Firefox Strict Mode — all of which strip GA4. Match the trend shape (both up Tuesday, both down Wednesday), not the absolute numbers. If trends diverge for more than 3-4 days, double-check the Asteris beacon is firing on every page type (DevTools → Network tab).

Do I have to remove the GA4 property?

No, and we recommend against it during the migration window. Your GA4 history is genuinely useful — year-over-year comparison from when you had MonsterInsights, ads attribution backfill, anything that needs historical GA4 data. Once you’re 100% sure you’ll never need GA4 again, you can delete the property in the GA4 admin — but that’s irreversible.

What if my marketing team still uses GA4?

Keep GA4 alive. Use the Analytics + Pixels module → Pixels tab to inject the GA4 tag (same effect as MonsterInsights’ tracking-setup, without the dashboard wrapper). Asteris Insights runs in parallel for the WordPress-admin dashboard view. They serve different audiences — marketing team in GA4, you in wp-admin.

Does Asteris Insights work with consent banners I already have installed?

Yes — it doesn’t fight with cookie-consent plugins because Asteris Insights doesn’t set cookies. If your consent banner is configured to block GA4 until consent is given, Asteris Insights tracks visitors during the pre-consent period anyway (legally, in most jurisdictions, because the tracking is cookieless and IP is truncated). That’s part of why Asteris’s numbers come out higher.

How long should I parallel-run before deactivating MonsterInsights?

14 days is the minimum for confidence on a typical content site. 30 days is safer for e-commerce (covers a full monthly cycle including any month-end promotional activity). If your traffic is highly seasonal, parallel-run through one full cycle of whatever your shortest seasonality is.