Docs

App Store Asset Library: What to Track

Apple's new Asset Library lets teams pre-approve creative and reuse it across the product page, search, and In-App Events — track it per placement.

Acquisition

Apple’s new Asset Library, arriving in App Store Connect alongside iOS 27 and iPadOS 27 this autumn, changes how creative gets shipped to the App Store. Instead of uploading screenshots and preview videos as part of a single app-version submission, teams can now manage images, videos, app previews and marketing assets in one centralised library, submit them for review independently of a build, and get them pre-approved for future use. The same approved asset can then be reused across three distinct placements: the product page header, search results, and In-App Events.

That reuse is exactly what makes tracking harder. Under the old model, a creative refresh was one event tied to one app version — easy to bracket in a before/after comparison. Under Asset Library, a single approved asset can go live in a header today, get pulled into a search results placement next week, and appear in an In-App Event listing the week after, each with its own visibility and its own conversion behaviour. Teams that keep measuring “creative performance” as one undifferentiated metric will end up averaging together three placements that behave nothing alike — a screenshot that converts well in a considered product-page browse can underperform badly as a rushed impression in a search result, and blending the two hides both signals.

Data Points to Track

  • Asset ID and placement combination for every impression and conversion, so the same creative asset can be compared across product page header, search results, and In-App Events rather than folded into one number
  • Approval-to-live lag per asset, since pre-approved creative can go live independently of an app update and that timing gap needs its own record for attribution
  • Conversion rate by placement, benchmarked separately, to catch a header-optimised asset underperforming when reused in search
  • Impression share by placement for each asset, to understand how much of its total reach comes from where
  • Asset reuse count, tracking how many distinct placements and campaigns a single approved creative gets deployed into over its lifetime

Setup Steps

  1. Assign a stable internal ID to every asset uploaded to the Asset Library that survives being reused across placements, rather than relying on Apple’s per-submission naming.
  2. Log the placement type alongside every App Store Connect conversion export — header, search results, or In-App Events — before aggregating anything into a single “creative performance” view.
  3. Record the approval date and each go-live date separately per placement, since one approval can produce multiple live dates as the asset gets reused.
  4. Build placement-level conversion dashboards first, then roll up to an asset-level summary, so no single high-traffic placement can mask a weak one.
  5. Flag assets nearing their review-approval expiry or platform-version scope so a reused asset doesn’t quietly go stale in one placement while still live in another.

Actionable Insights

Once placement-level data separates cleanly, the useful comparison isn’t “does this asset convert” but “where does this asset convert.” An app preview video that lifts product-page conversion but does nothing in search results is telling you something concrete about attention and intent at each placement — a browsing user versus a searching user reads the same creative differently. That splits your creative roadmap into two real workstreams: assets built to hold attention on a considered visit, and assets built to win a split-second decision in search, rather than one generic “improve our screenshots” backlog.

Expert help

Need help tracking this in your app?

Our team sets up analytics pipelines for mobile and web teams every day. Talk to us and get your first events flowing in under an hour.

Talk to an expert