Building a Reusable Asset Library for Ad and Concept Testing¶
A team running frequent concept and ad testing - a creative agency cycling through client rounds, a brand team iterating on packaging, a product team testing UI concepts sprint over sprint - ends up touching the same handful of core assets over and over: a product shot used in three different Stimulus Section tests, a logo lockup tested against five different backgrounds, a demo video reused across several rounds of feedback. Without a shared library, each new test means re-uploading the same file again, and duplicating a past test to iterate on it means uploading it a second time on top of that.
The Media Library - covered in full in our guide on reusing images and videos across surveys - is exactly the tool for this, and it's worth thinking about deliberately once concept testing becomes a regular part of how your team works, not just an occasional one-off.
Treating It as an Actual Library, Not Just an Upload History¶
The difference between "a place files happen to end up" and "a library you actually work from" is naming and organization. Upload assets with names that mean something months later ("Packaging Concept A - Front" rather than whatever filename your camera or design tool generated), and the library stays genuinely useful as it grows, rather than becoming a long, unsearchable scroll of unlabeled thumbnails.
Uploading Ahead of the Test, Not During It¶
For a planned round of testing - a batch of ad creative variants coming in from a design team, a set of packaging renders for an upcoming review - upload everything to the standalone Media page before you start building the actual Stimulus Section or Pairwise Comparison test. This separates "getting the assets into the system" from "building the test itself," which tends to go faster when you're not doing both at once, and means the assets are already available to pick from the moment you start building.
Reusing Across Iterations, Not Just Across Tests¶
The clearest payoff shows up when you're testing successive versions of the same concept - round one tests three logo directions, round two tests the two survivors against two new variants. The two survivors from round one are already sitting in your library; there's no need to re-upload them for round two, and picking them straight from the library guarantees you're testing the exact same file both times, not a re-exported or re-compressed version that might introduce a subtle difference between rounds.
What This Looks Like for an Agency Running Multiple Clients¶
If you're managing concept testing across several client accounts, naming discipline matters even more - a consistent convention (client name, concept, version) keeps one client's assets from getting confused with another's as the library grows across projects. Since assets are scoped to your own account, everything sits in one library regardless of which client or project a given test belongs to, which makes clear naming the main thing standing between a genuinely useful library and a hard-to-navigate one.
FAQ¶
Does reusing an asset across multiple clients' tests cause any conflict or mixing of data?
No - the asset itself is just a file; each Stimulus Section or Pairwise Comparison test that references it is otherwise completely independent, with its own questions, its own responses, and its own results.
Is there a limit to how large my library can grow?
See our guide on reusing images and videos across surveys for what's covered there; the practical limit that matters most day to day is how easy your library stays to search and navigate as it grows, which naming discipline addresses more directly than any hard limit would.
Can I clean up assets I no longer need without affecting past tests?
Removing an asset from your library doesn't retroactively affect results already collected from a test that used it - but it's worth checking whether any current, still-running test still references it before removing something you're not sure is fully done with.
See Reusing Images and Videos Across Surveys with the Media Library for the full mechanics.