Troubleshooting

Start with the symptom below. Check your selected project before changing settings: each project has its own ID, domain, sources, and configuration.

No popup appears

1. Check Billing for live access and ensure the project is enabled. Configuration access alone does not enable live delivery.
2. Confirm the script contains the selected project's ID and loads from https://popupneko.com/script/popupneko.js.
3. Visit an allowed hostname and path. New projects target / and /pricing, not every page.
4. Check Integrations for a connected source. On Events, enable the event types you need and save.
5. Use Real events in the Events preview. If empty, check eligible payments inside the age window or your saved review selection.
6. Check Customize's start delay, section trigger, display limit, and mobile visibility settings.

A popup stops after the available events or display allowance are exhausted. It does not repeat activity just to fill a larger limit. For a clean test, use a new browser-tab session when testing session-scoped limits.

Script is running but verification fails

The installation verifier downloads the selected production page's HTML. It looks for the hosted script URL and matching data-project-id; it does not execute JavaScript.

Open the page's source or inspect the document response in your browser's Network panel. A tag visible only in the live Elements inspector may have been inserted after hydration, by a tag manager, or after consent. That can run a popup without passing the HTML check.

Put one deferred script in a server-rendered global head/template where possible. If your platform cannot expose it in returned HTML, a client-only installation may remain undetected by the current checker. Repeated checks do not make the checker execute JavaScript.

Also confirm the deployment has finished, the verification URL uses the saved production domain, and the page is publicly reachable without login or a bot challenge. Use Verify Connection again after correcting the installation.

Popups work on one page or domain only

Check Page targeting. Paths are case-sensitive, trailing slashes are normalized, and a prefix rule such as /product/* differs from the exact path /product.

Check Allowed Domains for online staging hosts. Up to two exact test/staging hostnames are supported; wildcard hosts are not. Localhost is allowed without a slot. A hostname restriction cannot be fixed by adding a page path.

For single-page apps, install once in the global document/layout. History-based pathname changes are supported; hash-router screens and query-string changes do not create separate targeting paths.

Integration is connected but payments are missing

Connected confirms a successful connection, not that every provider transaction qualifies for a popup.

Review the provider-specific guide: Stripe, Lemon Squeezy, or Polar. Newly started subscriptions and eligible sales are supported; renewal activity is excluded from the popup feed.

Confirm the correct provider account/organization, live data, enabled event types, and the 1–7 day payment-age window. Save Events settings before testing the installed site. The feed is capped at 20 events and is not a complete transaction export.

Review import or display fails

Check that the Chrome Web Store listing is connected and ownership is confirmed. The review must be publicly accessible, belong to that listing, and pass eligibility/content verification.

An imported review needs its popup-display switch enabled and its selection saved. Enable Reviews on Events too. New or edited excerpts must be exact source passages of at most 130 characters, and the selection is capped at 15 reviews.

Check the remaining import allowance before retrying: once an external request starts, an attempt can be consumed even if it fails. See Reviews.

Product images or links are missing

Sync the current provider's active products, check the saved product override, and choose the appropriate image mode in Customize. An unavailable or slow image can use a fallback.

Product links need both a product URL and the product-link display option. Original review links need an available source URL and the review-link option. The excerpt and empty popup surface are not clickable substitutes.

A browser blocks the script or assets

Use the browser's Network and Console panels to identify the exact blocked request. Consent tools, content blockers, script optimizers, and Content Security Policy can each affect loading.

The installation needs the PopupNeko script, its configuration request, injected styles, and the selected image/font resources. A policy may allow the script yet block one of those other resources. Update the relevant policy for the specific required origins/directives after reviewing the reported error; do not disable your policy wholesale.

Avoid delaying the embed indefinitely or converting it into a non-executable script type. If consent is required by your site's setup, test after consent is granted.

Saved changes are not visible

The dashboard sample preview uses the current draft. Installed popups and the live-site preview use saved configuration. Choose Save Changes, then reload or navigate to a different pathname to initialize the popup again.

Events settings and Customize settings have separate saves. Product and review changes also need their own save actions. Check the page containing the setting you edited.

Profile or analytics is unavailable

A verified profile also requires detected installation and a qualifying source. A working local preview does not satisfy those requirements.

Popup analytics count production-domain traffic, not localhost, staging, or preview sessions. Verified Orders depends on the payment connection and is separate from the popup feed. If payment or access status is stale after returning from Stripe, refresh Billing before testing again.