Messages & notifications

SMProxy exclusive

A provider can send users in-app messages. They arrive inside the Provider ID check response and land in the app inbox (bell icon + unread counter), optionally triggering a system notification.

Each message has: id, title, body, optionally date, type (info/update/promo/warning), url, notify and targeting. Read status is stored locally per device.

Targeting

Compose messages in the provider portal. By default a message goes to everyone; each filter below narrows that down, and they combine.

Platform and app build

Tick the platforms that should receive the message. Leave the build field empty to reach every version of that platform, or set a condition (<, ≤, =, ≥, >) to reach only some of them.

Build numbers are per-platform — iOS 200 and Android 200 are unrelated releases — so a condition is always tied to a platform. Ticking nothing means “all platforms”; as soon as you tick one, the others receive nothing. That is how you reach users still on an old iOS build without touching Android:

Ticked	Build condition · Who gets it
nothing	— · everyone
iOS	— · every iOS user
iOS	< 200 · iOS users below build 200
iOS, Android	iOS < 200, Android < 300 · old builds on both, nothing elsewhere

Subscription domain

Pick a verified domain to reach only the users whose subscription is served from it — *.example.com for the domain and all its subdomains, or a single host such as sub.example.com for that host alone. The portal shows how many devices are currently on each host.

Requires a verified domain — see Domain verification (section 05a).

A single device

Paste a HWID to send the message to exactly one device — useful when you are walking one user through a problem.