Push notifications, automations and in-app campaigns

Push is built in: no third-party service, no extra plan. Under Push you send campaigns and run automations; under Campaigns you add in-app messages that are part of the published design.

Campaigns

Write a title and message, add an optional image URL, choose where a tap opens (a product, a collection or any screen), pick the audience and platforms, and send now or schedule it. Each campaign shows its status (draft, scheduled, sending, sent) and how many devices it reached.

Automations

Switch each one on with a toggle and set its delay and message:

• Welcome: minutes after a shopper allows notifications.
• Abandoned cart: minutes after the last change to a bag that was left behind. Skipped automatically if they checked out.
• Win-back: days since a shopper last opened the app.

Who can receive push

The Push page shows installs, how many can receive push, and how many were active in the last 30 days, split by iOS and Android.

Your app asks for notification permission at a moment that earns it: the second time it is opened, or the first time something is added to the bag. Shoppers who decline can still enable notifications in their phone's settings.

What each platform needs

• iPhone: an APNs push key from developer.apple.com → Keys (Apple only lets the account owner create it), sent to support@appfromshop.com so we can attach it to your build credentials. Builds and TestFlight work without it; notifications do not.
• Android: nothing. Android push runs on Firebase projects AppFromShop owns.

In-app campaigns

Under Campaigns, add a popup, bottom sheet or top banner with an image, title, message, button and an optional copyable discount code. Choose the trigger (app open, a screen, or a delay), how often it shows (once, daily, every launch) and the same audience and schedule rules as sections. They ship with your next publish.