TAG-Certified Ad Fraud and Brand Safety

Where this market publishes its structure

• TAG Registry (tagtoday.net/registry; registry-search public endpoint hubgloo.opxar.com) machine-readable, 410 companies, 168 with a seal; names only, no domain or TAG-ID in the record
• TAG Platinum Status members (tagtoday.net/certifications/platinum-status) machine-readable, names only, a subset of the registry; context
• tagtoday.net sitemap.xml machine-readable, program and news pages only; no company pages (compliant-company URLs 301 to /registry)
• TAG certified-against-fraud / malware / IQG compliant-company lists not machine-readable: retired: each URL 301s to /registry (read there)
• TAG Registry single-hit records not machine-readable: a query matching one company returns the record without its id or, for seal-only companies, its name; 321 such pages, none added a new named company
• TAG member portal not machine-readable: login (robots.txt disallow /member-portal); not read

Own = declares at least one integration itself; covered = visible only because an aggregator, standards body, regulator or partner contract names it; distribution-only = listed only on cloud marketplaces it sells through, a channel reported beside, never counted as its own declared integrations; undeclared = nothing we can read, so no number; declares_compatibility = providers with a `compatible` shape vote, report only (kin, 2026-10-13): never counted as own, never in depth or position.

Taxonomy how this market maps onto apis.io

Derived 2026-10-23 from the 65 providers in this market we could resolve in the catalog. The percentage is the share of those providers carrying each one; it describes the market, not the tag or industry. Tag groups have no page of their own yet, so they are listed unlinked.

share of resolved cohort carrying it; tags >=0.20 & >=3 members (max 12, junk dropped), tag_groups >=0.20 (cooccurrence, non-cross-cutting; max 8), industries >=0.20 (max 6), areas >=0.10 (max 6; areas are keyword-matched and sparse), capabilities L1 >=0.20 (max 8); derive-market-taxonomy.py

What apps actually use from application blueprints

Apps in 39 application categories integrate providers in this market. 9 of the 65 cohort providers appear in an app. The providers below are used by apps but sit outside the cohort. They are listed beside it, not ranked in it.

Derived 2026-11-03: blueprint stack rows (declared/observed) whose capability id falls under this market; providers outside the cohort integrated by apps in >= 3 app categories, max 10.

Leaders by position (provisional)

Provisional: grouped by position, depth compared within a position only. Distribution (cloud marketplaces) and iPaaS bridges are counted beside position, never inside it. Unknown-builder listings are left out of position shares and counted here.

gravity 2 · other companies invest to build on it

builds-on 4 · publishes apps on other platforms' stores

covered 8 · reached mainly through aggregators

standard 37 · listed by a voluntary standard's own directory

mixed 8 · no single mode dominates

distribution 2 · only sells through cloud marketplaces

undeclared 4 · declares nothing we can read: no number

Workflows

No in-market workflows yet; bridges: 2 (2 not yet mapped to a capability). In-market workflows only: a step on the market provider's side maps to this market's business capabilities (BC-400.60, BC-400.50), and the partner is not a generic export/notify app. Other workflows are counted as bridges (including any whose steps do not resolve to a capability yet). Methodology.