From Ad Candidate to Static Preview: Batch Research and Cloning

Finding one good ad is luck. Finding a pattern is process. This guide covers the batch workflow: importing in bulk, keeping your library free of duplicates, and moving from research to your own ads.

Batch import from Meta

In the Ad Library, open Import from Meta. You choose a keyword or advertiser and a country — the import queues a search job rather than filtering ads already in the library. That distinction matters: imports pull new source data, while filters only slice what you already have.

• Queued → Running → Completed: follow the job status in Recent imports.
• If the import executor is not running, jobs stay queued and will not finish until it is back — this is surfaced in the UI rather than failing silently.
• Imported results land in the library with full source disclosure, so you always know where a record came from.

How dedup keeps your library clean

The same ad appears in many searches. Instead of storing it twice, TexoAI keeps one canonical record per source ad ID:

• Ads already in the library are matched and reported as "already in library".
• A search also triggers a bounded refresh from Meta — not a complete real-time index, and clearly labeled as such.
• Progress shows "X imported or updated so far", so you can see the job is moving even when results arrive in batches.

The result: your boards and exports contain unique ads, and re-searching a brand costs you nothing in duplicate cleanup.

Date ranges and partial data

Scraping a long date range hits Meta's first-batch cap quickly. The import slices ranges — down to day-level when a month hits the cap — so you get complete coverage instead of silently truncated results. If a refresh is partial, records are marked partial or source unavailable, never mislabeled as stopped.

From library to production

Once the library is clean, production starts:

1. Pick a winner from your shortlist board.
2. Clone it with Ad Clone: choose the ad as source, set your brand profile and product, and generate static on-brand variants.
3. Track the job — credits are reserved, captured on delivery, and released on failure, so retries never double-charge.
4. Export your researched ads when you need to share or archive them.

Keep it honest

A batch library is only useful if you trust the labels. TexoAI never claims performance numbers it does not have: if a field is missing from the source it stays unavailable, and if a refresh missed a scrape it says "source unavailable", not "stopped". Build your process on that and the library stays a reliable asset.