Admin Guide

Users

A user is any visitor to your site or app who has ever interacted with the subscription prompt. The Users section gives a complete overview of your audience: statuses, tags, devices, and activity history.

What is a user

A user record is created automatically on the SDK's first contact with your site. A user can have multiple devices (browsers) — each is a separate subscription. One user can have several active subscriptions at the same time.

External ID

Your internal user identifier (ID from CRM, email, etc.). Set via SDK or API. If not provided — Notirix generates an anonymous ID. Used for sending messages to a specific person.

Last Seen

The time of the user's last visit to the site. Updated on every SDK call. Used in segments for the "active within N days" filter.

User statuses

Each user has one of three statuses. The status determines whether a notification can be sent.

active
Active

User allowed notifications and has an active push endpoint. Notifications are delivered.

unsubscribed
Unsubscribed

Set via the Server API (DELETE /api/apps/:appId/users/:id) or manually in the admin panel. Notifications are not sent. Re-sending an existing subscription keeps the status; a new subscription (another browser or device) makes the user active again.

blocked
Blocked

Set manually in the admin panel. Notifications are not sent, and the status stays even when the user subscribes again — only an admin can make the user active again.

ℹ️
When the push service returns 410 Gone or 404, Notirix deactivates that subscription (endpoint) and stops sending to it. The user status does not change: the user's other browsers and devices keep receiving notifications.

Table columns

The users table shows key characteristics. Columns can be toggled with the "Columns" button in the toolbar.

ColumnDescription
External IDYour internal user identifier. If not provided — the anonymous Notirix ID is shown.
StatusCurrent status: active / unsubscribed / blocked.
Last SeenWhen the user last visited the site with an active SDK.
SubscriptionsNumber of active web push subscriptions (browsers/devices).
TagsNumber of tags set.
Created AtDate of the user's first appearance in the system.

Filters and search

Use the toolbar to quickly find users:

Search by ID

Enter the External ID or part of it. Search uses partial matching (substring).

Filter by status

Filter the list by status: All / Active / Blocked / Unsubscribed.

User tags

A tag is a key→value pair attached to a user. Tags are used for audience segmentation. For example, the tag plan = premium lets you create a "Premium Clients" segment and send them targeted campaigns.

js
// Tags are set via the Web SDK (after the user has subscribed)
await notirix.sendTags({ plan: 'premium', city: 'Moscow', total_orders: 14 })

// Tags are used in segments:
// Rule: tag "plan" = "premium"  →  all users with plan=premium

Tags can be set in three ways:

1
Via Web SDK — notirix.sendTags() or notirix.sendTag(key, value). Call on the frontend once the user has subscribed.
2
Via REST API — POST /api/apps/:appId/users/external/:externalId/tags/bulk. Suitable for server-side integration and bulk updates.
3
Via Bitrix module — PushClient::setUserTags(). For sites on 1C-Bitrix.
💡
Tag values are strings, numbers, booleans or arrays. If a tag with this key already exists — it is overwritten (upsert). A tag with an empty string is considered non-existent and does not participate in segmentation.

User profile

Click on a row in the table to open the user's detail page. All information about a specific person is collected here.

User information

External ID, status, creation and last activity dates.

Tags

All set tags with keys and values. Used for segmentation.

Web subscriptions

List of browsers where the user granted notification permission: browser, OS, subscription date, endpoint status.

Mobile devices

FCM tokens of mobile apps (Android/iOS) connected via Mobile SDK.

Segments

List of segments this user falls into based on current rules.

Deleting a user (GDPR)

The "Delete user" button on the detail page deletes the user record along with all their subscriptions and tags. This is an irreversible operation. Use it to fulfill requests for personal data deletion (right to be forgotten).

⚠️
After deletion, the user will not receive notifications. If they grant notification permission again — a new record with a new ID will be created.

Related sections

→ Segments

User tags are the main segmentation tool. Create tags here, then use them in segment rules.

→ Messages

Via the REST API (POST /messages, field userId) you can send a message to a specific user — look up their Notirix ID by External ID first.