ASO

We’re interested in analyzing featured data for our apps and competitors, so we’re looking to get this data in CSV format.

Google Play store search currently uses web-form only, it might have limited functionality. We would love to see results for various devices as well.

Add the ability to use New Device Acquisitions instead of App Install State: New Users within AppFollow’s Google Play reporting. The current metric (New Users) does not align with how the customer measures acquisition performance. Specifically, it may include broader user activity across devices, leading to discrepancies when compared to New Device Acquisitions, which focuses strictly on first-time installs per device. Customer reports on New Device Acquisitions in Google Play to track first-time downloads. They’ve observed that App Install State: New Users does not match their internal reporting or Google Play’s New Device Acquisition metric. Their definition: Device Acquisition: Number of devices that installed the app (including pre-installed activations) New Devices: Devices where the app was installed for the first time Requested Solution: Allow selecting or switching the acquisition metric used in AppFollow (e.g., toggle between New Users and New Device Acquisitions) Alternatively, add New Device Acquisitions as an additional metric in reporting dashboards

Currently, AppFollow collects Google Play ranking data from a public endpoint that provides an extended list of apps (200+ positions). However, this data source does not always align with the rankings displayed in the Google Play storefront (e.g., category pages like “Top Free in Events”), which show a shorter, curated list. As a result, customers may see discrepancies between rankings in AppFollow and rankings visible directly in Google Play (web or mobile) Proposed Solution: Review and validate the current Google Play ranking data source Investigate alternative endpoints or methods that better reflect the rankings shown in the Google Play storefront Align ranking logic with the user-visible store experience where possible Ensure “best result” values reflect actual peak positions seen in the store Google Play rankings may vary depending on endpoint, personalization, or presentation layer. However, priority should be given to aligning with the default, user-facing storefront rankings whenever possible.

Since many keywords stopped showing their actual popularity after the end of September, it now takes a lot of time to check their relevance and popularity. I’ve attached examples of how competitors have implemented this.

We would like to get reviews and insights for this platform

Ensure the "Copy" button for a keyword remains active after a note has been added to it