Definition
SDK stands for software development kit. In app marketing it means code a vendor supplies for the app's developers to build in, so that the app records events and reports them back. The guide to app attribution, MMPs and SKAdNetwork describes the measurement partner's version: its SDK runs inside the app, records the install and later events, and matches each install to the ad interaction that most plausibly caused it.
The defining feature is where the code lives. A pixel or tag watches a browser from a web page; an SDK runs inside the product on the user's phone. The Meta Ads setup for app installs puts the difference plainly: an app campaign's signal has to come from code inside the app.
The kinds
The guides name three, which often sit in the same app.
- Analytics SDK. Counts first opens and in-app behaviour for the team's own analysis. It records a first open only when the app is launched with the kit running, so it never sees someone who downloads and never opens.
- Measurement partner SDK. Records installs and events, attributes them across networks under the advertiser's rules and tells each network what it has been credited with.
- Ad network SDK. A network's own kit, which reports installs and events back to that network so its delivery can optimise. Each network attributes to itself under its own rules.
In practice
Release timing. An SDK reaches users only when an app update containing it is published, so a kit added after launch leaves a gap that cannot be filled afterwards. The guide to launching a new app expects the measurement partner to be chosen, its SDK in the build and its links set up before paid campaigns start, and events tested before any money is spent.
Reconciliation. Each kit counts something different, so the totals never agree. The tutorial on reconciling app install numbers starts its search for a sudden gap on the team's own side: a release that changed an SDK, its initialisation or its consent handling can drop first opens on one platform.
Ownership and consent. The mobile measurement hub asks the measurement plan to name an owner for each tool, and notes that every kit collecting data on users needs to be listed in the app's privacy disclosures and consent flow. A kit that collects before consent where consent is required is a fault, not a setting to tidy up later.
A recipe app spends before the code ships
Jaskerow Recipes, an invented recipe and meal-planning app, started paid install campaigns on two networks the week after launch. Its measurement partner was contracted, but the partner's SDK was due in version 1.3, which the app store review delayed by 11 days. In that fortnight the networks between them claimed 5,400 installs, the store console showed 4,100 downloads and the analytics SDK counted 2,950 first opens, and nothing could say which campaign had produced which subscriber. The team paused further spend until 1.3 was live, tested the install and the trial-start event on both platforms, and only then restarted, writing the SDK release into the launch plan for its next market.
Related terms
An MMPAn independent service that attributes app installs and in-app events across ad networks. is the measurement partner whose SDK attributes installs across networks. An In-App EventAn action recorded inside an app, such as a sign-up, trial or purchase, reported through the measurement partner or SDK and used to optimise campaigns. is an action the SDK records inside the app, such as a sign-up or purchase, and reports for optimisation. 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 passes the SDK's results on to the network that should receive credit. A Deep LinkA link that opens a specific screen inside a mobile app rather than its home screen. opens a specific screen in the app; for new installs the deferred link is often supplied by the same measurement partner whose SDK attributes the install.
Common confusions
- An SDK is the same as a conversions API. The SDK runs inside the app on the user's device. A conversions API shares events from the business's server, which is a different route.
- It can be added whenever measurement is needed. It ships only with an app release, so anything that happened before the release is not recorded.
- One SDK is enough. The analytics kit, the measurement partner and the networks each answer a different question, and their counts differ for structural reasons.
- It is a developer's concern. Marketing relies on its data, so marketing needs to know which kits are in the build, who owns each and what consent covers them.
