Public Mobile App Store Presence Agent

Detect public native mobile app distribution evidence from website pages: iOS App Store links, Google Play links, Apple Smart App Banner metadata, Android deep links, app badges, download CTAs, stable hashes, diagnostics, and change-aware useful billing.

What It Reads

• One public website page per input.
• Static HTML links to apps.apple.com, itunes.apple.com, and play.google.com/store/apps/details.
• apple-itunes-app Smart App Banner metadata.
• Native app deep-link hints such as market://, android-app://, and intent:// when they expose an Android package.
• App badge images and app download CTA text as supporting, non-charging hints.

What It Does Not Do

• It does not fetch App Store or Google Play pages.
• It does not install apps, run a browser, execute JavaScript, crawl a full site, audit PWA manifests, collect brand assets, or inspect private account areas.
• It rejects private-network hosts, query strings, fragments, credentials, path parameters, sensitive account paths, and token-like path segments.

Pricing Events

• apify-actor-start: one tiny run-start event when configured in Apify.
• useful-mobile-app-presence-result: charged only for useful, new or changed App Store / Google Play / Smart App Banner evidence.

Deep-link-only records, badge-only pages, CTA-only pages, invalid inputs, failed fetches, duplicates, and unchanged hashes do not trigger the useful event.

apify-default-dataset-item is intentionally not used.

Example Input

{
  "pageUrls": ["https://www.spotify.com/"],
  "requestTimeoutSecs": 20
}

Output Highlights

• mobileAppPresenceType
• detectedPlatforms
• iosAppSignals
• androidAppSignals
• nativeAppDeepLinkSignals
• appBadgeSignals
• appCtaSignals
• riskLabels
• diagnostics
• mobileAppPresenceHash
• changeStatus
• billableEventName