Send Push
What it does
Section titled “What it does”Send a notification to every phone and browser that turned on notifications for your site, even while the site is closed - now, or at a time you pick. The page also shows how many players use the installed app and how many of them say yes to notifications.
Where to find it
Section titled “Where to find it”Marketing -> Send Push
The page needs the menu:config/push permission. If web push is not available, a warning says so and sending is disabled; contact support.
Send a notification
Section titled “Send a notification”- Give it a Title (up to 80 characters) and a short Text (up to 240).
- Set the Link a tap opens: a path on your site, like
/promotions, or a link on one of your site’s domains. - Leave Also send to devices where no one is logged in ticked to reach every subscribed device, or untick it to reach only devices with a player logged in.
- Choose Send now, or Schedule and pick a time in your site’s timezone (at least a minute and at most 30 days ahead).
A site can create a limited number of sends an hour. A scheduled send can be cancelled from the history until it goes out.
Every send that went out also appears on your players’ Notifications page (the bell at the top of the site, or the menu) for 30 days, so a player who missed the notification, or never turned notifications on, can still read it. A player who registers after a send does not see it there.
Send history
Section titled “Send history”Each send shows when it was made and by whom, its send time, status, and counts:
- Devices - how many devices it was queued for.
- Sent - delivered to the device’s push service.
- Failed - not delivered.
- Removed - devices that no longer accept notifications, removed from your list.
- Clicked - how many times a player opened the notification.
The Reach card counts your audience:
- Installed app - players who opened your site as the installed app (added to the home screen) in the last 30 days.
- From the installed app - subscribed devices that turned notifications on from the installed app.
Its table follows players through each step, for the last 7 and the last 30 days, with the share of the step before:
| Step | What it counts |
|---|---|
| Asked to turn on notifications | Your site showed its own “turn on notifications?” prompt. |
| Said yes / Said not now | The player’s answer to that prompt. |
| Allowed / Blocked in the browser | The browser’s own permission answer, after a yes. |
| Delivered (your sends) | Notifications from this page that a device’s push service accepted. |
| Opened (your sends) | Taps on those notifications. |
| All notifications opened | Every notification tap, including the automatic deposit and withdrawal alerts. |
The counts come from players’ devices and are approximate. A player who blocks notifications in the browser cannot be asked again on that device, which is why your site asks with its own prompt first.
Related
Section titled “Related”- Web Setting - the push alerts players get for deposits and withdrawals.
- Roles & permissions