49 of 51 records source-backed

How aifilliate verifies affiliate-program data.

The database is useful only when a creator can trace a number back to the vendor, see when it was checked, and distinguish a published fact from an unknown. This page defines that contract.

01

Source before summary

Record terms from the vendor’s own affiliate page, help center, agreement, or hosted program portal whenever available.

02

Unknown beats invented

When a public source omits a cookie, network, threshold, or rate, the field stays null and the site says “Not stated.”

03

Payment buys no facts

Affiliate links and sponsorship can fund the site. They cannot buy verification, a better rate, removal of a documented limitation, or editorial rank.

Evidence hierarchy

Which sources count

P0

Vendor agreement, official help center, or first-party program page

Preferred authority for commission structure, cookie window, payout threshold, restrictions, and program status.

P1

Vendor-controlled portal on a partner platform

Examples include a branded PartnerStack, Impact, Rewardful, Dub, FirstPromoter, or similar application page.

P2

Vendor announcement or staff statement

Useful for discovery and change detection, but weaker than the operative terms or application page.

P3

Third-party list, review, forum, or social post

Discovery signal only. It does not support a verified rate unless a first-party source confirms it.

Record states

What “source-backed” means

Source-backed

The cited page was accessible when checked and supported the material terms recorded on the aifilliate page.

Awaiting verification

A program or referral path appears to exist, but the public source did not support enough fields to mark the record as verified.

Not stated

The source does not publish that field. It is not automatically zero, unlimited, lifetime, or whatever would make a prettier card.

Checked date

The date a human or controlled workflow reviewed the cited source. It is not necessarily the date the vendor last changed its terms.

Operating workflow

From discovery to published record

  1. 1

    Discover the program

    Find candidates through vendor sites, partner marketplaces, hosted portals, support pages, creator recommendations, or change monitoring.

  2. 2

    Resolve the exact vendor and program

    Confirm the tool, canonical website, program type, and current application route. Referral programs and affiliate programs are not silently treated as identical.

  3. 3

    Extract only supported fields

    Record commission text verbatim enough to preserve meaning, normalize the type, and capture cookie, threshold, network, source URL, and checked date.

  4. 4

    Quality-check conflicts and nulls

    Compare first-party pages, identify contradictions, and leave unsupported fields unknown. A stale third-party list does not overrule a current vendor agreement.

  5. 5

    Publish one canonical record

    Expose the facts, source, date, limitations, category relationships, and machine-readable representation without generating thin permutations.

  6. 6

    Monitor and correct

    Recheck high-value and volatile records, accept evidence-backed corrections, and preserve the distinction between editorial facts and commercial links.

Commercial firewall

How monetization is kept separate from verification

  • An owner affiliate URL may create a “Try” button, but it does not replace the vendor source or official application page.
  • Affiliate links use sponsored and nofollow relationship attributes.
  • Sponsored placements must be labeled and cannot alter source-backed fields, verification status, methodology, or correction handling.
  • Directory inclusion is based on program relevance and evidence, not payment.
  • Rankings and benchmarks state their method and limitations rather than quietly arranging results by payout.
Freshness and corrections

Terms change. The interface should admit that.

Each record exposes a checked date and cited source. High-value records should be rechecked more frequently than obscure, stable programs. A broken source, contradictory term, or vendor closure moves the record into review instead of being silently patched with an unsupported number.

The current dataset’s latest checked date is 2026-07-03. Use the vendor agreement available inside your approved affiliate account as the final authority.

Submit a correction →