Ad Library Use Cases

The two use cases aren't alternatives so much as different starting points inside the same ad library. If the request is a product — a new SKU, a bundle, a seasonal offer — start with product ads: the playbook is built around a clean product shot and a matching set of placements. If the request is an angle or a testimonial-shaped hook meant for a scroll feed, start with UGC-style hooks instead: the playbook leans into hand-held framing and native pacing rather than a polished product shot.

Most accounts end up running both. A cold-traffic UGC hook earns the first look, and a cleaner product ad closes the sale once someone lands on the product page — two ad creatives doing two different jobs inside the same campaign. Neither workflow requires an account or a credit card to try; generate a first pass from either playbook and see which one matches the brief before committing to a full set.

Still unsure which one to open first? Ask what the ad has to do on its own. A product ad usually has to survive on its own — it needs to look right sitting next to a competitor's listing, which is why the playbook leans on a clean shot and a matching set of placements. A UGC-style hook is rarely meant to survive alone; its whole job is buying the next three seconds of attention before a cleaner ad or a landing page takes over. Neither playbook is more advanced than the other — they're built for two different points in the same funnel.