How Do Popunder Ads Work? Mechanics, Targeting and Measurement

Official standards explain window creation, blocking and experience boundaries

The WHATWG HTML Living Standard defines window.open as a mechanism for navigating an existing browsing context or opening an auxiliary one. Its popup feature encourages a minimal browser interface, and its noopener and noreferrer features affect the opener relationship and referrer handling. The standard does not define an advertising format named popunder or guarantee that a new context will sit behind the active window. Google Chrome Help says Chrome blocks popups from automatically appearing by default and lets users change permissions; it also notes that not every popup is advertising or spam. The Coalition for Better Ads identifies popup experiences as falling below its consumer-acceptability threshold for desktop and mobile web. Its popup definition concerns content-blocking overlays, so it should inform experience risk rather than serve as an exact technical definition of a popunder. These boundaries support browser-specific testing and cautious terminology, not claims of universal delivery or compliance.

• WHATWG HTML window.open - normative auxiliary browsing-context, popup-feature and opener behavior
• Google Chrome popup controls - current Chrome default blocking and user permission behavior
• Coalition for Better Ads Standards - consumer-acceptability boundary for popup experiences, not a popunder implementation specification

Define the claimed format precisely

Record whether the implementation attempts to open a new window, a tab, an in-page overlay or another browsing context. State the trigger and intended focus behavior. Do not group interstitial, popup and popunder experiences solely because they interrupt or accompany a page visit.

Preserve a screen recording and browser details for each test. The commercial label does not control what a browser renders. If the experience cannot be reproduced consistently, describe the observed variants instead of publishing a single mechanical promise.

Trace the window.open request

Document the source page, event, script owner, requested URL, target name and feature string. The HTML standard allows window.open to navigate an existing context or request an auxiliary one. Features can influence whether a minimal popup interface is requested, but the user agent retains control.

Inspect the returned state and failure behavior without attempting to defeat browser protection. A blocked request should leave the source usable and should not enter a retry loop. Keep the implementation version with campaign evidence so a later browser change is not confused with traffic quality.

Do not promise behind-window placement

Treat the word under as a description of the intended experience. The standard does not require a new context to appear behind the current page, and browsers may choose a tab, window, foreground treatment or no opening. Device and user settings can change the result.

Write page explanations in conditional language and show the tested environment. Avoid diagrams that imply deterministic stacking across browsers. When placement order is material to the campaign, measure the actual focus and visibility behavior for each supported environment.

Respect browser popup controls

Chrome states that automatic popups are blocked by default while users can allow them. Other browsers maintain their own controls and can change behavior. Do not market a technique as blocker-proof or encourage implementations designed to conceal or evade user-agent decisions.

Measure blocked, opened and unknown states where reliable instrumentation is permitted. Preserve browser version and settings for controlled tests. A lower opening rate is not a reason to increase triggering attempts or interfere with the user's original navigation.

Require an understandable trigger

Identify the exact user action associated with the request, such as a deliberate click on named content. Avoid ambiguous page-wide triggers, hidden layers or controls that imitate navigation. The user should be able to complete the original task without being forced into an advertising destination.

Test keyboard, touch and assistive-technology paths. Record accidental activations and complaints. A high event rate can reflect a confusing trigger rather than strong interest, so source-page experience belongs in the campaign quality review.

Evaluate consumer experience separately

The Coalition for Better Ads places popup experiences below its acceptability threshold, but its definition focuses on ads that cover content. Use that research as a warning about interruption and annoyance, not as proof that every implementation bearing a popunder label is identical.

Review whether the new context obstructs, steals focus, resists closing, repeats or surprises users after they leave the source. Apply the stricter relevant platform, publisher and advertiser experience requirements. A format can be technically possible and still be unsuitable for the intended audience.

Review the publisher environment

Record site or app, page type, trigger area, device, geography and source identifier. Ask whether the publisher owns the interaction and can explain frequency and user controls. A destination cannot repair a misleading or unauthorized source experience.

Render representative placements rather than relying on a network format name. Keep unknown or blended sources under a smaller ceiling and require exclusion capability. Do not infer endorsement from the publisher or call the inventory premium without direct evidence.

Approve the advertiser destination

Resolve every redirect and inspect the final domain, offer, claims, price, eligibility, disclosures, form and confirmation. The destination must be safe and usable when opened as a tab or window, regardless of whether the source remains visible. Preserve the URL chain and release.

Test closed cookies, consent-limited state, slow connection, mobile layout, back, close and reopening. Stop delivery on broken or materially changed pages. A cheap opening is wasted when the page cannot support the promise or accepted outcome.

Protect opener and navigation security

Review whether the new context needs a relationship with its opener. The HTML standard documents noopener and noreferrer behavior; use current security guidance and the organization's engineering review to choose an implementation. Avoid granting cross-context capability merely for convenience.

Test cross-origin behavior, unexpected navigation and close paths with controlled domains. Do not publish code that weakens browser protections or attempts to manipulate focus. Record unresolved security concerns as launch stops rather than advertising trade-offs.

Set a defensible frequency rule

Define how often a source may attempt the experience within a stated window and what identifier or storage scope implements the rule. Explain consent and browser limitations. One cap cannot be assumed to follow a person across devices or cleared storage.

