Shopify App Store listing traffic in Luseri
Luseri reads the Google Analytics 4 property connected to your App Store listing, with Viewer access, and shows your listing views, Install clicks and confirmed installs, the searches merchants typed before opening your listing with the position you held at that moment, and how your views split between search, ads, categories and other App Store pages. Searches can be filtered by country and by language, and exported. No BigQuery export is needed.
By Arthur Renard, updated
See it in the demo
The Acquisition screen of the dashboard, with example numbers. It opens without an account.
What you see
Two pages of the dashboard use your Google Analytics. Both follow the period you pick in the top bar and compare it with the period of the same length just before.
| What | Where | Detail |
|---|---|---|
| Listing views and visitors, day by day | Acquisition | Only the pages served by apps.shopify.com are counted |
| Install clicks | Acquisition and Keywords | A click on the Install button sends two events to GA4; it is counted once |
| Confirmed installs | Acquisition, by App Store page; Keywords, by search | Sent to GA4 by Shopify's servers when a store finishes installing your app |
| Searches typed by merchants | Keywords | Up to 200 per period, each with its views, Install clicks, click rate, confirmed installs, average position, views from an ad and its trend over the period |
| Where views come from in the App Store | Acquisition and Keywords | Search, search ads, category pages, the App Store home page, collections, stories, developer pages, other apps' listings and app extensions |
| Sites that send visitors | Acquisition | Source and medium in GA4 over the last five weeks, such as Google or an AI assistant |
| From listing to subscription | Acquisition | Views and Install clicks from GA4, then installs, trials and new subscribers from your Partner account |
The table of searches can be filtered by the merchants' country and by the language they use in the App Store. The Export button saves it as a CSV file that a spreadsheet opens directly.
Searches and the position at the click
When a merchant opens your listing from the App Store, Shopify writes in the address of the page what they came from: the type of page, the words they searched for, and where your app sat in the results. Google Analytics keeps that address. Each day, the address of every visit is read and turned into a table of searches.
The position is the one your listing held when the merchant clicked it, averaged over the visits of the period. It counts the ads placed before your listing on the same page, so it can be a few places further down than your ad-free position on a tracked keyword. Visits from beyond the tenth page of results are left out of the average.
Only searches followed by a visit to your listing appear. A keyword where you rank too low for anyone to click stays invisible here, which is why the Keywords page also follows the daily position of the keywords you choose, and suggests searches to track among those that brought visits.
For what each parameter means and how to read them yourself in GA4, see which searches bring merchants to your Shopify app.
Views from App Store ads
Views that came from a search ad are counted apart from organic search: on each search, as views from an ad, and as their own line in the split by App Store page, with their Install clicks and confirmed installs. You can compare paid and organic arrivals on the same words. Ad spend stays in your Partner dashboard: it is not read.
To decide whether ads are worth it, see Shopify App Store ads.
How to connect it
- In your Shopify Partner dashboard, open Apps, your app, Distribution, then Manage listing. In the Tracking information section, paste your GA4 measurement ID (it starts with G-) in the Google Analytics code field, then save.
- For confirmed installs, also create a Measurement Protocol API secret in Google Analytics (Admin, Data streams, your stream) and paste it in the same Tracking information section. Without it, views and Install clicks still arrive, but no confirmed installs.
- In Google Analytics, open Admin, then Access management under Property, and add the address Luseri shows you with the Viewer role.
- On the Acquisition page of Luseri, paste your property ID: the number shown in Admin, Property details, not the ID that starts with G-.
- Prove the property is yours: Luseri shows a short code made for your account. Add it to the end of the property name in Property details, save, then click Connect again. Once the property is connected, you can remove the code.
The first reading copies up to a year of traffic. After that, the property is read once a day, and the last 35 days are read again each time, because Google Analytics can still correct them.
Why the code in the property name
Since October 20, 2026, Luseri asks for this proof before it reads a property. Every account adds the same reading address to its Google Analytics, so being able to read a property says nothing about who owns it. Without the check, someone who knew another developer's property number could have seen their listing traffic.
Changing a property's name takes more than Viewer access: in Google Analytics, Viewers can see settings and data, while control of the property's settings belongs to the Editor role. So the code can only be added by someone who controls the property, and the code of one account proves nothing for another.
Why no BigQuery
Other tools read listing traffic through the BigQuery export of GA4. Here the reports are requested from the Google Analytics Data API, with read-only access, so there is no export to switch on and no Google Cloud project to create. Google limits how many reports each property can serve per hour: if the limit is reached, the dashboard says so and asks you to try again an hour later.
Read-only means it: nothing is written to your property. To stop, disconnect Google Analytics in the settings, which erases the copied traffic, or remove the reading address from Access management in Google Analytics.
What it does not do
- Google Analytics only counts visitors who accept analytics cookies, so the real numbers are a little higher than the ones shown.
- There is nothing before the day your measurement ID was added to the listing: GA4 has no earlier data to give.
- It does not tie an install to a store's revenue: searches lead to confirmed installs, not to subscriptions or revenue by keyword.
- It does not give search volume for a keyword, and it shows nothing about competitors' traffic.
Questions
- Do I need BigQuery to see my Shopify App Store traffic?
- No. Luseri requests the reports from the Google Analytics Data API with Viewer access to your GA4 property. You do not need to turn on the BigQuery export or create a Google Cloud project.
- What access does Luseri need to my Google Analytics?
- The Viewer role on the GA4 property connected to your listing. Viewers can see reports and settings but cannot change the property's settings, and Luseri only asks Google for read-only access. You can remove it at any time from Access management in Google Analytics.
- Why does Luseri ask me to add a code to my property name?
- To prove the property is yours. Every account uses the same reading address, so read access alone proves nothing. Renaming a property needs more than Viewer access, so only its owner can add the code. Once the property is connected, the code can be removed.
- How far back does the listing traffic go?
- Up to a year, copied on the first reading, and never before the day the GA4 measurement ID was added to your listing. After that, the property is read once a day.
- Can I see which searches led to installs?
- Yes, if your listing also has a Measurement Protocol API secret. Shopify then sends a confirmed install to GA4, and Google Analytics ties it to the visit, so each search shows its confirmed installs next to its views and Install clicks.