peekpandaPeekPanda docs
Request an app
Add an App Store listing the catalogue does not hold yet, and ask for evidence that has not been collected for one it does.
Download Markdown ↓Two different requests exist, and they do different jobs.
- The app is not in the catalogue. Add it yourself with a link. It is admitted immediately.
- The app is in the catalogue but a tab is empty. Record a data request. It saves demand; it does not collect on the spot.
Adding an app that is missing
Go to /emerging and use Add an app you found. Paste one of these:
- A numeric App Store ID, for example
1499198946. - An App Store URL containing the app's
/idsegment, for examplehttps://apps.apple.com/us/app/example/id1499198946.
Then press Add to the board.
This is the requested lane. It has no rating floor and no launch window, so a small or brand new app is welcome. See Emerging apps for how the lanes differ.
What is accepted
Only Apple. A URL from any other host is rejected with Only Apple App Store URLs can be added as iOS competitors, and a URL with no /id segment is rejected with a message saying so. Text that is neither a number nor a URL asks you for one of the two.
The app is then looked up on the US storefront. If Apple has no app with that ID there, you get Apple has no app with that id in this storefront and nothing is stored.
What happens next
On success the message line reads Observed and added to the board and the app appears on the board straight away.
At that moment the app is admitted with what the lookup returned: its name, its release date, and its rating count. That rating count becomes the app's baseline, and the app starts as Watching.
The app is now in the catalogue. It is findable by name in search, and it has a case file. The rest of the listing detail, such as category and developer, fills in when store metadata is collected for it. Nothing is invented in the meantime.
Adding the same app twice does not create a duplicate. The existing record takes a new observation instead.
Asking for evidence that has not been collected
Open an app's case file. Where a tab has nothing collected, it says so and offers a Request data button. The button appears on:
| Where | What it asks for |
|---|---|
| Overview | Paid ads, organic content, ASO |
| Organic tab | Organic content |
| ASO tab | ASO |
| Listing and about tab | Listing history |
Press it once. It changes to Requested and stays that way. Repeating the request is harmless; it records the same demand rather than a second one. Each account can register one request per kind per app.
If the request cannot be saved you get Could not save your request. Please try again.
What a data request actually does
It records that you want that evidence for that app. That is the whole promise. It does not queue a purchase, it does not schedule paid collection, and it does not put a date on anything.
One exception: an ASO request on an iOS listing also asks for title discovery collection on that app, so its keyword coverage can start filling in. Every other kind records demand only.
A request never invents data. Until something is actually collected, the tab keeps saying nothing was collected rather than showing a guess. Reading the evidence covers how absences are shown.