Until now, Google Play data in Easy App Reports only included the package name to identify your apps. For most apps that's fine, but package names can be cryptic (think com.acme.x1a), which made it harder to read your reports and impossible for the AI assistant to find your app when you asked about it by name.
That changes today. We've added a new app_name column to all your Google Play tables.
All Google Play tables now include an app_name column with the human-readable name of your app, pulled directly from the Play Store.
For Looker Studio users: If you're already using a Google Play table as a data source, just open it in Looker Studio and refresh the fields. The app_name column will show up automatically. If you're connecting a table for the first time, it's already there.
For BigQuery users: The app_name column is now part of the ear_all_sources dataset. No setup needed on your end.
This one has a practical impact if you use the AI Integration (MCP). Previously, when you asked the AI something like "how many installs did my app get last month?", it had to match your question to a package name - which doesn't always work, especially for less obvious package names.
Now that the app name is stored alongside your data, the AI can find the right app when you refer to it by name. Queries should feel more natural and reliable from here on.
Apps not yet published: The app name is pulled from the Play Store listing. If an app has been submitted but isn't published yet, the name may not be available. This is an edge case, but if you notice something missing, just let us know and we'll take a look.
If something looks off or you're not seeing the app_name column where you'd expect it, reach out. We're happy to help.
