Website integration
Create a site and install Pushrr on any HTTPS website without a CMS or commerce app.
Website integration
1. Create a site
Choose Create new site from the site selector in the top bar, enter the site's name and public HTTPS origin, and choose Create site. The new site's settings page opens with its installation code and one-time API verification key. A site is the isolation boundary for subscribers, browser configuration, credentials, campaigns, and analytics.
Pushrr generates two different credentials:
| Credential | Where it belongs | Secret? |
|---|---|---|
Browser SDK key (wpk_…) | Public website code | No |
API verification key (sk_site_…) | Server, plugin, or app backend | Yes |
2. Save the API key
The site API key is displayed once. Store it in a password manager or server secret store. Never put it in browser JavaScript, a public repository, or a theme template.
3. Install the website code
Copy Website installation code and place it before the closing </head> tag. The default setup uses the site's hosted subscription origin, so the website does not need to serve a service-worker file itself.
4. Test a subscriber
Open the exact site origin saved in Pushrr, allow notifications from a supported browser, and confirm the browser appears under Subscribers.
Keep subscriber identity stable
Do not replace an existing site's SDK key, hosted subscription origin, service-worker path, or VAPID keys. Create a new site only for a genuinely separate subscriber audience. Normal site edits and API-key rotation do not alter those browser identity fields.
Shopify and WordPress
Shopify can use its dedicated app and same-origin app proxy. The separately developed WordPress plugin will ask for a site API key and call the same Pushrr API. Neither integration needs a different subscriber data model.