Verified, Likely, Needs Check: The Three Labels We Use

what does verified mean and what evidence does it require?

Verified means someone at the Desk loaded the primary source directly and transcribed the figure as published, with the load date recorded next to it. That standard applied to every dollar figure, seat count and offer total sourced from a vendor's own pricing page, homepage or FAQ on 2026-08-05 — AdSpy's stated $149-a-month rate, Foreplay's $59 Basic tier, our own 28,042-offer catalogue count pulled straight from the listing_offers table. No verified figure gets rounded for effect; it prints exactly as the source states it, discount language and all.

Evidence has to be primary. A figure repeated by a review site, a Reddit thread or a competitor's own comparison page doesn't qualify, however often it circulates — only the vendor's own page, or in our case a direct database count, clears the bar. That rule cuts both ways: it verified AdPlexity's yearly Native discount to $208 a month exactly as printed, and it verified that our own creative library holds 4,296 ads against AdSpy's 208.2 million, a gap this page states rather than hides.

what does likely mean and when is it used?

Likely means the source states the number, but the number itself is undated or contradicted elsewhere on the vendor's own site. AdPlexity's homepage claims '100M+ Winning Ads' with no date attached anywhere near it, so that figure carries the likely tag rather than a flat citation. It probably points in the right direction — vendors rarely underclaim their own database — but a reader can't check it against a second timestamp, so neither can we.

The tag also covers straightforward self-contradiction. Minea's own pricing page states 'more than 10 million ads' while its homepage counter reads '80M+ active ads' and '120k+ daily ad & shop updates' — two pages on the same domain, two different orders of magnitude. We report both numbers and flag the disagreement rather than pick whichever one supports the sentence we happen to be writing.

what does needs check mean and what happens to those claims?

Needs check means the page would not load, the answer wasn't in the served HTML, or two live prices disagreed with no way to tell which one a subscriber actually pays. That's a fetch failure or a rendering gap, not an editorial guess — PowerAdSpy's pricing, features and FAQ pages all timed out on repeated attempts on 2026-08-05, so nothing from PowerAdSpy's own site appears as a stated fact anywhere on this domain.

A needs-check claim still gets published, but only inside a safe range and only with the gap named in the same sentence. Anstrex's Push Solo plan is one example: the product page shows $89.99 per month per user in its main pricing block and $69.99 in a separate promotional block, and until someone confirms which price actually renders at checkout, we print both and say so rather than pick the lower number because it reads better.

which competitor figures currently sit at needs check?

Five competitor figures currently carry the needs-check tag, and all five share the same root cause — the page that should confirm them didn't load, or didn't load completely, on the date we checked.

That list will change. A figure moves off it the moment a Desk researcher reloads the page and gets a clean answer, and a figure that stays unreadable for months tells a reader something about the vendor's own site discipline that a stated price never would.

why does a needs-check figure never appear in a headline?

A needs-check figure never leads a paragraph because a headline reads as settled, and none of these five are settled. Put a number in the first sentence of a comparison and most readers carry it out of the page as fact, caveat or no caveat — so the discipline has to happen before publication, not in a footnote after it.

There's a stronger reason underneath that one. A vendor's pricing, feature and FAQ pages failing to load isn't a research inconvenience to route around quietly — it's a data point in its own right about the infrastructure a subscriber would be trusting with a monthly card charge. PowerAdSpy's pricing page, feature page and FAQ page were all unreachable on 2026-08-05 across three separate fetch attempts; BigSpy's own dedicated pricing URL timed out the same day; PiPiADS' pricing URL refuses to render at all without JavaScript enabled. None of that proves the tools themselves are unreliable. It does mean a reader comparing uptime-sensitive tools should weigh 'the pricing page didn't load' alongside whatever number eventually gets confirmed, not treat it as noise this page filtered out.

how are dates recorded against each claim?

Every fact pack carries one check date printed at its head, and every claim pulled from that pack inherits it unless the source itself prints a different date next to the number. The competitor figures on this site are dated 2026-08-05 because that's when a Desk researcher loaded AdSpy, AdPlexity, Anstrex, BigSpy, Minea, Dropispy, Foreplay, AdHeart, PiPiADS and Atria's own pages; our catalogue counts — 28,042 offers, 15,582 with a numeric CPA amount, 1,544 written pages — carry the same date because they came from a direct count against our own tables that day.

Most vendors don't date their own numbers at all, which is exactly what pushes a figure into the likely tier instead of verified. AdSpy's '208,180,000+ Ads' counter and AdPlexity's '100M+ Winning Ads' both sit on public homepages with no timestamp visible anywhere near them, so a reader has no way to know if they're looking at a number from last week or three years ago. We can only date our own visit, not theirs.

who re-checks and how often?

The Desk rechecks a figure the next time that competitor's fact pack comes up for a full pass, and a needs-check item gets priority in that pass over a figure already confirmed. We don't have a fixed re-check interval to publish here — stating one would be exactly the kind of invented precision this page argues against — so the honest answer is irregular, with the unresolved items going first.

We hold ourselves to the same standard we apply to competitors. Of our own 28,042 offers, only 274 were re-confirmed by a scrape in the last 30 days as of this check, which is why 'updated daily' never appears as a claim about our own catalogue. A reference page that won't let a competitor claim daily freshness without proof shouldn't claim it for itself either.

how should a reader challenge a figure they think is wrong?

Write to contact@nutra.international with the page URL, the figure in question and, if you have one, a link or screenshot of what you're seeing instead. That's the fastest path to a correction — a specific claim tied to a specific source beats a general 'this looks wrong,' because it lets a researcher re-load the exact page instead of guessing which of a dozen numbers on it you mean.

A challenge that turns up a live, dated source outranks whatever this page currently states, full stop. If a reader can show AdPlexity has posted a Social plan price, or that PowerAdSpy's site is back up with a stated feature list, that figure moves from needs-check to verified on the next pass — not as a favor, but because that's the whole point of tagging it needs-check instead of guessing in the first place.

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.

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 external context, readers should compare advertising and research decisions against authoritative primary references such as Meta Ad Library, Google helpful content guidance, and Google SEO link best practices. Daily Intel adds the proprietary direct-response layer: blackhat, greyhat, and whitehat campaign pattern comparison across VSL-heavy niches and 14+ language markets.

For deeper evaluation, continue through How the Offer Catalogue Is Built, Field by Field, What Daily Intel Service Is, In Plain Terms, 4,296 Ads and 3,979 VSLs: The Creative Side, Measured, Every Competitor Price on This Site Was Read From the Vendor's Own Page, Best ad spy tools for direct response affiliates, and Best $50/month affiliate tool stack. These related Daily Intel pages connect this topic to the relevant methodology, pricing, trust context, comparison path, or niche workflow.