SDKs, or Software Development Kits, are the handy bits of code installed in a mobile app to improve performance (say, analytics or crash reporting ), offer a feature (social sharing or paying), or enhance revenue generation through UA or video advertising. There are plenty of SDK use cases we could discuss, but for now, let's dive into how SDK recognition technology works.
When a developer wants to work with a new service provider to offer a feature like push messaging or advertising, they install a few lines of code into the app. To activate the feature for users, they must push out an update. This causes the app to be re-downloaded with the newest version installed. Most of us set our phones to 'auto-update' our apps and barely realize the change. The same is true when an SDK is uninstalled. Nothing happens without pushing out an update.
The key to factual SDK recognition is in the update. By running a unique process every time an app pushes out a new release, a granular timeline of SDK installs and uninstalls is possible. Here's how:
Going forward, these 'fingerprints' are recognized and can tell the story of when an SDK is installed or uninstalled. More detail about how recognition works, and whether a live-scan is possible, is available in this quora post.