01 · Expect Campaign truth
Supply approved creatives, publishers, placements, markets, flight windows, languages, and destinations.
Ad verification
See how your ads appear across markets.
Capture the page, placement, creative, device, location, and landing path behind every monitored result. Use raw access, recurring records, or a managed verification program.
Each capture documents one defined context at one point in time. It does not establish accredited viewability, invalid traffic, attribution, audience delivery, or compliance.
Start with the workload
Choose the campaign decision you need to support.
Placement checks, market delivery, creative comparison, landing paths, page context, and anomaly review each need a different publisher list, capture profile, and result record.
Campaign delivery observation
Confirm the campaign appeared in the approved placement window.
Observe agreed publisher pages and placements with source URL, capture time, slot context, rendered evidence, and collection state.
- Define the publisher, page, placement, market, and flight-time matrix.
- Keep observed, not observed, page unavailable, and collection failed separate.
- Preserve the screenshot or source artifact behind every comparison.
Verification brief
Start with the campaign plan your team already trusts.
Bring the approved creatives, publisher and placement list, target markets, flight windows, devices, destinations, and interaction limits. Those inputs become the baseline for every comparison.
02 · Configure Capture profiles
Define location, browser, viewport, cookies, session behavior, cadence, and time windows.
03 · Observe Public page state
Capture the rendered source, slot, creative, context, configured destination, and collection state.
04 · Compare Reviewable evidence
Apply agreed comparisons when scoped and retain the artifact behind every result.
Verification record
Give media teams a result they can inspect and route.
Each row ties the campaign reference to the requested profile, observed placement and creative, landing path, capture time, artifact, and a clear result state.
Documented products keep their published response schema. Scheduled and managed programs can add the agreed comparison fields, artifacts, history, and review states shown here.
01
Record identity
observation_id, campaign_ref, verification profile, source reference, and schema version.
02
Anforderungskontext
Requested country, city, state or ASN when supported; device, viewport, language, cookies, and session policy.
03
Source & placement
Source and resolved URL, publisher domain, page title, slot locator, dimensions, page position, and iframe context when exposed.
04
Creative observation
Advertiser or creative reference when exposed, visible text, CTA, asset reference or hash, dimensions, and artifact link.
05
Landing path
Displayed URL, configured href, separately scoped redirect hops, resolved host, and path state.
06
Comparison & route
Baseline version, creative, placement, destination, and context states, plus the reason and review queue.
07
Capture history
Observed and retrieval times, first and last seen, collection state, artifact references, and quality flags.
Landing-path evidence
Keep the displayed promise separate from the configured path.
Preserve what the ad shows, what its link contains, and where an approved test resolves. The method must make unintended clicks, installs, purchases, forms, and conversions explicit exclusions.
No active ad interaction by default. Extracted links and separately approved navigation tests are different operations with different side effects.
Illustrative destination trace reviewed path
01
Displayed destination brand.example/work
observed
02
Configured link tracking.example/click?id=042
extracted
03
Resolved landing host brand.example/work?campaign=de042
reviewed
redirect_hops 2
final_host brand.example
conversion_action not performed
Evidence states
“Not observed” is a state—not a verdict.
One missing ad can reflect rotation, timing, eligibility, page behavior, source availability, or a collection problem. Preserve the distinction before escalating.
Ad verification quality measures
Profile and source coverage Expected capture completion Artifact availability Required-field availability Observation age and continuity Schema and delivery conformance
Illustrative repeated-capture matrix 12 attempts
Profile
08:00
12:00
16:00
Staat
DE · desktop
observed
observed
different
review
DE · mobile
not seen
observed
not seen
repeat
FR · mobile
failed
observed
observed
observed
Observed with difference Not observed Collection failed
Responsible verification
Set the interaction and decision boundary before launch.
Approve the public sources, request volume, browser behavior, retained artifacts, and review owner before a verification run begins.
A capture is not accredited measurement. A rendered screenshot or in-viewport observation does not establish human viewability, attention, audibility, invalid traffic, attribution, brand suitability, or legal compliance.
Excluded by default
Ad clicks, form submissions, purchases, installs, conversion simulation, audience impersonation, private or login-gated sources, and independent fraud or compliance determinations.
01 Approve sources
Public accessibility does not make every source, field, or use appropriate. Eligibility is reviewed before collection.
02 Control traffic
Define request volume, retries, session behavior, capture windows, and prohibited interactions.
03 Preserve context
Keep source, requested profile, observed state, capture time, and artifact together.
04 Govern artifacts
Agree screenshot, HTML, redirect, cookie, access, retention, destination, and deletion rules.
05 Own policy
Your team defines campaign truth, suitability rules, investigation, escalation, media action, and lawful use.
06 State limits
Report monitored results and exceptions without claiming universal auction or audience coverage.
Operating model
Choose how the verification work reaches your team.
Run your own collectors, use maintained browser access, receive recurring placement records, or hand off the monitored program. Campaign policy and media decisions remain with your team.
Maximum collection control
Run your verification stack on WSA proxy infrastructure.
WSA operates the documented proxy service and available routing or session controls. Your team runs browser automation, evidence capture, extraction, scheduling, comparisons, and downstream review.
VerantwortungOwner
Verification brief, approved sources & interaction policyIhr Team von Experten
Proxy access, routing & documented network serviceWSA
Browser automation, screenshots & evidence extractionIhr Team von Experten
Scheduling, quality, source-change maintenance & deliveryIhr Team von Experten
Storage, rules, escalation & campaign decisionsIhr Team von Experten
Best for verification teams with their own browser, detection, evidence, and review stack.
Discuss proxy infrastructureEvaluation process
Test one campaign across the hard cases first.
Include the expected placement, a different creative, a missing ad, an unavailable page, a hard-to-render slot, and a destination change before expanding the publisher and market matrix.
01
01 · Define
Approve the brief
Confirm campaign truth, intended use, sources, contexts, interaction policy, cadence, artifacts, and destination.
02
02 · Sample
Inspect real states
Capture representative publishers, placements, profiles, creative differences, missing states, and destination cases.
03
03 · Specify
Agree result rules
Set fields, states, comparisons, retries, artifact retention, acceptance measures, and ownership.
04
04 · Operate
Launch the matrix
Monitor source behavior and field quality, deliver placement records or exceptions, and retain review checkpoints.
Evaluation questions
What buyers should confirm before launch.
Capture scope, request context, evidence, side effects, ownership, and interpretation—answered without hiding the limits.
What can WebScrapingAPI observe for ad verification?
WSA can observe approved public pages under defined capture profiles and deliver source-linked evidence about creative, placement, page context, request context, screenshots or rendered HTML, and configured destinations when exposed and in scope. Availability depends on the source and tested method.
Which locations and devices are supported?
Location, browser, viewport, language, cookie, and session controls depend on the selected product, plan, geography, network, source, and page behavior. Only profiles confirmed in documentation or tested during the pilot enter the production brief.
Can WSA prove that an ad was viewable to a human?
No. A screenshot or an ad observed inside a captured viewport documents a browser state at a particular time. It does not prove an accredited viewable impression, human attention, audibility, or exposure duration.
Does WSA detect ad fraud or invalid traffic?
WSA can collect agreed signals and surface rules-based anomalies with their evidence. It does not issue an accredited invalid-traffic or fraud verdict. Those determinations remain with the customer or its qualified verification provider.
Can WSA determine brand safety or regulatory compliance?
WSA can preserve page context and map customer-supplied rules when contracted. It does not independently certify brand suitability, regulatory compliance, or legality.
Can screenshots and rendered HTML be retained?
Supported browser products can return screenshot and rendered-page outputs. For scheduled and managed programs, artifact type, format, destination, access, retention, and deletion are defined in the data contract.
Can landing pages and redirect chains be checked?
Configured links and resolved destinations can be observed when exposed. Active navigation and redirect testing require a separately approved method. Ad clicks, forms, installs, purchases, and conversion events are not part of the standard scope.
What does “not observed” mean?
It means the expected ad was not found in that capture. It does not by itself prove delivery failure. Page availability, collection failure, rotation, timing, capture context, and scope must remain distinct before interpretation.
Can verification traffic create impressions?
Loading a publisher page may trigger ad-serving or analytics events. The verification brief must define traffic levels, retries, sessions, and prohibited interactions. Active ad clicks or conversion simulation are excluded by default.
Who maintains collection when a page changes?
Proxy customers maintain their collectors and evidence parsing. API customers maintain their parsing and capture workflow while WSA maintains the documented API layer. WSA maintains the contracted connectors and extraction it operates for scheduled or managed delivery.
Request a representative verification sample
See one campaign through the full review path.
Bring a campaign reference, publisher pages, target markets and devices, approved creatives, expected destinations, and review rules. We will map the capture matrix, placement record, exception states, and operating ownership.