What Uptika connects to, and what changes when you do

Keyword ranks, popularity and difficulty, category charts, rival listings and reviews are read from the stores' public data; none of them needs a connected account.

Your own downloads, installs, revenue and ad numbers only come in if you connect them. An account you have not connected stays empty and is never filled with estimates. The Listing conversion part of the ASO score also needs Google Play Console data; without it, the part is left out and the remaining weights are re-normalised.

The workspace owner or an admin connects accounts. Connecting is open on every plan; the Analytics, Playbook and Apple Ads pages that show the data open on Starter. Keys are stored encrypted with AES-256-GCM and never shown again.

What it unlocks: your own App Store downloads on the Analytics and Playbook pages: first downloads and redownloads, by source type and territory. The growth part of the Uptika score is computed from this data too.

What Uptika reads: the App Downloads Standard report from App Store Connect Analytics Reports, every 3 hours. The first sync creates one ongoing report request in your account; it changes nothing in your app or your listing. Apple publishes the first report 1–2 days after the first sync; until then the page says it is waiting for the first report.

How to connect:

1. In App Store Connect › Users and Access › Integrations › App Store Connect API, create a key with "Sales" or "Admin" access and download the .p8 file.
2. In Uptika, open Settings › Integrations, click Connect on App Store Connect and enter the Key ID, the Issuer ID and the .p8 file.
3. Save and test: the connection is tried and the result shows on the card.

What the report contains: the App Store Connect Analytics guide.

What it unlocks: installs, uninstalls, active devices, store listing visitors and acquisitions, by traffic source, search term and country. The Listing conversion part of the ASO score and the retention (uninstall rate) part of the Uptika score come from this data.

What Uptika reads: the monthly CSV reports Play Console writes to your report bucket, every 3 hours.

How to connect:

1. Create a service account in Google Cloud and download its JSON key.
2. In Play Console › Users and permissions, give the service account's e-mail the "View app information" and "Download reports" permissions.
3. Get your report bucket address: Play Console › Download reports › Statistics › "Cloud Storage URI" (it starts with gs://pubsite_prod_…).
4. In Uptika, open Settings › Integrations, enter the service account JSON and the report bucket, then Save and test.

Without the report bucket, install, source and country data cannot be read; the dashboard flags this on the card.

What it unlocks: the Apple Ads pages: performance, campaigns, opportunities, your organic rank next to every keyword you bid on, rules and the action log.

What Uptika reads: campaigns, ad groups, keywords, negative keywords, daily reports and search terms, every 3 hours. The first connection reads the last 90 days.

Your budget stays yours: nothing that could raise spend happens without your explicit approval. Every change is written to the action log with its before and after values. API keys cannot change ads.

How to connect:

1. In ads.apple.com › Account settings › API, invite an API user (with the API Campaign Manager role) and upload its public key.
2. Copy the Client ID, Team ID, Key ID and Org ID from the same page.
3. In Uptika, open Settings › Integrations, enter the four IDs and the private key (PEM), then Save and test.

Step by step: the Apple Ads setup guide.

What it unlocks: daily revenue, MRR, active subscriptions, trials, new customers and refunds on the Analytics page. The revenue part of the Uptika score is computed from this data.

What Uptika reads: your project's metrics from the RevenueCat API v2, refreshed when you open the revenue page. A read-only key is enough.

How to connect:

1. In RevenueCat › Project settings › API keys › Secret API keys, create a v2 key (read-only is enough).
2. Copy the project ID from the address bar (it starts with proj…).
3. In Uptika, add the project under Settings › Integrations. You can add several projects; choose which app uses which project under Settings › Apps.

Add channels under Settings › Alerts and channels. There are no e-mail alerts. Events show on the Daily ping screen on every plan.

What it unlocks: the keyword, rank, rival, alert and ad data from the dashboard in the REST API, as JSON with a Bearer key. The MCP server gives the same data to Claude Desktop, Claude Code and other MCP clients as tools.

What it cannot do: the API is read-only; the one write is adding keywords. Apple Ads changes, review replies, team and key management are not possible through the API.

How to connect: create a key under Settings › API and MCP. The key is shown only once; you see when it was last used and can revoke it at any time. The MCP server runs on Node 22 or later over stdio; ready-made configs for Claude Code and Claude Desktop are in the dashboard.

More: API and MCP.