# Push notification implementation guides

Push brings a customer back to an installed application or a subscribed website. A complete integration connects app permissions, device registration, message content and the screen opened after a tap.

## Send a first notification

[Send your first push notification](/docs/get-started/send-your-first-push-notification) includes a complete browser registration and Channels API send, with a campaign path when you want to use the dashboard. Verify a test device before scheduling customer traffic.

## Connect the platform

Read [platform setup](/docs/guides/push/platform-setup) for the relationship between Bird's push channel, your app and its notification transport. Keep [device registrations](/docs/guides/push/device-registration) current when tokens or signed-in accounts change.

## Finish the customer action

A notification should open a useful destination. [Deep links](/docs/guides/push/deep-links) covers cold starts, sign-in and destinations that no longer exist. The [journey guide](/guides/design-a-push-notification-journey) connects the notification to a customer outcome.

## Operate and migrate

Use [troubleshooting](/docs/guides/push/troubleshooting) to separate permission, transport, registration and app-navigation problems. The [migration guides](/docs/guides/push/migrate) cover OneSignal and direct Firebase integrations, including identity mapping and a gradual rollout.

[Explore all Push resources](/push/resources) or [open Bird](https://app.bird.com).

## Related resources

- [Push notifications](/push-notifications) (product)

[Get an implementation brief](/learn/workspace?topic=push)