Review repeat attempts, successful openings, complaints and accepted outcomes. Lower the cap or stop the source when the experience becomes disruptive. Do not treat frequency as a performance lever without also measuring user cost and source retention.

Separate opening from engagement

Keep trigger, request, browser-open state, landing request, usable session, qualified action, accepted outcome and reversal distinct. Some states may not be observable reliably. Document instrumentation and avoid filling missing steps with assumed conversions.

Reconcile provider billing with server and first-party records over the same timezone and period. A new context may load without deliberate attention, so an opening or impression is not evidence that the person noticed, read or wanted the offer.

Investigate accidental and invalid patterns

Inspect timing, focus duration where legitimately measurable, landing continuity, repeated identifiers, source concentration, device behavior and accepted results together. A short or background session can arise from the format itself and does not alone prove automation or fraud.

Use observe, cap, pause, exclude and retest states with documented reasons. Apply the selected provider's current billing and adjustment definitions. Do not publish a fraud rate based on one heuristic or borrow invalid-click guarantees from an unrelated platform.

Map privacy and consent flows

Inventory identifiers, URL parameters, storage, device information, location, source evidence and form data across publisher, network, tracker and advertiser. Record purpose, notice, access, retention, transfer and deletion. Remove data not necessary for the approved campaign.

Test non-consenting and limited-data paths. A separate browsing context does not remove privacy duties, and a fast redirect does not create permission. Escalate market-specific questions rather than claiming that the format is legal everywhere.

Test desktop, mobile and app webviews

Run controlled checks on supported desktop browsers, mobile browsers and in-app webviews where the provider says delivery occurs. Record whether the request is blocked, becomes a tab, opens a window, changes focus or fails. Include orientation, keyboard, close and back behavior.

Treat each environment as a separate cell because implementation and user control differ. Exclude unsupported contexts instead of generalizing from desktop. Preserve versions and settings so a future browser release can trigger a targeted retest.

Build a small source-level pilot

Choose one source class, trigger, browser group, creative destination, geography and maximum loss. Validate measurement with synthetic or authorized actions before meaningful spend. Define stops for blocking anomalies, user complaints, destination failure, policy concerns and accepted cost.

Review source behavior and outcome maturation before adding volume. The pilot determines whether controls and evidence work under the tested setup; it does not prove that popunders as a category outperform display, native, interstitial or direct links.

Compare less disruptive alternatives

Test whether an inline display unit, clearly labeled link, contextual placement, user-initiated interstitial or another permitted format can deliver the same job. Keep offer, destination and accepted outcome comparable. Include production and moderation effort.

Choose the least disruptive route that meets the business and user requirement within evidence. A popunder's nominal price has little value when blockers, accidental openings, complaints or weak attention increase complete cost. Preserve negative results instead of repeating the format under a new name.

Prepare a browser-change retest

Set review triggers for browser releases, popup policy, publisher script, network implementation, destination and consent changes. Keep a minimal controlled test case and the last known behavior. Do not alter production code merely to restore an opening after a browser tightens protection.

Classify the change as expected blocking, defect, policy issue or unsupported behavior through evidence. Update campaign expectations and exclusions before spend resumes. Historical opening rates cannot be reused after implementation conditions change.

Close with a popunder decision record

Record the exact format, trigger, source, implementation, browser results, destination, frequency, user-experience findings, measurement gaps, accepted outcomes and complete cost. State continue, reduce, repair, replace or stop with a named ceiling and owner.

Keep conclusions confined to tested sources and environments. Explicitly state that behind-window placement and delivery are not guaranteed. The final record should make clear which observations came from standards, browser documentation, provider behavior and the advertiser's own pilot.

Audit the publisher trigger implementation

Inspect the rendered source page to identify the exact clickable element, event listener, script domain, loading order and requested destination for each approved placement. Compare desktop pointer, keyboard and mobile touch behavior. Confirm that ordinary scrolling, closing a notice or selecting navigation does not silently become the advertising trigger, and preserve the tested script hash or release identifier with the placement record.

Repeat the audit after publisher template, consent layer or network tag changes because an unchanged campaign name can mask a new interaction. Sample real source identifiers rather than only a demonstration page. If the provider cannot connect a billed opening to an approved trigger implementation, cap or pause that source until the publisher and network can supply reproducible evidence.

Reconcile blocked delivery with experience stops

Create a browser-by-source ledger that separates trigger attempts, blocked requests, opened contexts, landing requests and accepted outcomes without inventing values for unobservable states. Compare controlled browser results with provider billing rules and server evidence. A high attempt count paired with few usable sessions can indicate browser enforcement or implementation friction; it does not justify repeated requests designed to wear down the user's controls.

Set stop rules for unexpected focus theft, repeated prompts, source-page breakage, excessive blocked attempts, complaints and accepted cost before launch. Pause only the affected browser or source cell when the evidence is actionable, then verify that the stop takes effect. Resume after a documented fix and fresh user-experience test, never after a code change whose purpose is merely to restore blocked delivery.

Popunder implementation and campaign matrix

The format advances only when the observed browser behavior, user experience, destination and accepted outcome all remain within a bounded rule.

Retained popunder advertising resources

The original popunder explanations, advertiser links, calls to action and images remain below in their original sequence. They preserve navigation and do not guarantee browser behavior, policy acceptance or results.

How popunder ads work questions