StoreGit Help & FAQ

StoreGit is a macOS developer tool that creates a persistent history of App Store metadata and connects that history with keyword rankings and App Store performance.

The simple positioning: Git for App Store metadata.

App Store Connect primarily shows the current state of your listing. StoreGit helps you keep a history of what you have tried over time — so you can see what changed and when.

StoreGit is a companion to App Store Connect, not a replacement. You still manage apps, releases, and submissions in App Store Connect.

To use StoreGit you need:

• A Mac
• An App Store Connect account
• App Store Connect API credentials
• At least one app accessible through that account

StoreGit currently focuses on Apple’s App Store ecosystem.

StoreGit uses Apple’s App Store Connect API. In StoreGit you enter:

• Issuer ID
• App Store Connect API private key (.p8)

StoreGit fills in the Key ID from the .p8 file when it can. If it cannot, or if you need to correct it, StoreGit shows the Key ID field so you can enter or edit it.

To create or find these in App Store Connect:

1. Sign in to App Store Connect.
2. Open Users and Access, then the Integrations tab.
3. Select App Store Connect API and keep the Team Keys tab selected.
4. Click Generate API Key or the Add (+) button.
5. Give the key a name and choose an access role, then generate it.

View App Store Connect role requirements →

6. Copy the Issuer ID shown on that page.

7. Download the .p8 private key. Apple lets you download it only once.
8. If StoreGit does not fill in the Key ID after you add the .p8 file, copy the Key ID from App Store Connect.

For Apple’s official steps, see Creating API Keys for App Store Connect API.

Protect your .p8 private key. Treat it like a password — do not email it, commit it to git, or share it.

StoreGit features require different App Store Connect user roles and permissions. Timeline and Rankings — listing history and keyword positions — share one access level. App Info is filled from that Timeline data; it needs a separate permission only to edit and save listing metadata. Analytics needs reporting access. Choose the least-privileged role that covers the features you need, and give the key access to the apps you want to use in StoreGit.

View App Store Connect role requirements →

StoreGit is local-first. Metadata history, keyword rankings, App Store analytics that StoreGit displays, and StoreGit’s local database are stored on your Mac.

App Store Connect credentials are stored in the macOS Keychain. Cached app data lives in a local SQLite database under Application Support, one file per App Store Connect account.

StoreGit does not run a backend that stores your App Store metadata. See the Privacy Policy for a short summary.

No. Your Issuer ID, Key ID, and .p8 private key stay on your Mac and are stored in the macOS Keychain.

StoreGit uses those credentials locally to talk to Apple’s App Store Connect API. They are not uploaded to a StoreGit server.

StoreGit’s application data is local-first. StoreGit does not use a StoreGit backend to store your App Store metadata, keywords, rankings, or App Store analytics.

StoreGit does talk to Apple — App Store Connect for apps, metadata, and analytics reports, and Apple’s public search API for rankings.

If you use Translate in App Information, the selected metadata text is sent to the translation provider for that request.

If anonymous product-usage analytics are enabled, that telemetry is separate from your App Store data. It does not include:

• App names
• Bundle IDs
• App Store metadata
• Keywords
• Ranking positions
• App Store analytics values
• App Store Connect credentials

Not in the current app. StoreGit does not currently collect anonymous product-usage telemetry.

App Store performance data comes from App Store Connect and is stored in StoreGit’s local database on your Mac. If a future build enables anonymous product-usage telemetry, that data would be separate and would not include your App Store data.

StoreGit cannot reconstruct a complete historical timeline from before you started using it.

History accumulates as StoreGit observes and stores metadata snapshots after you connect and sync. Installing StoreGit will not immediately reconstruct years of listing changes.

Some information can be retrieved from App Store Connect on first sync — for example, versions and localizations Apple still exposes. That is not the same as a complete StoreGit snapshot history of every past live listing. Identity fields such as name and subtitle are especially limited: App Store Connect primarily exposes the current live and in-flight values.

StoreGit currently tracks these fields, including their localizations where Apple provides them:

• App name
• Subtitle
• Keywords
• Description
• Promotional text
• What’s New
• Screenshots
• App previews
• App icon

StoreGit uses a Git-inspired mental model. It is not a Git repository.

A StoreGit commit is a snapshot of App Store metadata at a point in time. When something actually changes, StoreGit records that snapshot so you can inspect the change and compare versions.

In App Information, Commit also means pushing your current drafts to App Store Connect. Timeline history is the local record; committing from the editor is how edits go back to Apple.

You can always look at historical metadata in the Timeline.

