SDK footprint
An SDK footprint is the full set of third-party SDKs found in an app or, from the vendor side, the apps and installs an SDK reaches.
From the app side, the footprint is the list of SDKs detected in an app's build, grouped by purpose: ads and mediation, analytics, attribution, payments, messaging and so on. It works like a technology profile. Two apps in the same category can look alike on the store and run completely different stacks underneath.
From the vendor side, an SDK's footprint is its reach: how many apps include it, in which categories and countries, and how many installs those apps represent. Weighting by installs matters, because an SDK inside 50,000 tiny apps can reach fewer people than one inside 500 large ones. Measured install counts make that weighting more reliable than download estimates.
Footprints feed sales prospecting, competitive analysis, partnership research and privacy reviews. A sales team can list apps that use a rival product, or apps in a category with no attribution SDK at all. A developer can compare their stack with category leaders before choosing a vendor. Keep two limits in mind: detection shows presence in the version that was scanned, not active use, and footprints change with every release, so check the scan date before acting. The guide to finding SDK sales leads with app data walks through the workflow.
Start with real numbers today
Free forever plan. No card needed. Upgrade when AppMetis earns it.