Skip to content

Edge extension analytics: what Partner Center shows and what it does not

6 min readModerok team

What Edge extension analytics Partner Center reports, which installs its numbers cannot see, and what you have to instrument yourself.

If you ship on the Microsoft Edge Add-ons store, your Edge extension analytics start in one place: the Analytics page under Extension overview in Partner Center. Microsoft documents four metrics there (Weekly users, Enabled vs Disabled, Installs and Impressions), four time ranges, three filters and a CSV export, each quoted below from Microsoft's own documentation as of November 2026. None of it reaches into your code. The feature nobody opens, the install cohort that quietly stopped coming back, the exception thrown only under one OS: all of that is yours to collect.

TL;DR: Partner Center's analytics dashboard documents Weekly users, Enabled vs Disabled, Installs and Impressions over Last month, 3 months, 6 months or All time, as of November 2026. Installs counts only installs "at the Microsoft Edge Add-ons website", so an Edge profile that got your extension by another route is outside that number. In-product signal is absent from the dashboard, and the Update REST API exposes no metrics endpoint.

What the Partner Center analytics dashboard reports

Microsoft's extensions analytics page documents the route: "From the left panel, click Extension overview > Analytics to view your extension metrics." Four metrics are documented there, with these definitions as of November 2026:

MetricWhat Microsoft's page says it countsSource
Weekly users"the number of users that have your extension turned on, turned off and status unknown on Microsoft Edge over the past seven days"Weekly users
Enabled vs Disabled"the number of instances of the extension that are enabled or disabled per user"Enabled vs Disabled
Installs"the total number of successful installs of your extensions per day at the Microsoft Edge Add-ons website"Installs
Impressions"the total number of page views and user visits to your extension product page at the Microsoft Edge Add-ons website"Impressions

The time range is a fixed list: "From the analytics dashboard you can view metrics for the Last month, 3 months, 6 months, or All time (the period since your extension was published at the Microsoft Edge Add-ons website)." That page documents no custom window and nothing shorter than a month, and Impressions data points on it "are based on weekly or daily totals depending on the selected time range."

Three of the four can be sliced: "You can further refine views of your extension's Weekly users, Installs, and Impressions by Region, OS, and Language." Read the OS one carefully, because that section says the filter "highlights the OS usage distribution of all the install requests for your extension." Install requests are not current users. The same page adds that "You can also export this report as a CSV file."

Note what Weekly users counts: someone who has your extension turned off is inside that number. Firefox works the other way: when Mozilla moved AMO's statistics pipeline off update pings, its June 2020 announcement said "The dashboards will only show data for enabled installs." (More on that gap.)

Why your own install count will not match Partner Center

The Installs definition does a lot of work in one phrase: successful installs "at the Microsoft Edge Add-ons website." Anything reaching an Edge profile another way falls outside it, and a user can open one such route themselves. Microsoft's policy page Configure default state of Allow extensions from other stores setting describes a flag users otherwise "turn on" themselves when "installing extensions from other supported stores such as Chrome Web Store", and says the policy "can't be used to stop installation of extensions from other stores such as Chrome Web Store" (as of November 2026). Microsoft's analytics page does not say whether such copies appear in the Edge Weekly users figure, scoped to users who have the extension "on Microsoft Edge", so read Installs as installs from the Edge listing, nothing wider.

An SDK inside the extension has the opposite vantage point: it never sees the store, and is not scoped to one store. Moderok's SDK tests the user agent for Edg/ before Chrome/, so a desktop Edge install is tagged browser: "edge" with its Edge version instead of falling through to chrome. Mind the mobile case: Microsoft's user agent guidance documents EdgA/ on Android as of November 2026, which that test does not match, so an Android profile records as chrome. Either way the value rides in each event's raw context; the current charts are aggregate and do not break down by browser. It is not a census: a profile running a build that shipped before you added the SDK sends nothing, and the event queue is capped, so events can be dropped. The install count divergence guide works the Chrome Web Store case through in detail, from ephemeral Chromebook profiles to reporting delay, multi-profile users, repair reinstalls and UTC day boundaries. Those mechanics apply to Edge too, but the ratio that guide gives for Chrome is not documented for Edge.

The Edge extension analytics you have to collect yourself

Nothing in Microsoft's dashboard documentation answers these three.

Which features get used. A store metric cannot tell you that the toolbar button carries your whole product while the context menu item is dead weight.

Retention by install date. Weekly users is a rolling seven-day count, not a cohort: it cannot tell you whether the profiles that installed in week 1 were still active on day 30.

Errors. An exception that fires on startup under one OS leaves no trace in an installs chart. What production error capture takes in MV3 is in Chrome Extension Error Tracking: Catching Service Worker Errors in Production.

No API route reaches them either. The Update REST API documents four endpoints, as of November 2026, covering package upload, publishing a submission and the status of each, and adds that "There aren't REST API endpoints for:" creating a new product or updating its metadata. Metrics are in neither list, so automated reporting means the CSV export.

Instrumenting an Edge extension: what actually changes

Microsoft's porting guide says, as of November 2026, that "The Extension APIs and manifest keys supported by Chrome are code-compatible with Microsoft Edge." Two of its steps touch the package rather than your analytics code: "Remove the update_url field from the manifest file." and, if Chrome appears in your extension's name or description, rebrand it, because "To pass the certification process, the changes are required."

Check your dependencies against the supported APIs list, which, as of November 2026, describes Edge extensions as using "a subset of the JavaScript methods for the Chromium browser engine platform." On that page runtime and storage, the two APIs a lightweight analytics path needs, are both listed as supported in MV2 and MV3, while its unsupported table, where a heavier SDK fails, includes gcm, instanceID, identity.getAuthToken and identity.getAccounts.

What you send is what you would send on Chrome: install, update, an activity ping at most once a day, one event per user intention rather than per click, and errors. Keep properties flat (string, number or boolean) and free of identifying content. Moderok's SDK handles the lifecycle part with no track() call of yours, through the five events documented as automatic. Setup is three parts: install @moderok/sdk, add the storage permission, and call init() at the top level of the service worker before any await.

import { Moderok } from "@moderok/sdk";

Moderok.init({ appKey: "mk_your_app_key_here", trackUninstalls: true });

Moderok.track("export_completed", { format: "csv" });

When Partner Center alone is enough

For one of its four metrics there is no alternative. Impressions is store-side by definition: no code inside your extension can see how many people viewed your product page, so listing-view-to-install conversion is a question only Partner Center can answer. The Region and Language filters are store-side too, documented as of November 2026 as "the geographical distribution of users for your extension" and "the language distribution for users of your extension".

If your question is whether the listing is growing, where the installs come from and how many people have switched you off, Partner Center answers it today with no code shipped. In-extension events are for the questions that start at the product instead.

When those are the ones you have, the Moderok dashboard shows which reports come back, and the getting started guide covers the Edge build. One package with zero runtime dependencies covers Chrome too.