Where to find Google Play submission history in Play Console

Where do I check Google Play submission history in Play Console

Open Play Console, then use Activity log for account change history and Submission activity for submission records. Use Releases overview only when you want release history, because it shows rollout details, not the full submission log.

The page people usually want is Submission activity. Google says every submission gets its own record, with the changes included, when it was received, how it was submitted, and its current state. That is the closest thing to submission history in Play Console.

In Play Console, go to Publishing overview if you want to see pending changes that have not been sent for review yet. That page shows what is waiting in the publishing flow, but it is not the same as a history page. If you are trying to understand what already went to Google, switch to Submission activity.

If you want to see release history for a specific track, go to Test and release, then Releases overview. Google says that page groups rolled-out releases in one place and lets you open individual release details. It is useful for tracking production, open testing, and closed testing releases, but it does not replace submission activity.

If you need to check who changed something in the console, open Activity log. Google says the Activity log records changes made by team members across the lifetime of the developer account, and it includes items related to publishing and status changes. That makes it the right place for user actions, not submission records.

A practical path is simple: open your app in Play Console, then check Publishing overview for items still waiting, Submission activity for what was already sent, and Releases overview for track rollout status. That is the part people get wrong, because “submission history” can mean three different screens.

The inconvenient part is that older records are not unlimited. Google says Submission activity displays up to one year of history starting May 1, 2026. If you need older context, keep your own release notes, ticket numbers, and build IDs outside Play Console.

Inside a submission record, Google says you can open the submission to see the submission ID, whether it came from the Play Console UI or the Publishing API, and timestamps for state changes such as sent for review, approved, canceled, or published. That is the detail to copy when you are talking to support.

If a release was rejected, Submission activity is still the first place to check, because Google links the latest rejected submissions to the Policy status page. That is where you look for the issue details and the fix path. The releases pages will show status, but not the policy explanation you need.

For day-to-day work, the cleanest mental model is: Activity log = who changed Play Console, Publishing overview = what is waiting, Submission activity = what Google received, Releases overview = what rolled out. Once you separate those, you stop hunting through the wrong menu.

If you are already using DevConnect for tester exchange, the same rule applies there: use the right screen for the right job, and keep the release trail outside your memory. The platform itself is at https://devconnectplatform.com, but the Play Console history you need still lives in Google’s publishing and release pages.

A concrete example helps. If you submitted a closed test release on Monday, fixed a store listing issue on Tuesday, and pushed a new build on Wednesday, Submission activity should show each submission record. Releases overview should show which track each rollout reached. Activity log should show who edited the listing or release settings.

If you do not see the record you expected, check whether a newer submission superseded the older one. Google says a submission can be canceled when a newer submission replaces one that was still in review. That is one reason submission history can look shorter than you expect.

The fastest way to remember it is this: if the question is “what did we send,” open Submission activity. If the question is “what changed in the console,” open Activity log. If the question is “what is live on a track,” open Releases overview.