My Dashboard

Install PopupNeko

Choose your platform and add one site-wide script to start displaying verified activity.

On this page
  1. Before you install
  2. Choose where popups appear
  3. Test on the right domain
  4. Verify after publishing
  5. Updating or removing the embed

PopupNeko works through a single JavaScript embed. Its styles are included, so you do not need a separate stylesheet or a PopupNeko framework package.

ReactView guide Next.jsView guide VueView guide NuxtView guide AngularView guide HTMLView guide FramerView guide WordPressView guide WixView guide

Before you install

Create a project for your production domain and connect a source. You need active trial or paid access to copy the live script, verify installation, and display live popups. Keep the project enabled when testing live delivery.

Open Install Script in the project dashboard and copy the generated script. It contains your project's ID. The example below uses a placeholder; replace it with the value from your dashboard.

html
<script
  defer
  src="https://popupneko.com/script/popupneko.js"
  data-project-id="YOUR_PROJECT_ID"
></script>

Install it once in your global HTML <head> or shared layout. Keep it outside frequently mounted page components. The script loads configuration and eligible activity for the current pathname and handles History API navigation automatically.

Choose where popups appear

New projects use Recommended targeting, which allows / and /pricing. In the Install Script page's targeting section, choose Specific for your own paths or All for every page that loads the script. See Page targeting for matching rules.

Adding the script to every page does not override targeting. A script can be installed successfully without displaying a popup on the page you are viewing.

Test on the right domain

Your production domain and its www equivalent are allowed. Add up to two exact online test/staging hostnames in Allowed Domains if you need them. Wildcard hosts are not supported.

Localhost, 127.0.0.1, and ::1 are allowed on any port without using a staging slot. Localhost and staging can display popups but do not contribute to production popup analytics. Live access and event/targeting rules still apply unless you use an authorized live-site preview.

Installation verification is separate: it checks a URL on the saved production domain, not a staging or localhost URL.

Verify after publishing

  1. Deploy or publish the site with the script included.
  2. Visit an allowed page on your production domain.
  3. Return to Install Script. PopupNeko makes one automatic homepage check for an unchecked production installation.
  4. To check a particular page or retry, enter its production URL and choose Verify Connection.

The verifier reads the page's returned HTML and checks for the PopupNeko script URL and matching project ID. It does not execute the page's JavaScript. Prefer a server-rendered script tag when possible. If a tool injects the tag only after hydration or consent, the popup may work while verification reports it undetected; see script detection.

Updating or removing the embed

Dashboard configuration changes apply when the script next initializes, including after a distinct pathname change. You do not need to reinstall it for ordinary design, event, or targeting changes.

To stop live popups temporarily, disable the project. To remove the installation, remove the script from your site's global layout or custom-code settings and publish again. Remove duplicates left in tag managers or page-level code too.

For a complete first-run walkthrough, follow Getting started.