Skip to main content
First-party Capgo Notifications

Capgo Notifications Native push, silent update checks, and campaign visibility

Message users, update badges, and trigger live-update checks from the same Capgo release workflow. Notifications now connect native push with progressive deployments instead of leaving release teams to stitch it together.

Native notifications work alongside Capgo Live Updates and channel rollouts.

+ Provider setup in Capgo + Broadcasts and API sends + Progressive rollout companion

iOS + Android

Native push delivery

External ID

Target known users

Badge + events

Track opens and state

Update checks

Silent push companion

Next or set

Install mode control

Channel-aware

Guide live updates

Capgo notification dashboard showing provider setup, campaigns, and push update controls
Provider setup, broadcasts, API sends, and push update controls in one console.
Mobile view of the Capgo notification console
Usable on mobile during release work.
Release communication

Push is now part of the deployment loop.

Capgo Notifications gives product teams the messaging surface they expect and gives release teams a native way to wake devices for live-update checks.

Reach the right devices

Register devices with an external ID, tags, attributes, and consent so campaigns can target real product audiences instead of anonymous tokens.

Move updates faster

Use a silent notification to ask opted-in devices to check, download, and queue the latest Capgo bundle for the channel you choose.

Prove what happened

Track provider setup, campaigns, delivery events, opens, badge changes, and background update-check results from the Capgo console.

Use notifications when a release needs a nudge.

  • Tell users about a change that ships with a live update.
  • Ask devices to check for a bundle without waiting for the next app open.
  • Keep progressive rollout, channel, and install-mode controls in place.
Workflow

From provider setup to targeted update checks.

The notification plugin, Capgo console, and updater now work together for Capacitor apps.

1

Configure providers

Add Android and iOS push credentials in the Capgo console, then run the notification setup so the native plugin and updater are wired together.

2

Register recipients

Attach external IDs, tags, attributes, consent, and badges from your app so support, growth, and release workflows share the same device identity.

3

Send or trigger updates

Broadcast alerts, send API notifications to one user, or push a background update check during a progressive rollout.

Feature set

Native notifications without a separate release stack.

Capgo handles the surfaces that usually become one-off glue code around push, user targeting, and update nudges.

Capgo Notifications
Native push for release teams
Ship alert, background, badge, and update-check campaigns from the same product console your team already uses for Capgo releases.
$ npx @capgo/cli@latest notifications setup
provider ready | recipients linked | update check enabled

Provider control plane

Keep Android and iOS notification providers active from the same Capgo app settings screen used by your release team.

Broadcast campaigns

Create alert, background, badge, or update-check campaigns when you need to reach every matching device.

API sends

Send a notification to a known external ID and inspect the devices linked to that recipient before you trigger it.

Badge management

Read, write, and sync app badge counts through the native plugin so notification state remains visible to users.

Background callbacks

Handle foreground receives, notification opens, and background data notifications in your Capacitor app.

Campaign stats

Follow campaign status, delivery results, opens, and update-check results without leaving the Capgo release workflow.

Rollout guidance

Use push to accelerate updates, not bypass controls.

Silent notifications can ask devices to check for a new bundle, while Capgo channels, install mode, and progressive rollout rules continue to decide what each device can install.

  • Use alerts for user-facing messages and background campaigns for release operations.
  • Keep silent update checks paired with channels and progressive rollout controls so every device still follows your deployment rules.
  • Treat iOS background pushes as best-effort because the operating system can throttle delivery.
Capgo notification update check panel with install mode and channel controls

$ notification.kind = update_check

channel selected | install mode next

progressive rollout still controls eligible devices

devices check, download, and queue the bundle

Capgo Notifications
Reach users and move releases forward.

Add native push, badge control, campaign stats, and silent update checks to your Capacitor release workflow.

Start with Capgo
+ Native iOS and Android push + Background update checks + Campaign stats

Keep going from Capgo Notifications

Connect native notifications with Capgo Live Updates, Capgo Pricing, Capacitor Notifications, Channels, and Update Behavior when you plan progressive deployments.