Adset.ProAdset.ProKnowledge base
Home/Push Notification

Push Notification

Push notifications allow sending messages to users who subscribed on pre-landing pages or on PWA.

The system supports:

  • Regular notifications (on schedule)

  • Event notifications (triggered)

  • Content localization for different countries

Regular Notifications

Regular Push Notifications are pre-scheduled messages that are sent to users on a schedule. The system has a notification scheduler, where you can lay out the sends by time slots (specific time windows) and set which notifications should be sent automatically and when.

Each notification is configured with a target — the group of users to whom it will be sent:

  • Everyone — the entire audience.

  • Reg- / Dep- — users who have not registered and have not made a deposit.

  • Reg+ / Dep- — users who have registered, but have not made a deposit.

  • Reg+ / Dep+ — users who have registered and made a deposit.

Purpose

Regular push notifications help:

  • Automate communication with users without manual mailings every day/week.

  • Deliver messages at the right time, increasing the likelihood of opening and action due to properly chosen time slots.

  • Work more accurately with different segments: separately warm up new users, return undecided ones, support active users, and retain those who have already made a deposit.

  • Increase conversion through the funnel (registration → deposit → repeat deposit) through systematic and regular support for the user at each stage.

Event Push Notifications

Event Push Notifications are messages that are sent to the user after a specific event occurs in the product. Unlike regular notifications, they are not tied to time slots, but are triggered by a trigger and are sent with a specified delay after the event.

Available triggers:

  • PWA Install — sent after PWA installation. Recommended minimum delay — from 10 minutes, because the process of subscribing to push usually occurs between installation and registration.

  • Registration — sent after registration.

  • Deposit — sent after making a deposit.

How to configure

For each event, the following is set:

  • Delay after the event (for example, after 10 minutes / 1 hour / 24 hours).

  • Target (audience segment), similar to regular notifications:

    • Everyone

    • Reg- / Dep-

    • Reg+ / Dep-

    • Reg+ / Dep+

Targeting limitations (exclusions)

Some targets for certain events are not advisable and are unavailable:

  • For the Registration event, the target Reg- / Dep- cannot be selected
    (the event “Registration” cannot occur for those who are not registered).

  • For the Deposit event, the targets Reg- / Dep- and Reg+ / Dep- cannot be selected
    (the “Deposit” event notification is received by users who have already made a deposit, so the logical segment is Reg+ / Dep+, or “Everyone” if necessary; this target is unavailable for segments without a deposit).

Purpose

Event notifications help:

  • Respond in a timely manner to user actions and lead them to the next step.

  • Increase conversion through messages at the moment when the user is most engaged.

  • Improve onboarding and retention — for example, support after installing PWA, reinforce value after registration, or enhance further activity after a deposit.