Explore popunder traffic, integration options, browser behavior, fraud prevention and click validation for direct advertisers and publishers.
Explore types & examplesPlaces, stories and a little inspiration for your next escape.
A separate advertiser window opens behind the publisher. Browser rules and frequency limits apply.
The visitor is reading the original website. No advertiser window is open yet.
Popunder advertising opens an advertiser destination in a separate tab or window. Unlike a banner, the creative is the destination page itself. The publisher keeps the original content open, while the browser determines how the new window is displayed and focused.
A visitor interacts with an eligible publisher placement. When browser rules and frequency settings allow it, a separate destination opens. The visitor can then explore the advertiser’s page and decide whether to take action.
Popunder uses a separate advertiser destination rather than a space inside the page. The device, browser and eligible visitor action influence how that destination opens.
A visitor interacts with an eligible publisher page and an advertiser destination opens in a separate window behind it. The original page remains in front; the visitor may discover the offer when switching or closing windows.
Check browser focus behavior and landing-page loading. A background window does not establish that the visitor saw or engaged with the offer.
An eligible interaction can open the advertiser destination in another mobile browser tab. Mobile browsers may bring that tab forward instead of keeping it behind, so the desktop popunder experience cannot be assumed on a phone.
Validate supported devices, tab behavior and the mobile destination before testing. Foreground popup behavior is different from a window opening behind content.
The publisher limits when an eligible interaction can trigger a new destination. This example illustrates a frequency-controlled placement: a repeat page action need not create another window, even when the same visitor continues browsing the website.
Agree the frequency definition and available controls. Browser restrictions, eligibility and demand can still prevent a destination from opening on a permitted opportunity.
A pop-up brings a separate advertiser window in front of the publisher’s page. This foreground behavior differs from a popunder, which aims to keep the original page in front. The comparison explains focus behavior rather than treating the two experiences as identical.
Confirm the intended window behavior and permitted user interaction before integration. Browser restrictions can block the opening or change how focus is handled.
Illustrative examples, not live advertising. Available inventory, creative requirements and delivery behavior are confirmed for your setup.
The visitor interacts with the publisher website.
The configured placement opens a separate tab or window when permitted.
Recorded traffic and conversion tracking help evaluate the source.
Put your landing page at the center of the campaign. Match the page to your offer, location and device audience, then compare source performance against your conversion objective. Popunder can suit offers that need more explanation than a small creative allows.
Plan a popunder campaignAdd a monetization opportunity without reserving a banner slot in your layout. Choose the placement and frequency deliberately, and evaluate revenue together with repeat visits and audience feedback. The experience must fit your website and existing partner policies.
Discuss your websiteReview recorded delivery, spend and attributed conversions by source and device. A new window is not proof of engagement or a completed conversion.
Window opening and focus depend on browser restrictions and user interaction. Frequency settings affect both delivery and audience experience.
A popunder setup connects an approved publisher interaction to a separate advertiser destination. Agree on the activation point, permitted sources, browser coverage and reporting definitions before adding code. Window delivery, traffic validation and conversion attribution are separate parts of the integration.
Place the approved browser tag on reviewed pages and connect it to an eligible visitor interaction. The implementation must respect browser restrictions and the agreed frequency policy. Test the actual browsing experience; adding a script does not guarantee that a separate window opens.
Publishers controlling their page code and interaction design.
An agreed tracking route can connect the eligible interaction with the approved landing page. Keep the visitor's original task usable and document which event the route records. A request to that URL must not automatically become evidence of an intentional advertiser click.
Partners with an approved activation and destination flow.
For an approved feed partner, XML or JSON may supply the destination and agreed metadata to a compatible renderer. The partner still needs permitted browser code to perform the opening. A server response alone cannot open a window on a visitor's device.
Technical partners with an agreed feed and renderer contract.
Follow what happens on the device. The integration, placement and browser all shape the experience your audience receives.
Popunder describes the intended background experience. The browser may open a tab, bring a destination forward or block the request. Do not promise identical focus behavior across devices or attempt to override a visitor's browser preferences.
A visitor can trigger the placement while continuing their original task. That opening is different from choosing an advertiser's offer, seeing its page or completing an action. Name these stages separately in campaign analysis.
Agree how repeat opportunities are limited and what happens when no eligible destination is available. Evaluate landing-page speed and repeat exposure together; more openings can increase interruption without producing more useful advertiser visits.
Agree source eligibility and event definitions before launch. Reconcile source records, browser-side delivery evidence and accepted advertiser outcomes so every reported stage has a clear meaning. Use the agreed review process to resolve discrepancies.
Match the request to the approved publisher, domain and placement. Review declared traffic origins and permitted acquisition methods. Investigate unexplained source changes before combining their results with an established placement's history.
Separate an eligible request, an opening attempt and available arrival evidence. Check event identifiers for duplication. Browser blocking, connectivity errors and provider policy rejections need distinct reasons; none alone establishes fraudulent activity.
Review agreed automation signals, repeated event patterns and inconsistencies between source and destination records. Evaluate signals together: a unique IP address does not prove a human visitor, and a shared IP address does not prove invalid traffic.
Reconcile attributed events with the advertiser's accepted conversion definition. Deduplicate repeated notifications and distinguish pending, rejected and accepted outcomes where available. Agree review evidence and discrepancy handling before using these outcomes to change buying decisions.
Active filters, validation criteria and reporting treatment are agreed for the integration.
Use the source, event history and destination together when reviewing traffic quality.
Assess whether the activation point misleads visitors or interferes with navigation. Unexpected openings and accidental interactions are experience problems even when the underlying page visitor is human. Review problematic placements individually.
Review the final landing page, redirect behavior and offer consistency. Agree how unavailable or changed destinations are paused and rechecked. A campaign approval should not replace monitoring the destination after launch.
Document why an event is excluded: duplication, an integration error, an agreed invalid-traffic finding or a commercial eligibility rule. Align evidence access and review periods; an exclusion does not automatically establish a refund entitlement.
Compare like-for-like events. Use this guide to agree the reporting definitions for your popunder setup before traffic starts.
Judge popunder traffic through the complete sequence: approved source, eligible activation, measurable arrival and accepted outcome. Agree which event is reportable and chargeable rather than treating every opening as a click or sale.
Connect the creative, placement and reporting decisions before traffic starts. These are the practical questions to resolve with your team.
A popunder visitor has not clicked a banner promising a particular product. Your destination needs to establish the offer immediately: what it is, who it is for and what to do next. Put the essential proposition near the top, make the primary action easy to find and check the complete mobile journey before buying traffic.
Begin with a market and device combination your business can serve. Keep the destination consistent while reviewing individual sources; otherwise a changed page and a changed source mix can obscure the reason for a result. Verify that campaign identifiers survive the redirect path and that your conversion system records the intended action once.
For a publisher, the trigger matters as much as the absence of a banner slot. Review when an eligible action can open the destination, how often a visitor may encounter it and how it behaves alongside navigation or other monetization. Test the actual desktop and mobile browsers used by your audience rather than relying on a single development device.
Assess the effect on return visits, completed reading sessions and any important site actions alongside advertising revenue. Adding a new window to a short utility task can produce a different experience from adding one during a long browsing session. Start with a controlled placement and a way to disable it promptly if the observed behavior differs from the agreed setup.
A recorded opening, a landing-page load and a conversion are different stages. Compare the network's delivery definition with the events your own analytics or conversion system can observe. Browser focus, loading failures, consent choices and attribution settings can affect the relationship between the two reports, so an apparent discrepancy needs investigation before a source is judged.
Review acquisition cost against accepted outcomes and the value of the customer or lead. Lower-priced delivery is not automatically better if few visitors can use the destination. When testing frequency, compare similar traffic periods and watch both advertiser outcomes and publisher experience; changing several constraints together makes the tradeoff harder to understand.
Choose a popunder test when the landing page itself can introduce the offer and a separate-window experience is appropriate for the publisher. Choose display when a visible on-page message should earn the click first. The formats create different entry points, so compare completed business outcomes rather than treating each recorded delivery as equivalent.
The main creative is your landing page. Validate loading speed, destination content and tracking before launching.
No. Browser behavior, eligibility, demand and frequency settings determine delivery.
The systems can count different stages. A network delivery event does not necessarily mean the destination was focused, fully loaded or measured by your analytics. Check event definitions, timezones, redirects and tracking conditions before interpreting the difference as traffic quality.
A publisher can discuss a combined setup, but each placement should be evaluated within the whole visitor journey. Introduce changes gradually, agree frequency and triggering rules, and check whether the combined experience affects important site actions or returning visitors.
No. A postback reports an event between systems. An approved feed can provide destination data, but browser-side code still performs the opening and remains subject to browser rules. Delivery and conversion measurement require separate integration checks.
No. Browser settings, unsupported behavior or technical errors can prevent an opening. Investigate delivery failures separately from invalid traffic, and do not infer a human visit or an intentional click merely because an opening was attempted.