Skip to content
← All products

Public ad research source package

Benchmark public ads before creative.

Turn public Meta Ad Library results into a private benchmarking machine: compare offers, hooks, CTAs, formats, landing domains, platform mix, and active creative windows before you brief a campaign or client report.

Request handoff See what ships
Historical checkpoint
5,003
ad rows · 0 duplicate IDs
Export formats
4
ZIP · CSV · JSONL · JSON
Console routes
7
search, jobs, detail, insights, demo, settings, search all
Included stack
3
Python engine · FastAPI · React/Vite UI
adlib console local demo
Query northwind active ads US · active · max 5000
ad_archive_id
72044...931
page_name
Northwind Co.
publisher_platforms
facebook, instagram
export
manifest.zip
duplicates
0
✓ checkpointed output ZIP · CSV · JSONL · JSON

What you can actually do with it

The value is not just collecting records. The value is building your own ad-intelligence workflow: gather public market signals quickly, review them locally, then turn structured exports into creative direction, client reports, internal dashboards, or research archives.

  • Benchmark a market before spending

    Collect a focused set of public ads around a niche, country, advertiser group, or offer category. Compare CTA mix, destination domains, platform split, active status, creative reuse, and timeline patterns before deciding what angle to test.

  • Build agency-ready research deliverables

    Run the research once, filter it in the console, then hand analysts or clients a ZIP, CSV, JSONL, or JSON package with summaries and manifests instead of scattered screenshots and manual notes.

  • Create a living swipe-file system

    Separate active from inactive examples, group by advertiser or format, tag reusable creative patterns, and keep public references organized for strategists, media buyers, and copywriters.

  • Feed your own data stack

    Use structured exports as input for BI tools, warehouses, classification models, QA workflows, or internal dashboards. The buyer owns the schema and can adapt the FastAPI layer.

What ships in the handoff

Everything transfers as source you own: the working code, the demo data, the docs, and the limitations notes. One price, no subscription, no hosted dependency.

product
Meta Ad Library collection console
price
$3,000
buyer
Media buyers, growth agencies, market researchers, and technical data teams.

included

  • adlib/ collection engine and replay helpers
  • FastAPI local backend with export endpoints
  • React/Vite operator console source
  • Sanitized demo dataset and export builder
  • Tests, docs, sale-package scripts, and limitations notes

components

Collection engine
Browser-assisted bootstrap, browserless pagination path, checkpointing, output indexing, verification, split/merge strategy, and resume-oriented run structure.

How intent becomes output

The operator path, start to finish. Each step is a real command surface, not a promise.

  1. 01

    Plan

    Choose query, country, dates, filters, goal, strategy, workers, and optional proxy settings.

  2. 02

    Collect

    Bootstrap the public Ad Library session, replay pagination, checkpoint output, and preserve resume state.

  3. 03

    Review

    Use table/card views, result filters, transparency panels, tags, diagnostics, and insights inside the local console.

  4. 04

    Export

    Package clean outputs for analysis, buyer review, or internal research handoff.

What's proven, what's excluded

The same diligence a technical buyer would run: what the code demonstrates locally, and what is deliberately left out of a clean handoff.

✓ proven

  • Historical local proof

    Docs record Python tests passing, a Vite frontend build, and a 5k checkpoint summary with 5003 ads, 5003 unique IDs, and 0 duplicates.

  • Buyer-safe demo mode

    Sanitized sample data drives the same export builder as real jobs, so a buyer can inspect behavior without private production datasets.

  • Source handoff framing

    The inventory frames the sale as source code and IP handoff, not a hosted SaaS, data resale product, or managed account service.

! excluded

  • No accounts included

    No Meta accounts, cookies, tokens, browser profiles, proxy accounts, or raw production datasets are part of the default handoff.

  • Platform behavior can change

    Meta surfaces, browser behavior, rate limits, access controls, and export fields can change without notice.

  • Buyer review required

    Buyers should rerun verification in their environment and perform legal, platform, privacy, and operational review before use.

Build it yourself, or start from the source

Build from scratch Pullmesh handoff
Reverse engineer collection, checkpointing, exports, UI, and sale-safe packaging from scratch. Start from an existing Python/FastAPI/React codebase with demo data, docs, tests, and export flows.
Spend weeks discovering edge cases around duplicate IDs, resume cursors, and local review workflows. Use the existing verification, job state, filters, and export manifest model as the starting point.
Create diligence materials after the code is built. Review existing architecture, proof, limitations, and platform-risk docs before purchase.

Request handoff

Own the benchmark loop behind better ad decisions.

Request the handoff to inspect scope, exclusions, transfer terms, and support. You bring the authorized environment and decide how the research workflow should run.

Request handoff