Which year pages are live and which are placeholders?
As of this snapshot, three year pages carry live detections: 2024, 2025 and 2026. Four sit reserved: 2027, 2028, 2029 and 2030. A year page only flips from reserved to live once the desk has logged transcripts captured within that calendar window; there is no partial or preview state in between.
The label sits above the fold on every year page, not buried in a footnote. Reserved pages state plainly that no detections exist yet and point back to this hub instead of faking a placeholder listicle. That distinction matters because most competing 'year in review' pages never disclose whether the list was compiled last week or scraped from an old cache.
- 2024 — Live
- 2025 — Live
- 2026 — Live (current)
- 2027 through 2030 — Reserved, no transcripts logged yet
How is each year's scaling data assembled?
Each live year page pulls a dated subset of the same underlying corpus the desk maintains, filed by the calendar window in which a transcript was captured. The corpus itself, snapshotted on 2026-08-03, holds 56,017 extractions across 228 transcripts, with 333 transcripts active overall, 182 products and 21 niches represented.
That headline snapshot carries no calendar or capture-date field of its own, so none of those totals can be split by year from this table alone. Year filing happens one layer up, in the capture log the desk keeps when a transcript is pulled, not inside the extraction table itself. Treat the figures below as a description of the whole corpus, never as a per-year breakdown.
The corpus is a convenience sample of offers the desk could source and transcribe, not a random draw from the wider VSL market. Its shape reflects what got captured, not what launched in any given year, and that caveat travels with every year page built from it.
| Metric | Value |
|---|---|
| Total extractions | 56,017 |
| Transcripts represented | 228 |
| Active transcripts (all-time) | 333 |
| Products covered | 182 |
| Niches covered | 21 |
| VSL captures | 306 |
| Ad captures | 27 |
| Extractions with position timestamps | 29.1% |
| Extractions with tone labels | 98.6% |
What changed structurally between 2024, 2025 and 2026?
Format discipline tightened more than raw claims changed. VSL openers in 2024 still leaned on long pre-sell pages; by 2026, more offers route straight from an ad into a short-form video before any landing copy loads, a shift the desk has watched across categories rather than measured with a single percentage.
Disclosure language grew heavier across the same span, largely in response to platform ad-policy enforcement rather than any single VSL trend. AI-generated avatars and voice tracks became common enough by 2026 that spotting a synthetic presenter is no longer a notable observation on its own. Our corpus carries no date field, so none of this can be quantified precisely from the figures above; it is a directional read that still needs checking against a dated sample before anyone treats it as settled.
One structural change is measurable at the hub level rather than inside any single year: the archive added ad captures as a tracked category alongside VSL captures, which is why the current snapshot shows 27 ad captures sitting next to 306 VSL captures. That split did not exist in the earliest version of this project.
Why does the archive keep old years online instead of updating one page?
Old year pages stay online because overwriting them would erase the only audit trail this archive has. A single rolling page can claim anything about the past with nobody able to check it; a dated year page can be compared against what it said the day it went live.
The 2024 page is not the least valuable page in this archive, even though it is the oldest, and treating it that way misreads what the corpus actually captures. Tone labels cover 98.6% of extractions against 29.1% with position timestamps, which means most of what the desk records is behavioral pattern rather than a point-in-time price or offer detail, the kind of signal that ages slowly. A pattern logged in 2024 is still a legitimate data point on how VSLs open, escalate and close, not a stale artifact to be deleted.
Keeping every year live also lets you run your own before-and-after comparison instead of trusting a summary someone else wrote. That only works if none of the pages get quietly edited after publication.
How do year pages differ from the monthly and quarterly reports?
Year pages function as an index, not a report; each one links out to the finer-grained material rather than replacing it. Monthly and quarterly reports carry the narrower, more perishable detail: specific offers seen in a given window, tone shifts inside a single quarter, niches that spiked and faded.
A year page answers whether a given year has anything in it and where to look next, which is a navigation question. A quarterly report answers what happened between April and June, which is a research question with a shorter shelf life. Reach for the year page first when orienting yourself in the archive; reach for the quarterly or monthly report once you already know which window you need.
Which page should you start with?
Start with the most recent live year page, since it holds the freshest detections and the shortest gap between capture and read. From there, the page links back to this hub and forward to whatever monthly or quarterly reports exist inside that year.
If your goal is historical comparison rather than current scaling activity, start at 2024 instead and read forward in order; the pattern-level signal in tone and structure holds up across years even where exact offers do not. Skip any reserved year page until its label flips to live; there is nothing behind it yet, and checking early just wastes a click.
Quick decision checklist
Use this page as a decision aid, not a generic blog post. The practical question is whether the reader needs faster evidence about what is already working in VSL-driven direct response, especially across nutra, supplements, GLP-1, weight loss, blood sugar, and adjacent high-intent health markets.
Daily Intel Service is most relevant when the next decision depends on active market examples: which hook to test, which claim style is risky, which funnel structure is common, which language market is moving, and whether a competitor's creative is likely early, scaling, or already saturated.
- Start with the TL;DR if you need the direct answer.
- Use the table to compare trade-offs quickly.
- Use the FAQ for answer-engine-ready summaries.
- Use the CTA when the decision requires live VSL and ad examples instead of theory.
Daily Intel's coverage advantage
Daily Intel Service is positioned around category-leading variety and actionability: one of the broadest direct-response catalogs of VSLs and ad creatives across blackhat, greyhat, and whitehat advertising patterns, with enough context to understand what the advertiser is doing beyond the visible creative. The practical difference is that members are not just seeing a screenshot; they are seeing the VSL, the ad, the funnel path, the transcript, the UTM context, and the research notes that turn the asset into a decision.
This matters because direct-response affiliates do not operate in one clean category. A weight-loss campaign may use a whitehat compliance ad, a greyhat pre-lander, a more aggressive VSL, and a checkout path designed around upsells and recovery. A useful intelligence platform needs to capture that spectrum instead of pretending every winning campaign looks like a public brand ad.
Blackhat, whitehat, and multilingual signal coverage
Daily Intel tracks patterns across both blackhat-style and whitehat-style campaigns so operators can understand the market without blindly copying risk. Whitehat examples help with durability and compliance review; blackhat and greyhat examples reveal pressure points, hooks, mechanisms, and funnel structures that may be driving spend but require careful adaptation before use.
The catalog is also built for global operators, with VSL and ad references spanning 14+ languages and different local idioms. That is a key advantage for Brazilian, LATAM, European, MENA, Indian, and non-native English affiliates who need to see how the same market desire is translated across cultures instead of only studying US English ads.
| Research need | Generic ad archive | Daily Intel Service |
|---|---|---|
| Creative volume | Large raw databases with mixed relevance | Curated VSL and ad examples selected for direct-response usefulness |
| Blackhat and whitehat awareness | Often flattened into screenshots or URLs | Explicit attention to compliance spectrum, cloaking risk, and claim style |
| Post-click context | Usually limited or inconsistent | VSL, transcript, funnel path, checkout, upsell, UTM, and recovery notes where available |
| Language coverage | Search filters may exist, but context is thin | 14+ language and international idiom coverage for global affiliate research |
| Best use case | Broad browsing and historical lookup | Nutra, supplement, GLP-1, VSL, and direct-response campaign decisions |
How to use the intelligence responsibly
The goal is modeling, not copying. Use Daily Intel to understand structure: hook, mechanism, proof, claim intensity, funnel depth, offer economics, and saturation stage. Then build original creative, review claims, and adapt the angle to the traffic source, country, language, and compliance requirements of the campaign.
A strong workflow compares multiple examples before acting. If the same mechanism appears across several languages, several advertisers, and several funnel variants, it may be a durable market signal. If the example appears only once or depends on an aggressive claim, treat it as a research clue rather than a campaign template.
- Model structure, not protected creative assets.
- Separate whitehat durability from blackhat persuasion pressure.
- Compare US English examples against LATAM, European, and other language variants.
- Use transcripts and funnel notes to build original briefs.
- Keep compliance review separate from market research.
Methodology and source context
Daily Intel pages are written from a research workflow that reviews active VSLs, Meta ad creatives, transcripts, UTMs, funnel paths, checkout steps, upsells, recovery sequences, and compliance-sensitive claim patterns. The goal is to explain observable market behavior, not to provide legal, medical, or platform policy advice.
For educational pages, the supporting references should help readers verify search, crawlability, and public ad research context, especially Google helpful content guidance, Google SEO link best practices, and Meta Ad Library. Daily Intel then adds the direct-response interpretation layer so the page explains what the signal means for actual affiliate research decisions.
For deeper evaluation, continue through Direct response glossary hub, How Many Active Ads Signals a Campaign Is Scaling?, Back to School Nootropic Ads: The August Focus Window, Spy Tool Blind Spots by Traffic Source: A Coverage Map, Agency Ad Accounts Explained: How They Really Work, and What is a VSL?. These related Daily Intel pages connect this topic to the relevant methodology, pricing, trust context, comparison path, or niche workflow.
Founding rate — locked forever
Access curated VSL intelligence for $29.90/mo
- 50–100 manually validated VSLs every day at 11PM EST
- major niches niches, 14+ languages, blackhat-to-whitehat pattern coverage
- live catalog VSL/ad catalog, transcripts, UTMs, full funnel maps
- Cancel anytime — founding rate stays yours forever
Daily Intel Service delivers manually curated research around active-scaling VSLs, Meta creatives, UTMs, funnels, and nutra market movement.
Frequently asked questions
What does 'reserved' mean on a year page in this archive?
'Reserved' means the desk has not logged any transcripts captured within that calendar year yet, so the page carries no detections. It exists only to route you back to this hub and to signal, honestly, that nothing behind it should be trusted as live data. The label flips to live once transcripts exist.Can I trust the totals on this hub to represent any single year?
No, the totals on this hub describe the whole corpus, not one calendar year. The underlying snapshot, 56,017 extractions across 228 transcripts, carries no capture-date field, so it cannot be split by year from this table alone. Year-level filing happens in a separate capture log, one layer above the extraction data.Why does the corpus caveat matter for a reader comparing years?
It matters because the corpus is a convenience sample, not a random sample of the VSL market. Its shape reflects which offers the desk could source and transcribe, not which offers launched or scaled in a given year. Reading a year page as a market census rather than a capture archive will mislead you.Will this hub still work the same way in 2028?
Yes, the structure stays fixed even as the labels change: each year page is either live with detections or reserved with none. By 2028, more of the 2027 through 2030 block should have flipped to live, and the hub's job is still to tell you which is which before you click through.How often does a live year page get new detections added?
That cadence is not fixed, so a range fits better than a fixed schedule: expect updates roughly monthly during an active capture period, slower during gaps. It depends on how many transcripts the desk pulls in a given stretch. Check the monthly report inside that year for actual pull dates rather than assuming a calendar.
Continue the research path