App Store Integrations

Without a store connection, the install numbers in your dashboard are third-party estimates. Connect your App Store Connect and Google Play accounts from Settings → Integrations and Noise reads your real install data straight from the stores instead: it flows into your dashboard metrics, the Reporting API, and AI clients as first-party data (see Understanding Your Metrics for how the two sources merge).

Both integrations are read-only: Noise can see reporting data, and nothing else.

Connecting App Store Connect

You will paste a read-only API key:

In App Store Connect, open Users and Access → Integrations.
Create an API key with the Sales and Reports role (read-only) and download the .p8 file.
On the Noise Integrations page, paste the Issuer ID, Key ID, and the .p8 contents, then click Validate key.
Pick the app Noise should pull install data for, and connect.

The one-time Admin key step

Apple only produces install reports for apps that have analytics reporting enabled, and enabling it requires an Admin key: the read-only key cannot do it. If your app already has analytics reporting on (it does if you use tools like RevenueCat or Adjust), your connection completes immediately and this step never appears.

Otherwise, the page asks for a second, one-time Admin key. It is used once to enable reports and never stored; you can revoke it in App Store Connect immediately afterwards. Only the read-only Sales and Reports key stays with Noise.

Prefer not to paste an Admin key at all, even transiently? Your team can enable analytics reporting yourselves via Apple's API (there is no App Store Connect UI for it): see "Downloading Analytics Reports" in Apple's developer documentation, then connect on Noise with just the Sales and Reports key.

After a fresh enablement, Apple takes 24 to 48 hours to generate the first report data.

Connecting Google Play

No keys change hands for Google Play. Instead, you invite a read-only Noise service account:

In Play Console, open Users and permissions and invite the Noise service account shown on the Integrations page, with the account-level permission "View app information and download bulk reports".
In Play Console, open Download reports → Statistics and copy the Cloud Storage URI: the part starting with pubsite_prod.
On the Noise Integrations page, enter your app's package name and that bucket ID, then connect.

Play Console permission grants can take anywhere from a few minutes to a day to become active. If access is not live yet, your connection is saved as Waiting for access: use the Check access button to retry once the invite has propagated.

What Noise reads, and how credentials are stored

Apple: daily install counts (first-time downloads and redownloads; app updates and restores are excluded) and installs by source type and campaign, from Apple's installation reports.
Google: daily user installs from your statistics exports, and store acquisitions by traffic source.

Your Apple .p8 key is stored encrypted (AES-256-GCM) and is only ever used to download these reports. The one-time Admin key is never stored anywhere. For Google there is no credential at all: you can see and revoke the service account's access in Play Console at any time, and disconnecting on the Noise side deletes the stored connection details.

Install totals vs attribution sources

The stores report two different measures, and Noise keeps them separate:

Install totals: how many installs your app got each day. These power the install metrics in your dashboard and reports.
Attribution sources: where installs came from (search, browse, referrals, campaigns for Apple; traffic sources for Google).

For Google in particular, the by-source numbers come from a different report than the totals and do not sum to them, so never add attribution rows together and expect the total. Attribution data is collected from the day you connect and will surface in upcoming reporting.

Apple data reaches back only as far as your app has had analytics reporting enabled: if the Admin key step just enabled it, data starts from now; if it was already on, history accumulates from when it was enabled. Google connections backfill your historical install totals on the first pull. Either way, data is pulled daily, and recent days can be revised as the stores finalize their reports (see Understanding Your Metrics).