Skip to main content
PushNotifAI runs your app’s push notifications. Your app streams its analytics events to us. An AI reads how your users behave and proposes which notifications to send, when, and to whom. You approve or reject each proposal. A deterministic engine then makes every send over our own APNs connection.
The AI writes the strategy. It never decides an individual send. Every push traces back to a rule you approved and can read, so “why did this user get this notification?” always has an exact answer.

​
What you get

Proposals with a reason

Each suggested change comes with the diagnosis behind it: “61% of users never add a second connection, so nudge them after 48 hours.”

Flows you can read

A flow is a plain rule over one user’s events: “did X, then didn’t do Y for two days, so send this.”

Real delivery numbers

APNs only confirms it accepted a push. Our extension reports when it actually reached the device, then whether it was opened or dismissed.

Honest measurement

A permanent holdout group gets no notifications, so you can see whether your notifications help or hurt retention.

​
How the pieces fit

  1. The iOS SDK sends your events, links devices to your user ids, registers push tokens, and reports delivered, opened and dismissed.
  2. The Composer reads the aggregate behavior and how your current flows are doing, and proposes flows to create, adjust, pause or retire.
  3. You review proposals in the dashboard. Nothing sends until a person activates a flow.
  4. The engine matches events against active flows, applies quiet hours, caps and cooldowns, and sends. It records every decision, including the ones where it chose not to send, and why.
Ready to integrate? Start with the quickstart.