Use case — keep the database alive

Your publisher database was accurate the day it shipped. Keep it that way.

A vertical's publisher universe runs to tens of thousands of live sites — and it drifts every month. New publishers launch, old ones go dark, and plenty quietly change what they are. Scheduled re-runs over 120M+ classified domains re-screen the whole category against your locked ICP and hand you a clean quarterly delta: what's new, what died, what changed.

120M+
classified domains re-scanned every cycle
tens of thousands
of publishers kept current in a single vertical
3 delta types
new · dead · reclassified
from $499
per quarterly refresh
The job to be done

A static list decays the moment you export it

The first full run gives you a deduplicated universe of qualified publishers. But affiliate ecosystems are living things — and a database that isn't refreshed silently loses value in three directions at once.

New publishers you're missing

Sites that didn't exist — or weren't yet on-topic — at the last run. These are the uncontested names your competitors haven't reached either, and they're only discoverable by re-scanning the full web, not by revisiting a fixed list.

Dead and parked sites

Publishers that expired, went to a parking page, or abandoned the niche. Outreach to a dead domain wastes a rep's day and dents sender reputation. The refresh flags them dead/parked so they drop out of sequences.

Changed classifications

A blog that pivoted, added its own store (a disqualifier), dropped affiliate links, or shifted language/geo. The verdict that was true last quarter may be false now — re-screening against the same ICP catches the flip.

How a refresh cycle runs

Six steps from your baseline to a clean delta

Every cycle repeats the exact pipeline of your first run, with the ICP definition locked so the comparison is apples-to-apples. You review only what moved — not the whole universe again.

1

Lock the baseline

Your last delivered universe becomes the reference snapshot — every canonical domain, verdict, and confidence score, frozen as the state we diff against.

2

Re-scan the full category

The whole vertical is pulled again from 120M+ classified domains — including domains newly classified into the category since the last cycle. Nothing is limited to the old list.

3

Re-screen against the locked ICP

Every domain in scope is read by the LLM against the same required / preferred / disqualifying signal set, so a verdict change reflects the site changing — not the rules.

4

Alive & reachability check

Each known domain is re-fetched. Expired, parked, redirect-looped, or hard-404 sites are marked dead/parked with the date first observed unreachable.

5

Diff against baseline

The diff engine sorts every domain into added, removed, or changed, and for changes records which signals flipped and how confidence moved.

6

Deliver the delta

You get a delta CSV of only what moved, plus a refreshed master universe in the same schema — ready to sync straight into your partner CRM.

A note on confidentiality

The worked example below is drawn from real refresh runs. Because the publishers are independent sites, we follow standard confidentiality practice on public pages: domains are withheld and descriptions generalized, so the figures and profiles shown here are intentionally not traceable to specific sites — including through a web search. That protects the publishers without changing the underlying data. Your pilot and refresh deliverables carry the actual domains and every signal, so everything can be verified directly.

A worked example

One quarter of drift in a mid-size vertical

An illustrative quarterly delta for a program whose last run left them with roughly 41,000 qualified publishers. Every figure below is a labeled estimate extrapolated from calibration slices — your own deltas come from your real baseline and locked ICP.

Added

~1,900 new publishers (estimate)

Freshly launched or newly on-topic sites clearing the ICP for the first time — names not in any prior export.

Removed

~1,300 dead / parked (estimate)

Domains now expired, parked, or abandoned — pulled out of outreach before a rep ever hits a bounce.

Changed

~2,100 reclassified (estimate)

Verdict or key signals flipped — e.g. a publisher that added its own store, dropped affiliate links, or changed geo focus.

How to read this: a quarter of movement on a ~41,000-publisher list can touch several thousand rows. Left unrefreshed, that's thousands of missed new partners plus dead-domain outreach that quietly erodes deliverability. The delta turns all of it into a few minutes of CRM sync.
Why refresh at all

Discovery is a snapshot. Coverage is a subscription.

The same full-web pipeline that built your universe re-runs on a cadence you set — monthly, quarterly, or annually — so the database stays a live asset instead of aging into a stale spreadsheet.

0
domains re-scanned each cycle
0
delta types: new, dead, changed
$0+
per quarterly refresh
0
locked ICP, so deltas stay comparable
Baseline
last delivered universe
Re-scan
120M+ domains
Diff
add / remove / change
Delta CSV
only what moved

Reference engagement (a large-scale production run on our own classification platform): a 30M dataset → 1.73M travel-related domains → 1.2M ICP-screened → ~96% precision on a reviewed sample. Refresh figures on this page are estimates shown for illustration.

The deliverable

What a delta file actually contains

Same one-row-per-canonical-domain schema as your master universe, with change-tracking columns added so your CRM can act on each row automatically.

ColumnExample valueWhat it tells your team
change_typeadded / removed / changedHow to route the row: enroll, suppress, or re-review
statusalive / dead / parkedReachability at this cycle — suppress the unreachable
first_seen / last_seen2026-02-14 / 2026-08-12When the domain entered and was last confirmed in the universe
is_icp (prev → new)fit → not-fitVerdict flips, so pivots and disqualifications are explicit
signals_changed+own_store, −affiliate_linksExactly which signals moved and in which direction
confidence (prev → new)0.78 → 0.91Slice re-review by how much certainty shifted
Cadence is a dial: monthly for fast-moving verticals, quarterly for most, annual for stable ones. Pricing starts at $499 per quarterly refresh and scales with universe size — see pricing.
Questions

Publisher database refresh — FAQ

How is a refresh different from just running discovery again?
The pipeline is the same, but the ICP definition is locked and your prior universe is used as a baseline. Instead of a fresh list you receive a diff — added, removed, and changed rows only — so your team reviews what moved rather than re-vetting tens of thousands of unchanged domains.
How do you catch publishers that weren't in the first run?
Each cycle re-scans the full category across all 120M+ classified domains — not just the domains you already have. Sites newly launched or newly classified into your vertical are screened for the first time and arrive tagged added, which is where uncontested new partners come from.
How do you decide a site is dead versus temporarily down?
Reachability is re-checked each cycle and a domain is only flagged dead or parked on persistent signals — expired registration, a parking template, hard 404s, or redirect loops — with the date first observed unreachable recorded so you can set your own suppression threshold.
What cadence should we choose?
Most programs run quarterly. Fast-moving verticals — crypto, consumer tech, gaming — often justify monthly, while stable categories are fine annually. You can change cadence between cycles; the baseline simply carries forward from whichever run came last.
Can the delta sync straight into our CRM?
Yes. The delta keeps the canonical domain as a stable key plus a change_type column, so an upsert rule can enroll added rows, suppress removed ones, and queue changed rows for re-review — without touching unchanged records.
Do we need a full run before we can subscribe to refreshes?
A refresh needs a baseline, which is the delivered universe from a paid full run (or a prior refresh). The free pilot is the fastest way to see the pipeline on your vertical first — it returns your first 20 qualified domains and a full-run projection before you commit to a monitoring cadence.

Stop re-buying the list you already own

Start with a free pilot to see the full pipeline on your vertical, then keep the universe alive with scheduled deltas. First 20 qualified publishers and a full-run projection, free.

Request a Free Pilot