Push Notifications

MakerVera supports push notifications as a delivery channel alongside email and SMS. Push notifications appear directly on your phone or tablet — no app inbox to check, no email to open.

Mobile app required

Push notifications require the MakerVera companion mobile app. This feature is available once the app is installed and you’ve registered at least one device.

For Members — Managing Your Devices

Registering a device

When you install the MakerVera mobile app and sign in, the app automatically prompts you to allow push notifications. If you accept:

1. Your device is registered with your MakerVera account
2. You’ll start receiving push notifications for events you’re opted in to
3. The device appears in your Profile → Settings → Push Notifications section

Viewing your registered devices

1. Go to your Profile (click your name or avatar in the top right)
2. Select the Settings tab
3. Scroll to the Push Notifications section

You’ll see a list of all your registered devices, showing:

Column	What it shows
Device	A platform badge (iOS, Android) with the device identifier
Registered	When the device was registered
Remove	Button to unregister the device

Removing a device

If you no longer want to receive push notifications on a specific device:

1. Find the device in your Push Notifications list
2. Click Remove
3. Confirm the removal

The device is immediately unregistered. No further push notifications will be sent to it. You can re-register by signing in to the mobile app on that device again.

Device limits

Each member can register up to 10 devices. If you reach this limit, you’ll need to remove an existing device before registering a new one. This limit is in place to prevent accidental token accumulation from reinstalls or device changes.

For Admins — Push Notification Templates

Editing push content

Push notifications have their own template content, separate from email and SMS.

1. Go to Admin → Notifications → Templates
2. Find the template you want to add push content to
3. Click Edit and select the Push tab
4. Fill in the push notification fields:

Field	Limit	Description
Title	100 characters	The bold headline shown in the notification
Body	255 characters	The message text shown below the title
Deep Link URL	Optional	A URL that opens when the member taps the notification

5. Click Save

Deep link URLs

Deep links let you direct members to a specific screen in the app when they tap the notification. Supported URL protocols:

• https:// — opens in the app’s built-in browser or navigates to a matching app screen
• http:// — same as https
• makervera:// — app-specific deep links (e.g., makervera://events/123)

Other URL protocols are rejected by the editor to prevent security issues.

Keep push content concise

Push notifications are glanceable — members see them on their lock screen or notification shade. Even though the limits are generous, aim for a clear title and a one-sentence body. Save the details for the email.

Enabling push on a notification rule

1. Go to Admin → Communications
2. Click on an existing rule or create a new one
3. Set the Channel to Push
4. Select a template that has push content configured
5. Save the rule

Like SMS, you can have separate email, SMS, and push rules for the same trigger event.

How Push Delivery Works

Delivery pipeline

Push notifications follow the same notification pipeline as email and SMS:

1. A trigger event fires
2. The dispatcher finds matching rules with channel set to Push
3. For each recipient, the system:
   • Looks up the member’s registered device tokens
   • Sends to all registered devices (a member with 3 devices gets 3 push notifications)
   • Automatically removes stale tokens (e.g., uninstalled app, expired registration)
4. Results are logged in the delivery log

Delivery statuses

Status	What it means
Sent	Push notification accepted by the push service for delivery to one or more devices
Failed	The push service rejected the message — check the error detail
Suppressed	The member has no registered devices, or has opted out of this notification category

Stale token cleanup

When a member uninstalls the app or the device token expires, the push service reports the token as invalid. MakerVera automatically removes these stale tokens — no admin action is needed. The member’s device list updates accordingly.

Troubleshooting

A member says they didn’t receive a push notification

1. Check their device list — they need at least one registered device. Ask them to check Profile → Settings → Push Notifications.
2. Check the delivery log — filter by Push channel. A suppressed status means no devices are registered or the member opted out.
3. Check the member’s phone settings — push notifications may be disabled at the OS level (Settings → Notifications → MakerVera on iOS/Android).

Push notifications are delayed

Push delivery depends on the device’s network connection and the operating system’s notification scheduling. Some factors:

• Battery optimization — Android may batch notifications when in battery saver mode
• Do Not Disturb — notifications are held until DND ends
• Network connectivity — offline devices receive notifications when they reconnect

These are device-level behaviors outside MakerVera’s control.

Best Practices

1. Complement, don’t replace — push notifications work best alongside email, not as a replacement. Use push for time-sensitive alerts and email for detailed content.
2. Keep it short — even though the limits allow up to 100 characters for the title and 255 for the body, shorter is better. If you can’t say it briefly, it’s probably an email.
3. Use deep links — tapping a notification should take the member somewhere useful, not just open the app’s home screen.
4. Don’t over-notify — members can disable push notifications at the OS level, and once they do, you can’t get them back without the member manually re-enabling them.