> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/development-guide/android/android-push-message-setup/android-push-message-integration.md).

# Push Message Integration

Integrate Firebase with the Hackle SDK to receive Hackle Push Messages in your Android app.

{% stepper %}
{% step %}
**Integrate Firebase Project**

To use Push Messages in an Android app, you need to configure the integration between the Hackle Workspace and a Firebase project.

{% content-ref url="/pages/EnrApWvzWfZ7innLv6Le" %}
[Android FCM Integration](https://docs.hackle.io/en/external-link/crm-channels/fcm-integration.md)
{% endcontent-ref %}
{% endstep %}

{% step %}
**Integrate Firebase Cloud Messaging SDK**

Complete the Android app setup by following the [Firebase Cloud Messaging Installation Guide](https://firebase.google.com/docs/cloud-messaging/android/client).
{% endstep %}

{% step %}
**Integrate with Hackle SDK**

Follow [SDK Integration](https://docs.hackle.io/en/development-guide/android.md) to add the Hackle SDK dependency and initialize the SDK.

The push token is automatically registered when the app is built and launched.

{% hint style="info" %}
Once the SDK integration is complete, push token collection, push reception, and push click handling are automatically enabled.
{% endhint %}
{% endstep %}

{% step %}
**Test Push Messages**

**Check Token**

* Use the [User Identifier guide](https://docs.hackle.io/en/development-guide/android/android-user-explorer.md) to check the token configured on the Android device.
* Use the [User Profile guide](https://docs.hackle.io/en/user-view/user-profile.md) to check the Android push token assigned to a specific user.

**Test Send**

* Follow the [Push Message test send guide](https://docs.hackle.io/en/crm-marketing/push-message-guide/create-campaign.md#id-3-1) to verify Push Messages on an Android device.
  {% endstep %}

{% step %}
**Push Message Reception**

When a push is received, an icon is displayed in the status bar and notification center.

* On Samsung Galaxy Android smartphones, the app icon is displayed.
* On standard Android smartphones or simulators, a white circle icon is displayed.
* If you have customized the push icon, the changed icon is displayed.
  {% endstep %}
  {% endstepper %}

## Deep Link Navigation

For handling links when a Push Message is clicked, see [Deep Links](https://docs.hackle.io/en/development-guide/android/android-deeplink.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hackle.io/en/development-guide/android/android-push-message-setup/android-push-message-integration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
