How to Read Attributed Downloads and App Opens for App Store In-App Events
Use App Store Connect event metrics to separate discovery, attributed downloads, and event-related app opens.
An App Store In-App Event card can introduce the app to someone new or bring an existing user back. The In-App Events report separates these outcomes. Pick the metric that matches the event's goal before judging the result.
Read the event as a short funnel
| Question | What to look at |
|---|---|
| Did people see the event? | Event impressions and event page views |
| Did it bring in new or returning installers? | Downloads and redownloads attributed to the event |
| Did people open the app through the event? | App opens attributed to the event link |
Compare one event against another only when their observation windows and goals are similar. A holiday event designed for existing users can have strong app opens and few first-time downloads. That is not necessarily a weak outcome. Apple requires at least five first-time downloads attributed to an event before displaying its analytics. An empty event report should not be read as zero app opens.
Separate the App Store result from in-app success
Start with one primary outcome: event-attributed downloads for acquisition, or app opens for re-engagement. Then measure the action you care about inside the app, such as starting a challenge. Keep store outcomes and SDK events in separate columns unless you have a documented way to connect them. A jump in app-wide installs during the event does not make those installs event-attributed.
Use your acquisition reports to flag changes in other channels, such as an ad campaign that started on the same day. This context helps explain movement without assigning it all to the event card.
