How to check a mobile campaign CTA before launch
Check mobile CTA visibility, size, placement, and obstruction against an approved campaign baseline.
Make the promise measurable
Choose a stable CSS selector for the primary conversion element. Approve its minimum width and height, the viewport to inspect, and whether the entire element must appear above the fold. A rule should describe the campaign promise; a screenshot alone does not define it.
Check the actual viewport
AdsWerk observes fresh desktop sessions at 1365 × 900 CSS pixels and mobile sessions at 390 × 844. Mobile rules apply only to the selected mobile viewport. These are reproducible test sizes, not coverage of every device, browser, font configuration, or logged-in experience.
Look for what covers the button
Layout rules sample five points on the element to detect an overlay covering those points. An element with a bounding box can still be unusable. Keep the conversion-route actionability check alongside geometry rules. Sampled obstruction is limited evidence, not proof that every point or interaction works.
Keep consent and uncertainty visible
Approve a fresh-session or consent-accepted scenario. If a firewall, dependency failure, unresolved consent banner, or unavailable browser prevents the required observation, the check remains Unverified with a reason and next step. Missing evidence must not become an automatic success.
Review, approve, and watch
Create a campaign in your workspace, set its destination and conversion selector, then add layout requirements in the approval form. Saving revised requirements creates a new baseline version. Daily observations compare against that version, and repeated matching failures can open an incident.