Appy

Measurement and attribution

What is an in-app event?

Short answer

An in-app event is an action a person takes inside an app after installing it, such as a registration, a completed level, a subscription or a purchase, recorded with a name and often a value. Tied to the source of the install, events show which campaigns and links bring users who actually do something.

What counts as an event

Anything you decide matters. Common ones are sign-up, tutorial completed, add to cart, purchase, subscription started and subscription renewed. Each event has a name, a timestamp and optional properties, such as an amount and a currency for revenue.

A short list is better than a long one. Pick the few events that mark real progress towards revenue, name them consistently, and keep the names stable. Renaming an event halfway through a quarter splits its history in two.

It also helps to separate one-time events from repeatable ones. A registration happens once per user. A purchase can happen many times, and each one needs its own amount so that revenue adds up correctly.

How events are sent

The app reports events through an SDK, or your backend reports them server to server. Server-side events suit things the app does not see, such as a subscription renewal or a refund.

When both the app and the backend can report the same purchase, a deduplication ID makes sure it counts once. Events can then be forwarded to an ad network or to your own systems as a postback. Never put personal data such as an email address into event properties.

Timing matters as well. An event can only be credited to a link or a campaign if the install itself was attributed first, so initialise the SDK before sending anything, and include a stable user ID once the person signs in.

Why they matter for attribution

Install counts say how many people arrived. Events say what they were worth. Two campaigns with the same cost per install can differ several times over in purchases per install, and only events reveal that.

Ad networks also use events to optimize: a campaign aimed at purchases needs purchase events flowing back. On iPhone, the SKAdNetwork conversion value is a compressed form of the same idea. On Appy, in-app events and revenue are credited to the link behind the install, through the SDK on the Enterprise plan.

ExampleA purchase event
{"event": "purchase", "revenue": 9.99, "currency": "USD", "dedup_id": "order_1042"}

Try it here

Know which link brought each install

The Appy SDK credits installs, in-app events and revenue to the link, QR code or campaign that brought them.

  • Installs, events and revenue for each link and QR code
  • Verified installs from Universal Links, click IDs and store referrers
  • Apple Ads, Google Ads and Meta installs credited to their network
  • Postbacks and webhooks for every install and event
Read moreInstall Postbacks and Webhooks, ExplainedHow a network’s click ID travels from the click to the install and back, and how to receive postbacks and webhooks safely.

Frequently asked questions

What is the difference between an install and an in-app event?

An install, as attribution tools count it, is the first time the app is opened. An in-app event is anything recorded after that. Installs measure reach, and events measure whether the people who arrived did anything useful.

What is an in-app event on the App Store?

That is a different thing with the same name. Apple uses “in-app events” for timely happenings inside an app, such as a competition or a premiere, which developers can promote on their App Store product page.

Which in-app events should I track?

Start with the steps between install and revenue: registration, the first key action in your app, and purchase or subscription. Add more only when a decision depends on them. A short, stable list is easier to trust.

  • Postback

    A postback is a server-to-server message that reports an app install or an in-app event, such as a purchase, to an ad network or to your own server. When it goes to your own server, it’s usually called a webhook. Postbacks are often signed, so the receiver can check they are genuine.

  • Install attribution

    Install attribution is the step that credits a new app install to the link, ad or campaign that caused it, or marks it as organic when no source is found. It joins two moments that the app store separates: the tap before the install and the first time the app is opened.

  • Mobile attribution

    Mobile attribution is working out which ad, campaign or link brought an app install or an in-app action, such as a sign-up or a purchase. It can be deterministic, based on a click ID, the install referrer or the link that opened the app, or probabilistic, based on statistical matching.

All glossary terms

One link for every phone

Create a free smart link and QR code that sends iPhones to the App Store, Android phones to Google Play and desktops to your website.