# Mobile Push

Mobile push notifications are messages that appear on a mobile device's screen in real-time, even when users are not actively using the app. To receive push notifications on Android or iOS devices, users must first subscribe or opt-in to push notifications.

## How Is FlareLane's Mobile Push Different?

* With just one line of code, you can build a high-quality push marketing delivery, operation, and analysis environment, **saving time and costs**. 
* We manage your **push tokens** and notification histories, so **there's no need to spend money on building an extensive database**.
* If notification permissions are denied, we **optimize the process by sending users directly to the app settings** to boost re-authorization.
* You can analyze every message in detail, tracking metrics like **click-through rates, purchases, conversion rates, and revenue generated**.
* Clicking a push notification triggers **automatic, optimized handling** based on the URL, whether it's a deep link or a website.
* We provide integrated tools for managing and analyzing API dispatch cases, including **API templates.**
* We provide tools to **manage user fatigue**, such as controlling how often notifications are sent.

***

## What Mobile Push Looks Like

<div align="center"><figure><img src="/files/BqshXulxZhDvbqNBTO3Q" alt="mobile push notification displayed on on iOS" width="375"><figcaption><p><strong>iOS</strong></p></figcaption></figure></div>

<figure><img src="/files/FuFDwJc71sv0f3ADgnGm" alt="mobile push notification displayed on Android" width="375"><figcaption><p><strong>Android</strong></p></figcaption></figure>

<table><thead><tr><th width="276">Type</th><th>Detail</th></tr></thead><tbody><tr><td><strong>Title</strong></td><td>The subject or headline of the push notification</td></tr><tr><td><strong>Message</strong></td><td>(Required) The main content of the message of the push notification</td></tr><tr><td><strong>URL</strong></td><td>The destination URL, such as a deep link or HTTPS address, where users will be directed when they click on the notification.</td></tr><tr><td><strong>Image</strong></td><td>A horizontal or square image to be displayed within the notification.</td></tr><tr><td><strong>Button</strong></td><td>A button to be inserted at the bottom of the push notification.</td></tr><tr><td><strong>Data</strong></td><td>Custom key-value data included in the push notification for additional information.</td></tr></tbody></table>

***

## How Push Notifications Work

### 1. App or Website Subscription

To receive push messages, customers first need to subscribe to push notifications. Upon subscription, the customer's device generates a unique anonymous identifier known as a push token, which is sent to FlareLane. This push token allows FlareLane to identify the recipient's device and send notifications accordingly.

### 2. Delivery of Push Notification

After a push notification is sent, FlareLane uses the push token to identify the device that matches each token and then delivers the notification to the corresponding device.

### 3. Receipt of Push Notification

Once the delivered push notification reaches the device that initially subscribed to your app or website, it is displayed on the device for the recipient to see.

***

## Automatic URL Processing&#x20;

FlareLane automatically handles push notification clicks for URLs starting with the following schemes:

* **http/https:** Opens a web view to load the webpage. If the device supports **app links** or **universal links**, the corresponding app will be launched.
* **Deep links:** If an app with a matching scheme is installed, the app will be launched automatically, and the deep link will be executed.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guide.flarelane.com/channels/mobile-push.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.