Custom Events

Events are user actions tracked by the system. They are the foundation of auto-push: when an event occurs on the server, Notify Partners automatically triggers the attached push scenario with a specified delay.

Event Types

System Events

Created automatically and available to all platform users. They cannot be deleted or renamed.

System events are visible through all API keys regardless of project_id.

Custom Events

Created by you for specific actions in your product. Examples:

• tutorial_complete — completing the tutorial.
• level_10 — reaching level 10 in a game.
• purchase — making a purchase.
• cart_abandon — abandoned cart.
• win_big — large win.

Custom events can be activated and deactivated — a deactivated event does not trigger auto-push but remains in the system.

Creating an Event

1. Go to Events and click "Create".
2. Enter the event code — Latin letters, digits, underscores (e.g., purchase_premium).
3. Enter a name for convenient display in the interface.
4. Save and activate the event.

How Events Reach the System

Events are sent from your backend via a postback — an HTTP GET request to the Notify Partners API:

GET /postback?app_id=APP_ID&token=POSTBACK_TOKEN&event=reg&ic=INSTALL_TOKEN

Parameters:

• app_id — application ID from the dashboard (required).
• token — postback token from the application settings.
• event — event code (e.g., reg, purchase).
• ic — device install token (obtained via SDK on installation).

Optional parameters:

• external_id — external user identifier (alternative to ic).
• segment — audience tag to assign to the device.
• webmaster — webmaster identifier.
• offer — offer identifier.

The system also accepts POST /postback with the same parameters in the request body.

After receiving the postback:

1. The system finds the device by ic (or external_id).
2. Records the event for this device.
3. If there is an active auto-push scheduler for this event — starts the delay timer.
4. After the delay expires, sends the push.

Incoming postback history can be viewed in Analytics → Postback History.

Using Events in Auto-Push

When creating a scheduler of type Auto-Push (Conversion):

1. Select the event that triggers the scheduler.
2. Specify the delay in minutes.
3. Attach the push template.

Example chain:

Using Events in Filters

Events are also available in scheduler filters — regardless of send type (instant, scheduled, weekly):

• Include — send only to devices that had the dep event.
• Exclude — send to everyone except devices with the dep3 event.

This allows building complex segments: for example, "users who registered but haven't made a deposit yet" = filter "has reg" + "no dep".

API