Skip to main content
When you finish this guide you have one tracked app, its first metadata snapshot and a set of keywords already tracking in its home storefront.

Import from a store URL

1

Copy the store URL

Any public listing URL works, for either store.
A bare iTunes numeric id is also accepted.
2

Paste it into the import dialog

asobeast parses the store and the storefront from the URL.
3

Confirm the home storefront

The country segment in the URL becomes the home storefront. apps.apple.com/de/... imports a de home market. A bare id, or a URL with no country segment, falls back to DEFAULT_COUNTRY, which defaults to us. The dialog lets you override it before importing.
The home storefront is not just a label. It decides where snapshots, category ranks and reviews are collected. See Countries and markets.

What happens on import?

Three things, in order.
  1. The listing is fetched and snapshotted. asobeast stores the parsed fields and the raw payload, so a later parser fix can reprocess history rather than recollect it.
  2. Keywords are extracted from the indexed fields and auto tracked. Each one carries the source it came from.
  3. The first checks are enqueued. Positions appear after the next daily pipeline run rather than immediately.
Auto tracked sources differ by store, because the stores index different fields. See App Store and Google Play for the full field comparison.

Refresh a listing

Refreshing fetches the listing again, writes a new snapshot and returns the difference against the previous one, so the response is meant to be read rather than discarded. Field level changes also land in the changes feed, where they are kept alongside changes asobeast detected on its own schedule. See Watch listing changes.

Troubleshooting

  • The URL is rejected. The parser accepts App Store listing URLs, Google Play details URLs and bare iTunes ids. A search result URL, a developer page or a shortened link will not parse. Open the listing in a browser and copy the address bar.
  • The app exists in one storefront but not another. Storefronts carry different catalogs. Import using a URL for a storefront where the app is actually published, then track keywords in the other market.
  • The import fails with a parse error. A store response shape changed. The job fails and BullMQ retries it with backoff, so check the queue dashboard at /admin/queues for the retry state. Request handling is unaffected. See The daily pipeline and rate limits.
  • Positions are empty after importing. Expected. The first position check runs on the next daily pipeline, which defaults to 03:00 UTC.

Track keywords

Add keywords, add markets and paste the iOS keyword field.

Track competitors

Competitors cost no extra store requests on keywords you already track.
Last modified on July 31, 2026