We match a public AdScan ad’s direct store URL to an exact App Store or Google Play ID in our catalog. We only include records reported active at collection, with a start date in the last 90 days. Activity flags can lag; collection dates are shown.
No. We select sufficiently long ad copy using a conservative English-language heuristic. Audience targeting countries are unavailable. Multilingual copy can be misclassified, and short English ads may be excluded.
No. Counts describe unique records in a bounded daily source sample. They are not total live ads, unique creative concepts, spend, conversions or ROAS. Open the source ad to investigate further.
Collection is scheduled daily and successful results are cached for 24 hours. Errors retain the last successful snapshot; advertising records disappear from the fresh desk after three days without an update.
All existing app profile URLs, category pages, rankings and charts remain available. The previous homepage discovery desk is at /discover, linked in the navigation.
Legacy profiles contain third-party estimates, not audited accounts. Public Apple metadata refreshes do not update financial estimates. Compare collection dates and platform coverage; see our methodology for limitations.
No. This integration reads AdScan’s public discovery records. It does not read customer campaigns, budgets, private boards or performance data from AdManage.
Study the messaging, format and store destination as inspiration for your own tests. An observed ad is not proof of effectiveness, an endorsement or permission to reuse another advertiser’s creative.
