Definition
An in-app event is an action recorded inside an app and sent, with its name and parameters, to the app's analytics and measurement tools. The guide to deep links and app analytics events describes events as the raw material of every metric an app is judged by: activation, retention, conversion and lifetime value are all computed from them.
The term is used for actions inside an app, not for website conversions or for the install itself. Web pages send events through a site tag; apps send them through an SDK, and they reach ad networks through postbacks rather than a pixel. Some events are collected automatically, such as first opens and screen views; the ones marketing usually means are the activation, value and revenue events the team defines.
From installs to in-app events
Install campaigns start with the install because it is frequent enough for a network to learn from. The TikTok setup for app installs recommends staying on the install goal while the chosen in-app event is too rare for delivery to learn from, and moving to the event once it is reported in steady volume. The event should be the action that best predicts a user who stays, not the one easiest to count.
The Google Ads setup for app installs describes a good candidate: it happens soon after install, is performed by most users who stay and is rare among those who leave, such as finishing onboarding or creating a first project. A purchase is the truest signal but often comes too rarely and too late to train bidding. That guide keeps an install campaign for volume beside a second campaign bidding on the event.
How the network learns is explained in the guide to app attribution, MMPs and SKAdNetwork: when a campaign optimises towards an in-app event, the network chooses whom to show ads to based on which earlier users performed that event, and it only knows because the measurement partner or its own SDK told it.
In practice: the event taxonomy, testing and iOS limits
Events start as a written taxonomy: the agreed list of events, their names, parameters and meanings, written before instrumentation from the questions the business needs answered. The deep links guide asks for one activation event per app, agreed across teams and sent to the measurement partner and the networks, and for recommended event names wherever the analytics platform documents one.
Before spend, the app install campaign launch checklist asks for the attribution SDK to report installs and in-app events from a test device, for the events the campaign will optimise towards to be mapped, and for the SKAdNetwork conversion value schema to be set and documented. The attribution guide adds that the event a campaign optimises to must be defined identically in the app, the measurement partner and the network, and that postbacks should fire close to real time.
iOS adds a constraint. Post-install behaviour reaches networks as a conversion value the app updates within limited windows after install, so which in-app events can be reported depends on the scheme configured in the measurement partner, agreed with the product team before launch.
A puzzle game moves its campaign from installs to a level event
Skaffesk Puzzle Game ran an Android install campaign at a cost per install of £0.90, but only 6% of those installs were still playing a week later and 1% ever paid. Its analytics showed that players who completed level three on their first day were far more likely to return. The team made "level_3_complete" the activation event, sent it through its measurement partner and confirmed it from a test device. Once the event was arriving at around 80 a day, it set up a second campaign optimising towards it. The cost per install in that campaign rose to £1.60, but the share of installs that went on to pay rose to 2.4%, so paying players per £1,000 spent rose from about 11 to 15.
Related terms
A PostbackA server-to-server message reporting a conversion, install or in-app event back to the ad network or affiliate platform that should receive credit. is the server-to-server message that carries an in-app event to the network that should receive credit, and an MMPAn independent service that attributes app installs and in-app events across ad networks. is the independent service that attributes installs and events across networks and forwards them. When a campaign is set to pursue an in-app event, that event becomes its Optimisation EventThe conversion event an ad set or campaign is told to optimise delivery towards, such as a purchase, lead or install.. A Deep LinkA link that opens a specific screen inside a mobile app rather than its home screen. decides where a tap lands inside the app, and the events recorded after it show what the person did once there.
Common confusions
- More events reported means better optimisation. Sending every event the app records is noise; networks need the install, the target event and a few supporting ones.
- The best event to optimise towards is a purchase. It is the truest signal but often too rare and too late for bidding to learn from; an early action that predicts retention is the usual alternative.
- An event means the same thing everywhere. It must be defined identically in the app, the measurement partner and the network, or the campaign optimises towards something different from what is reported.
- iOS reports events like Android. On iOS, post-install behaviour is compressed into a conversion value, so the reportable events are fixed by the scheme agreed before launch.
- Switching to an event goal on day one is fastest. Without steady volume, delivery cannot learn; start on installs and move when the event is frequent enough.
