Symptom: Two popups (or Forms) are appearing on the same page at the same time, stacking on top of each other or showing back to back. Or you're trying to decide which popup surface to use: a popup, the Native Browser Prompt, or the iOS Install Prompt.

TL;DR. PushOwl ships three popup surfaces: your popups (the Forms you build in the dashboard), the Native Browser Prompt (the browser's built-in push permission dialog), and the iOS Install Prompt (Add to Home Screen flow for iOS push). They're complementary; if more than one is active and they overlap, you'll see them stack.

Troubleshoot: two popups showing at the same time

1. Do you have two campaigns with overlapping targeting?

If campaign A targets "all visitors on all pages" and campaign B targets "new visitors on the homepage," both fire for a new visitor on the homepage.

To check:

Forms > Campaigns: scan all Active campaigns. Look at each one's Targeting dialog.

Fix: Add a mutually-exclusive rule:

Campaign A: New visitors only.
Campaign B: Returning visitors only.

Or use subscriber list targeting:

Campaign A: visitors NOT on the "newsletter" list.
Campaign B: visitors NOT on the "vip" list.

2. Is your popup conflicting with the Native Browser Prompt?

The Native Browser Prompt (in Forms > Campaigns, Additional options at the bottom) fires the browser's built-in push permission dialog. If both a popup and the Native Prompt are Active, a visitor could see both, back to back.

Fix: Pick one. Either:

Disable the Native Browser Prompt (recommended if your popup already has a Web Push step). Open Forms > Campaigns, scroll to Additional options, Native Browser Prompt, Actions, Pause.
Disable the Web Push step in your popup (recommended if you prefer the bare browser prompt). Open the popup editor, click the Web Push step, Delete.

3. Is the Teaser still visible after the popup opens?

This isn't strictly "two popups," but it's a common observation. By default, the Teaser hides while the full popup is open and reappears after the visitor dismisses it.

If both are visible at the same time, it's likely a CSS conflict in your theme. Open the page in incognito to rule out browser extensions. If it persists, share a screenshot of the storefront with both visible.

What each surface is for

Two extra surfaces live in Forms > Campaigns, under Additional options. They're complementary to popups, not replacements.

Native Browser Prompt

The Native Browser Prompt is the browser's built-in "Site wants to send notifications" dialog. No custom design; pure browser UI.

What it's good for

Lowest-friction web push opt-in. Visitors who'd ignore a popup might tap "Allow" on a single browser prompt.
Stores where popups don't fit (heavy SPA, no theme app extensions).
Backup when your popup is paused.

What it looks like

Browser-specific. Chrome shows it at the top-left. Safari shows it as a sheet. Firefox shows a doorhanger.

Trade-off

Less context: visitors see "Allow notifications?" with no offer or branding. Allow rate is lower than a designed popup.
One-shot: in many browsers, once a visitor blocks the native prompt, it can never be shown again (until they clear site data). A popup gets multiple chances.

How to use it well

Pair the Native Browser Prompt with a popup that hand-holds the visitor toward Allow: explain in the popup what they'll get, ask for the email first, then close the popup and let the Native Prompt fire.

To enable: Forms > Campaigns, Additional options, Native Browser Prompt, Actions, set Active.

iOS Install Prompt

iOS Safari doesn't support web push the way Chrome and Firefox do. The workaround: ask visitors to install your storefront as a home-screen PWA. Once installed, iOS does support push (iOS 16.4+).

What it looks like

A custom in-page card that says something like "Add {store name} to your home screen," with steps for the Share, Add to Home Screen flow.

When to use it

Your store has meaningful iOS traffic (most consumer stores do).
You want web push reach on iOS visitors (currently blocked unless they install).

What the visitor does

Sees the prompt.
Taps the iOS Share button.
Picks Add to Home Screen.
Confirms.
Your icon appears on their home screen; tapping it opens your store in PWA mode.
From PWA mode, the visitor can grant web push permission.

Trade-off

The install flow adds steps that not every visitor completes, so conversion is lower than a single web push prompt on Chrome.

To enable: Forms > Campaigns, Additional options, iOS Install Prompt, Actions, set Active.

Should I use one surface, or layer them?

Setup	When
Popup with Web Push step only	Most stores. The popup explains the value, then asks.
Popup + Native Browser Prompt	High-traffic stores looking to maximize web push reach. The popup catches motivated visitors; the Native Prompt catches the rest.
Popup + iOS Install Prompt	Stores with significant iOS traffic that want push on iOS.
All three	Mature stores optimizing every channel.