What is PushFire?

Push notifications are critical to the success of any mobile app. In fact, it's the key advantage between web and mobile - the ability to reach your users when and how you want to.

There are two key types of push notifications:

1. Triggered notifications. For example, when one user sends another a message, you can easily trigger a push notification to the user receiving a message.
2. Notification workflows. Imagine an onboarding workflow, when a user abandons a cart, or after they cancel a subscription.
   1. Note: we sometimes call these drip campaigns.

PushFire is the easiest way to build push notification workflows.

Traditionally, if you want to build a push notification workflow, you or your developer would have to write code for each notification, waiting period, and logic. This is expensive and more importantly it's difficult to change, test, and iterate.

PushFire is the easiest way to build, test, and deploy push notification workflows for Firebase push notifications.

Use PushFire's visual drag and drop interface that includes:

• Entry requirements for which users are included in a workflow.
• Push notification nodes - create nodes with titles and body for push notifications.
• Wait nodes - can choose a wait durations like one day, two weeks, etc.
• Conditional nodes - these are logic nodes that allow you to split the workflow based on conditions, like the user's language or spending habits.

Mobile application founders, marketing, and go to market teams use PushFire to develop push notification workflows.

One of the benefits of using PushFire is that it doesn't require development experience. It's easy to visually create push notification workflows instead of writing code. This empowers non technical founders and teams, like marketing, to add, change, and analyze workflows.

You can use PushFire to build push notifications workflows for any user engagement strategies.

Here are a few examples of workflows we've seen:

• Onboarding push notification campaign
• Re-engage inactive users

PushFire can also be used to develop push notifications for any industry or use case. For example, you can build workflows for:

• Improving cart recovery in ecommerce. For example sending a series of push notifications reminding users there are items in their cart if they don't checkout in a specific time period.
• Onboarding workflows in wellness apps. For example users receive one message per day with a tip or trick for using the app.
• Re-engaging inactive users in a game. If a user doesn't use the app for a month, you can send them a push notification about a new feature, event, or words of encouragement to return to the app.

One key element of workflows is they can always be improved. In PushFire, you can view metrics related to workflows to better understand how they're performing. Once you have a baseline, you can begin testing the workflows to improve them. For example, does changing a wait period from one day to two days improve activation? Or does a shorter period reduce the cart abandonment rate?

This is where PushFire really shines. It's the easiest way to A/B test and improve your push notification and user engagement sequences.

Since you're making these changes in PushFire's visual editor, it saves significant engineering and development resources as well.