NEXUSADTECH

Performance display

Popunder and CPV advertising

A separate landing-page window opened behind the active page, where permitted. Deliver a landing-page visit under explicit traffic-quality rules.

IN PRACTICE

A simple example.

An eligible user action can trigger a partner landing page. Browser policies, consent and frequency limits constrain delivery.

Where it appears
Eligible partner inventory
What to measure
Valid visits · CPV

Traffic placement / Nexus fit

How Nexus
supports this workflow.

XML ad network ↗

What Nexus provides

Feed routing, source controls, quality rules and click / commercial reports for compatible partners.

What you need to connect

A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative.

DEPLOYMENT FITNexus Soft heritage; available as custom deployment scope

Exact format support, enforcement and reporting depend on the connected revenue engine and agreed deployment configuration.

CPVcommon buying model
Frequencycritical control
Web trafficprimary environment

Plain-language definition

What is popunder / cpv advertising?

A popunder opens a destination in a secondary browser context behind the active page. The user typically encounters it after closing or moving away from the original window, which makes source transparency, browser behavior, timing and frequency essential.

WHERE IT APPEARS

Placements

  • Publisher page interaction
  • Direct-link campaign
  • Feed-backed destination
  • Multi-site rotation where explicitly configured
HOW IT IS BOUGHT

Buying models

  • CPV — cost per valid view
  • CPM in some supply contracts
  • Campaign-specific bid or publisher payout
HOW ELIGIBILITY CHANGES

Targeting signals

  • Country and region
  • Browser and operating system
  • Device class
  • Publisher, site and source
  • Time and frequency

Delivery path

From opportunity to measurable outcome.

The exact services differ by format, but every useful implementation keeps eligibility, delivery and evidence connected.

01Publisher interaction
02Eligibility and cap check
03Destination selection
04Secondary window opens
05View and outcome tracking

Measurement

Metrics that explain more than volume.

Use these metrics to evaluate the format. They are not a promise that every Nexus integration supplies every metric: player, publisher, analytics or conversion reporting may be needed.

Valid views

Accepted destination opens

Unique rate

Unique users or devices ÷ views

Frequency

Views per user or device

Post-view outcome

Validated action after exposure

Operator guide

What clients should understand before launch.

01

What the user sees

The original page remains active while a second destination opens behind it. Because the experience is interruption-based, placement consent and predictable behavior matter more than raw delivery volume.

02

How delivery is governed

Publisher identity, browser capability, campaign eligibility, direct-link or feed response, time caps and per-user frequency determine whether an opportunity should open.

03

Quality and fraud controls

Repeated opens, automation, hidden windows, blocked or unsupported browser behavior, misleading sources and excessive frequency can distort a CPV campaign.

04

When it is appropriate

Popunder can support direct-response campaigns with broad reach, but it is not a universal substitute for intent, native or video formats. Brand requirements, browser policy and user experience must be evaluated explicitly.

Frequently asked

Questions about popunder / cpv.

Cost per view charges for an accepted view or opened destination according to the campaign and supply contract. The exact validity rules must be defined.

Build the right delivery path

Connect format, targeting, traffic policy and commercial evidence.

Talk to an AdTech expert ↗