Track new users source - Chrome Store extension - google-chrome

I have a new extension that I am trying to get more users for, I am running two campaigns - lets call them A and B
These campaigns eventually lead to my extension's page on the Chrome store.
Is there a way to know how much installs\addons did each campaign added?
Not clicks - Proper users that added the extension.
Thanks!

In theory, yes.
If you have enabled Google Analytics for your extensions (created a property and added it while editing the extension), that property will start tracking your Web Store page. If you haven't installed it, then no, no such refined data will be available.
You will see installs as visits to /track_install/* URLs. You can create a Goal to have better analytics for it, but you can probably dig through the data even without it.

Related

How to set up a conversion event for a Chrome Extension install?

The Chrome Web Store allows you to add a Google Analytics UA tracking number to your Chrome Extension's page, however I can't find a way to integrate it directly with Google Ads to be able to track installs -- and to be able to track what keywords lead to higher or lower install rates.
Is there a simple method of doing this?
Thanks

How precise are Google Chrome extension statistics?

I published a Chrome Extension, but statistics are weird. At first, I realized that it doesn't count inline installation on my custom webpage.
Do you think that Total Current Users is precise?
For some days I have bigger drop of Total Current Users than number of uninstallations, which is nonsense.
Is there any way how to get precise statistics of total users, installations and uninstallations?
I am not sure is how precise stats in the current version of Developer Dashboard. But I know that Google working on a new version and it is already in closed-beta testing.
The new one has more detailed stats about installation sources.
Here also some steps that can help to improve your stats counting:
Add Google Analytics tracking ID to your Chrome Web Store item;
Track 'successCallback' event on the extensions promo website;
Open a "welcome" page, hosted on your website – so you can count those who just installed the extension. Docs: chrome.runtime.onInstalled;
Open a "good bye" page, after users remove your extension from a browser. So you can calc uninstall events. One more benefit - you can ask "what was wrong?". Docs: chrome.runtime.setUninstallURL.
Updated.

Private beta testing a Chrome extension

Is there a way of beta testing a Chrome extension in the Web Store among a small group of users?
I'd like to do this before scaling to everyone on my waiting list, but I don't want to have to send round the file with installation instructions, especially given that Google is tightening up on extensions that aren't downloaded from the Web Store.
It'd also be useful to be able to slowly roll it out (à la Mailbox) if that's at all possible.
Publishing on Chrome Web Store has 3 (well, 4) options:
Public. The extension will be listed in search and gallery, everyone can install and use.
Unlisted. The extension will not be listed in search and gallery, but everyone with a direct link can install.
(Google Apps domains only) People with accounts on [example.com] only. This allows to publish items privately, as long as you administer a Google Apps domain.
Private. The item will only be available to a selected list of Google accounts, or a Google Group. Note that this is aptly aliased as "Trusted Testers".
That said, you most probably have 2 options:
Have a restricted set of accounts that can use your app. CWS allows to either specify an explicit but short list, or to link with a Google Group you administer.
Use "unlisted" and send everyone the link. Use only if you don't care if the link leaks: you won't be able to remotely kill any install.
Note that if you have enough (10000+) users you can do partial rollouts of regular updates, to have less impact from problematic updates if they happen.

Chrome store statistics

I'm building a funnel for our chrome extension using Google analytics.
When it comes to the chrome store stats at the beginning of the funnel, the data the developer's dashboard provides is limited (impressions & installations only).
I'm looking for data such as referrals to my extension page, the amount of people who clicked on the extension page but didn't install it (not impressions).
Can this data be found in the dashboard or GA? where? and if not, how can I otherwise track this?
Thank you very much!
Efrat
You can add a Google Analytics ID to your projects from the Developer Dashboard. Create a new account in Analytics, click on "Edit" next to your project in the Chrome Developer Dashboard, and add the ID near the bottom of the page. (I'm not sure how new this feature is, but it is a little hard to find).
Inside Analytics, I have a goal set up for the URL /track_install/detail/ext/free/{% my extension id %}, which tracks installations. This shows the number of views without an install in the goal funnel. Referrals are available like any other Analytics page. GA is much more granular and updates in real time instead of once a day like the dashboard.

Inject ads to Google Chrome Extension

I am developing a google chrome extension, and planning to inject ads using the allowed feature. I have checked in front of "Ads Behavior" that says "This extension injects ads into some third-party websites."
My question is, how and where do I mention the source of ad? Say, if I want do display google adsense, how do I set it up??
I searched it throughout the day today, but didn't get any information anywhere.
Thanks,
James
Injecting ads is not that simple.
The first problem you will face is to find an ad network that allows extensions to inject advertisements in pages. AdSense doesn't allow this behavior.
The second (and maybe more complicated) problem is to inject the ads. In a chrome extension you can use script injection to add the advertisements to the pages. The real problem is where to put the advertisements. They should be placed in a smart manner; ensure they don't conflict with the page layout/functionality; they shouldn't be everywhere and on every page, otherwise your users will promptly uninstall the extension; you absolutely shouldn't just replace existing ads if you don't want your extension to be flagged as malware.
I haven't yet added ads to my extension because of these and others problems, and I am striving to get some money from it since it has cost me a considerable amount of time to create it, and I have received very, very few donations considering the over 150.000 users.
Hope I could help.