Re-engagement
A small place to start again
Explore a beginner lesson whenever you are ready to return.
Workflow
Invite an audience you have identified as inactive to return with a useful message. Generate copy and send on the schedule you choose.
Generated from your business context and campaign goal.
Firebase topics or OneSignal segments.
Dates, send times, and a campaign timezone you choose.
Begin by maintaining an inactive-user audience in your app or provider. Then register the Firebase topic or select the OneSignal segment in PushPilot and write a campaign brief with a clear reason to return.
FIND THE RIGHT MOMENT
Start with a clear reason to reach your audience.
FROM SETUP TO SEND
Use this sequence to shape the campaign in your workspace.
Connect your Firebase project or OneSignal app. Confirm devices can receive notifications and belong to the topic or segment you plan to target.
Add the business context, objective, tone, and accurate facts that should guide the generated messages. Avoid claims that depend on individual data the campaign does not have.
Set the campaign date window, frequency, send time, and timezone. Check other campaigns aimed at the same audience when deciding how often to send.
Review the campaign details and any preview samples. Activation starts generating actual upcoming notifications in the Scheduled state; a preview is not a queued send.
Inspect and edit scheduled copy before its send time. Check notification status and available analytics, then adjust the brief or pause the campaign if needed. Engagement reporting depends on tracking events.
EXAMPLE MESSAGES
These notifications illustrate the workflow. Adapt the content for your own app.
Re-engagement
Explore a beginner lesson whenever you are ready to return.
Re-engagement
Take a look at the latest learning collection in the app.
Re-engagement
One short lesson is enough to get started.
THE CAMPAIGN SETTINGS
BEFORE YOU ACTIVATE
Consider these cases before the first scheduled send.
Your app or provider needs to remove people when they no longer qualify. PushPilot does not automatically detect a return visit, stop a user’s sequence, or enforce a per-person frequency cap across campaigns.
AI copy can need correction. Check dates, offers, feature names, and tone before the scheduled send, especially when the underlying information changes.
A schedule controls this campaign. Consider other campaigns and provider sends reaching the same people; a per-user cap across campaigns is not part of this workflow.
A successful provider send does not by itself prove a person saw or opened the message. Use available tracking events and your own product data to assess engagement.
Yes. Connect the provider your app uses and select its registered topics or segments. Your application must be configured to receive notifications and maintain audience membership.
No. This guide uses scheduled campaigns. Activity-based audience membership must be maintained in your app or provider. Each campaign uses the dates, frequency, and timezone you set.
Active campaigns generate upcoming notifications in the Scheduled state. You can review and edit them before their send time. If a notification is Pending, its Approve action schedules it.
PushPilot uses your campaign context and recent copy to generate upcoming messages. Review the results for repetition and accuracy. There is no guarantee that each message will be unique or that engagement will improve.
See the current Pricing page and Settings → Billing in your workspace. Your plan controls notification allowance, active campaigns, and AI image availability.