How campaign assurance works
What AdsWerk checks, how approvals work, and why unverified evidence stays unverified.
Start with an explicit agreement
A campaign approval records the destination, required query keys, visible offer text, conversion selector, tracking IDs, consent condition, and desktop/mobile viewports. These requirements are versioned. A changed page cannot overwrite its own approval.
Read observations in context
HTTP checks follow up to eight redirects. Required parameter values are compared against the original submitted URL at every observed HTTP hop and at the final browser address. Rendered checks inspect fresh desktop and mobile sessions. Only the selected requirements are covered.
Three results, with meaning
Verified means the listed checks passed at the observation time. Needs attention means at least one approved requirement failed. Unverified means a needed observation was unavailable, blocked, incomplete, or uncertain. A failing requirement can coexist with incomplete coverage; inspect each check.
Confirm before opening an incident
A failure needs another matching failed check set against the same approved version, at least 90 seconds later and within one hour. Cron runs every five minutes, so actual confirmation depends on queue capacity. An incident recovers only after a passing rendered check against that approval.
Respect the free service budget
Free workspaces have two campaigns, a daily schedule, and up to 60 monthly browser reservations. The service also reserves at most 16 browser sessions a day globally, spaced at least 25 seconds apart. Capacity may defer rendered checks. Scheduling and change windows are best-effort; the latest observation time is always shown.
Know the boundary
Forms and checkout are never submitted. Tag presence does not prove conversion event delivery, consent compliance, attribution, or revenue. Third-party challenges are unverified results, not proof that a customer sees a broken page. Historical results cannot guarantee the page is still healthy.