Google Analytics (GA4) Name Changer for Chrome Extension Developers

Chrome Web Store analytics arrive in Google Analytics 4 under a 32-character extension ID, and every Chrome Web Store developer account is labelled with the same generic string. If you publish more than one Chrome extension, every GA4 report, comparison and account switcher looks identical. GA4 Name Changer puts your real extension names back, live inside analytics.google.com. No account to create, no API key, no setup: open a property and it names itself. inkkcgalfjninhfflfhkflidilkjmhof → Tab Session Saver Pro 241067359 → Tab Session Saver + Dark Mode IT NAMES YOUR EXTENSIONS FOR YOU There is nothing to set up. Open a Chrome Web Store property in Google Analytics and the name appears by itself, usually within a few seconds. It works because the name is already on your screen. Your own "Page title and screen class" report lists your store listing, and the Chrome Web Store titles every listing page "<Extension Name> - Chrome Web Store". Splitting that suffix off the end gives the name, with no lookup and no request to anyone. Because the split takes the last separator, it works in every language the store is published in (Интернет-магазин Chrome, Chrome ウェブストア, Cửa hàng Chrome trực tuyến), and it keeps names that themselves contain a dash intact. It also works for extensions you do not have installed. ACCOUNT NUMBERS GET REAL NAMES TOO Google labels every Chrome Web Store developer account identically, so the nine-digit account number is the only thing telling them apart. Each account is named after the extension it holds. An account holding two is named after both, as in "Tab Session Saver + Dark Mode"; one holding three or more is named after the first plus a count. Extensions it has not seen yet are counted rather than guessed at, so a half-explored account reads "Tab Session Saver Pro + 1 more" and corrects itself when you open the rest. NAME THE ONES YOU HAVE NEVER OPENED A name is read from each property's own report, so a property you have never opened has nothing to read yet. One button on the settings page visits them for you: it opens a single tab in the background, goes through your remaining properties in turn, and closes it when it is done. About ten seconds each. It never takes over your screen, and you can stop it at any point. IT WORKS THE MOMENT YOU INSTALL IT If you already had Google Analytics open in a tab, that tab starts showing real names straight away. You are not asked to refresh anything. YOU CAN SEE THAT IT IS WORKING Because the names are swapped in place, a page it has fixed looks like a page Google got right. So the toolbar icon carries a count of the names applied to the page you are looking at. No count means there is nothing on that page to rename yet, and the tooltip says so. EVERYTHING IN ONE TABLE The settings page shows every Google Analytics account with the extensions it owns nested underneath, paired from Google Analytics' own account tree. Worked-out names are badged "auto". Type over any of them and press Save, and yours wins from then on: on this machine and, through Chrome sync, on your others. A property Google Analytics knows about that nothing has managed to name still gets a row of its own, so there is always somewhere to type it in by hand. Nothing is ever saved for you. A name the extension worked out stays a draft until you keep it, an "Unsaved changes" marker sits beside Save, and your browser asks before you leave with work in progress. Import and export the whole set as plain JSON, so you can move it between machines or keep it in version control. YOUR ANALYTICS NEVER LEAVE YOUR DEVICE There is no account to create, no telemetry, no analytics and no tracking. Every name is worked out from the page already open in front of you, and naming and replacing make no network request at all. Your traffic figures, revenue, user counts, property names and account numbers are never transmitted. Not to us, not to anyone. The extension sends exactly one thing, and only when you ask it to: if you fill in the feedback form on the settings page and press send, your message, your email address, your name if you gave one, and the installation details shown to you on that same page are sent so that your report can be answered. Those details are counts and version numbers only, with no property slugs, no display names, no account numbers and no URLs. If you never use the form, the extension never makes a request. Nothing in your Google Analytics account is modified. The replacement is display-only and lives in your browser; your configuration, your data and your reports are untouched. Remove the extension and Google Analytics looks exactly as it did before. ONE OPTIONAL EXTRA If you would like it, you can grant Chrome's "management" permission and any extension ID that matches something installed in your own Chrome profile is named from Chrome directly. It is off by default, it reads names and nothing else, and switching it off hands the permission straight back. Names are resolved entirely locally, with no network request. WHO IT IS FOR - Chrome extension developers reading Chrome Web Store analytics in GA4 - Anyone publishing more than one extension from one developer account - Agencies and studios managing extensions across several Google Analytics accounts - Teams comparing installs, uninstalls and store-listing traffic across a portfolio OPEN SOURCE Plain JavaScript. No build step, no bundler, no dependencies, no remote code. What ships is what you can read on GitHub, and the full architecture, the design decisions and the known limitations are all written down in the repository.