Skip to main content

Trust & methodology

What the data can prove—and what it cannot.

AdGlobal keeps public creative activity separate from customer-private performance and business results. Every insight should preserve its source, time and confidence.

Public signal

Source timestamps, observed longevity, related variants and market reuse. These signals do not reveal ROAS or profitability.

Account performance

Spend, delivery, clicks and platform-attributed conversions only after customer authorization.

Business outcome

Orders, revenue, subscriptions or margin only from a connected first-party system and stated attribution window.

Current demo

The public product-validation demo uses synthetic fixtures modeled on fields commonly available in advertising transparency and creative libraries. It is not a live scraper, does not represent real advertiser results and is labeled throughout the interface.

Source controls

Before a source is enabled, the Source Registry records its access method, rights status, terms URL and review date, media policy, rate limits, retention and owner. Official APIs, authorized accounts and licensed providers are preferred. AdGlobal will not make bypassing login, CAPTCHA or access controls a core dependency.

Customer-authorized pilot evidence

The Private Beta import path accepts only a signed-reference manifest, text metadata and source links. Imported records are private to one Workspace, cannot be cited by another tenant and carry an explicit retention date. The path remains disabled until its Source Registry policy has an approved reviewer and review date; full media is not rehosted by this importer.

AI analysis

OCR, transcription and structured AI analysis may identify format, Hook, pain point, selling point, evidence, Offer and CTA. Inferred fields show confidence and remain correctable. Facts, inference and recommendations are kept distinct.

Corrections and removal

Advertisers and rights holders can request correction or removal. Requests are verified, logged and propagated to derived views where appropriate.

See something that should be corrected or removed?

Use the structured request path so the source and derived records can be tracked.

Submit request