I have created a Chrome Extension, hosted on the Chrome Web Store, and I'm driving PPC ad traffic to it via Google Ads.
My goal is to be able to track, what percent of users searching Keyword A, vs Keyword B, vs Keyword C, ultimately download the Chrome Extension. However there is a shockingly small amount of information/documentation online about how to track and set up any of this.
Here's what I've done:
Inside of Google Analytics, I created a new Property for the Extension. For the Data Stream, I link to the Chrome Web Store page for the extension.
On that Data Stream page inside of Google Analytics, I copied the Measurement ID, which is something like "G-R57QV4PBCE"
I then pasted that, inside of the Chrome Web Store developer editor page, for the Chrome Extension, where it asks for a Google Analytics ID.
Inside of Google Ads? Under "Linked Accounts"? I found Google Analytics, found the specific property which contains that Chrome Extension data stream, and I linked that.
So my understanding is that all of these things should now be linked -- the Chrome Web Store Extension page is linked with Google Analytics, which should track all of the install information on there. Then the Google Analytics page is integrated with the Google Ads account, meaning I should be able to ultimately see information about -- What percent of people who searched Keyword A or Keyword B, ultimately landed on the Web Store page, and installed the extension -- correct?
Am I missing anything here? Any additional steps or anything to be able to track this correctly? Do I need to add UTM parameters to the Google Ads link I use to drive traffic to the web store? Do I need to set up any custom events inside of Google Analytics to be able to correctly track what I'm trying to track?
Thanks
Related
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
I made an app as an extension on Chrome Web Store. I would like to know the download count for my extension.
From the developer's dashboard I can access to Statistics, but the graphic starts in 21/5/2015 (three months ago) and the CSV file too.
How can I see the complete download history?
Creating a Google Analytics account using it to track installs is probably a pretty close estimate of downloads.
Once you create your Analytics account, you create a new property with the default URL being your extension page. For example, https://chrome.google.com/webstore/detail/<extension-name>/<extension-id>
Once you get your tracking id, add that to the edit page for your extension in the webstore developer dashboard.
Once you have done that go to the Analytics admin panel and on the right click Goals. Add a new Custom goal of Destination type for the RegEx match of /track_install/.*.
You can now add a graph of this goal completion to track installs.
Here is a comparison of the data collected by Google Analytics and the Statistics in the webstore developer dashboard.
I'm doing some beta testing of my new Chrome extension for Gmail, and I'm wondering what the correct way to link to the web store from an adwords campaign is?
There isn't enough space to display the web store link, and shorteners violate policy. Should I be linking to the main site, and then using an ad extension with a link to the chrome store?
The idea is just to drive some limited targeted traffic directly to the download/install page without self hosting it yet.
I need some light on the matter of Chrome Webstore registration.
I'm still confused despite searching through the web: the "app" will be only private for the site (we're trying to develop a Elgg plugin for our website that will allow users to access their drives).
1) for testing, do I need to register it (I did a search but some say yes like in the Google Drive SDK documentation, some say no in the google-drive-sdk tags)?
2) when the plugin is finished, tested and ready to go live for our users, do I still need to register it and pay 5$?
Thanks you for the answer you can provide us.
You don't need to register your app on the Chrome Web Store if you don't want to integrate with the Google Drive web UI: having the option to create a new file or open a file with your app directly from Google Drive.
Also, it might be easier for you not to create a Chrome Web Store listing while developing.
If you do need to integrate with the Google Drive web UI, but don't want your app to be public, you can publish your app to Trusted Testers only.
I have released an app for Google Drive in the Chrome Web Store. I thought it might get added to the Google Drive Collection automatically, but that didn't happen. Is there any form I have to submit?
For your application to appear in the collection of Drive apps your Chrome Web Store app's manifest file need to specify the Google Drive container and your API console project ID as described in this document.
Then your app's listing should get the "Works with Google Drive" badge and, given a few minutes delay for indexing, your app will appear on the collection of Drive apps.
Beware: you may not see it there as a listing doesn't appear for you in that collection if you have already installed it on your browser. It will appear to all other users who have not installed your app yet. To make sure it's there: try looking at the collection with another browser (FireFox for instance).