For text fields — name, subtitle, keywords, description, promotional text, and What’s New — Restore copies a previous released value into the editor. Nothing is pushed to App Store Connect until you Commit.

Screenshots and app previews are stored in history, but Restore is not available for those fields.

StoreGit does not automatically roll back an entire listing. Restore reuses a previous value in the editor; you choose whether to send it to App Store Connect.

Rankings are primarily forward-looking. StoreGit can start observing a keyword after that keyword and region are being tracked.

Historical rankings from before tracking began are generally not available. There is no official App Store rank history API to backfill from.

StoreGit automatically tracks words found in name, subtitle, and keyword metadata.

For each tracked country, StoreGit uses that storefront’s default localization when the app provides it, and it also includes the app’s primary locale in every region. Other localizations are not automatically mined for every country.

You can add keywords manually. Terms you hide are not tracked.

App Store search results are storefront- and region-specific. Language, localization, competition, popularity, conversion behavior, and other factors can differ by territory.

StoreGit therefore tracks keyword rankings per selected region, not as a single worldwide position.

Ranking checks require requests across storefronts and keywords. Tracking more countries substantially increases update time and resource usage.

You can choose the countries that matter to your app rather than automatically tracking every App Store territory. Automatic refresh is currently limited to 25 countries per app. You can still check an untracked country when you select it — it just is not included in automatic refresh.

App Store metadata is localization-based (en-US, ja, and so on). Rankings and analytics are territory-based (United States, Japan, and so on).

StoreGit maps each localization to a home territory so region selection is easier. That mapping is a StoreGit heuristic, not a concept Apple defines as Localized Regions.

Localized Regions are derived from your metadata locales. They are not favorites, and they are not the same as the countries you choose to track.

StoreGit retrieves supported App Store performance data from App Store Connect — specifically the Analytics Reports API.

StoreGit does not independently measure downloads, impressions, page views, or conversion. It displays the reports Apple provides, cached locally on your Mac.

Rankings are primarily forward-looking. Analytics can provide backward-looking performance context.

Rankings show how an app appears for tracked search terms over time. Analytics shows broader App Store performance metrics such as impressions, page views, downloads, and conversion.

No.

StoreGit can help you identify correlation and directional evidence around changes. For example, a keyword ranking or search performance metric may improve after a metadata change.

Many external factors can affect App Store performance — competition, seasonality, featuring, conversion, and changes Apple makes to search. StoreGit does not establish that a metadata change caused a result.

App Store indexing and ranking changes are not guaranteed to occur immediately, and Apple does not publish a fixed period for ranking impact.

Evaluate changes over a meaningful period rather than treating short-term movement as definitive evidence.

Yes. The public beta is now open.

Functionality, interfaces, and data models may continue to evolve. If something looks unexpected, please report it.

StoreGit intends to preserve beta data where possible. Because this is beta software, migrations or occasional resets may still be necessary.

Some updates rebuild caches from App Store Connect. Your App Store listing itself stays in App Store Connect; StoreGit’s local history may need to be re-synced after a migration.

Use Help → Send Feedback… inside StoreGit, or email support@sarvalabs.app.

Useful reports include:

• What you were trying to do
• What happened instead
• Steps to reproduce
• StoreGit version
• macOS version

Never send your App Store Connect private key or credentials in a support message.

Work through this checklist:

• Verify the Issuer ID
• Verify the Key ID
• Confirm the correct .p8 key is selected
• Confirm the API key has the right App Store Connect access
• Confirm the key has not been revoked
• Check your internet connection
• Retry later if App Store Connect or the API is having a temporary issue

Do not send your Issuer ID, Key ID, or .p8 private key to support.

StoreGit lists the apps returned by App Store Connect for the API key you connected. Check that:

• The API key has access to the app
• You connected the correct App Store Connect account or team
• The app is visible in App Store Connect
• You refresh or pull again

Archived apps are hidden from the default list and appear under Archived. If the first fetch was incomplete, try pulling again so the full app list can load.

Ranking updates can take time depending on how many keywords and regions you track, and on whether Apple’s search API is available.

• StoreGit captures a rank once per keyword, region, and UTC day
• Background refresh runs once per local calendar day at the time you choose in Settings
• Countries that are not in your tracked list are not included in automatic refresh
• A larger tracked set takes longer to finish

Common causes:

• App Store Connect reports are still generating after the first request — this can take a day or two
• No data is available for the selected period or territory
• The API key does not have Analytics report access (Admin, Finance, or Sales and Reports)
• The app is new or has little activity
• Apple has temporarily limited report availability

StoreGit’s analytics window also excludes today. Apple does not publish a guaranteed reporting delay, so missing recent days can be normal.