> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-developer-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-developer-guide/netmera-onboarding/onboarding-integrations.md).

# Onboarding Integrations

**Onboarding Integrations** is the starting point for connecting your application to Netmera. Use this page to create integrations for **Android, iOS, Huawei, and Web**, provide the platform-specific configuration required by the push notification provider, and access the SDK integration steps.

A separate integration can be created for each platform. After the required configuration is completed and the SDK is initialized in the application, the integration appears on the Onboarding Integrations page with its setup progress and last update date.

**Path:** `Developers > Onboarding > Onboarding Integrations`

<figure><img src="/files/AazTFHQGjv1QOENU9Vkg" alt=""><figcaption></figcaption></figure>

### Integration Overview

The Onboarding Integrations page lists the integrations created for the current app.

Each integration card displays:

* **App name** — The name assigned to the integration.
* **Platform** — Android, iOS, Huawei, or Web.
* **Setup progress** — Indicates how much of the integration setup has been completed.
* **Updated** — Shows the date when the integration was last updated.
* **More options** — Provides actions for managing the integration.

An integration with a completed setup is shown with a full progress bar and completion indicator. Integrations that still require configuration display the remaining setup progress.

Select **+ Create Integration** to add a new platform integration.

### Create an Integration

Creating an integration consists of up to three stages:

1. **App Details** — Select the platform and provide the application's identity information.
2. **Platform Configuration** — Provide the credentials or configuration file required by the selected platform.
3. **Integrate & Initialize** — Add the Netmera SDK to the application and initialize it.

The second stage varies depending on the selected platform.

<figure><img src="/files/Lx4rPHuNy58WNWSVIiLD" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="114.2890625">Platform</th><th width="228.10546875">App Details</th><th>Platform Configuration</th><th>Final Step</th></tr></thead><tbody><tr><td><strong>Android</strong></td><td>App Name, Package Name</td><td>Firebase Configuration</td><td>Integrate &#x26; Initialize</td></tr><tr><td><strong>iOS</strong></td><td>App Name, Bundle ID</td><td>APNS Certificate</td><td>Integrate &#x26; Initialize</td></tr><tr><td><strong>Huawei</strong></td><td>App Name, Package Name</td><td>HMS Configuration</td><td>Integrate &#x26; Initialize</td></tr><tr><td><strong>Web</strong></td><td>App Name and web application details</td><td>Web-specific setup</td><td>Integrate &#x26; Initialize</td></tr></tbody></table>

> The platform configuration is required to establish the connection between Netmera and the push notification service used by the application.

### Android Integration

The Android integration uses **Firebase Cloud Messaging (FCM)** for push notification delivery. The setup consists of:

1. App Details
2. Firebase Configuration
3. Integrate & Initialize

#### Step 1: App Details

Select **Android** and enter:

* **App Name**
* **Package Name**

The package name should correspond to the Android application's package identifier. Select **Next** to continue.

<figure><img src="/files/rhBlhD68UdtUzQT0eF3L" alt="" width="563"><figcaption></figcaption></figure>

#### Step 2: Firebase Configuration

The **Firebase Configuration** step connects the Netmera integration to the Firebase project associated with the Android application.

#### Configuration file

Upload the Firebase configuration file generated for the application:

```
google-services.json
```

Select **Upload google-services.json** and upload the configuration file. After the file is selected, its filename is displayed below the upload area.

<figure><img src="/files/rMiSrjrw2idMJRi7sBvv" alt="" width="563"><figcaption></figcaption></figure>

#### Why the Firebase configuration is required

The `google-services.json` file contains the Firebase project and application configuration required to establish the FCM connection. Make sure that the file belongs to the same Firebase application as the Android package name entered in the previous step.

> Do not upload a configuration file from another Android application or Firebase project. The Firebase application configuration should correspond to the package name of the application being integrated.

#### Step 3: Integrate & Initialize

Retrieve the API key required to integrate and initialize Android. Then follow the [SDK Integration](/netmera-developer-guide/platforms/android/sdk-integration.md) guide.

<figure><img src="/files/MpMTZ7hk1ZQJuaUIhGZB" alt="" width="563"><figcaption></figcaption></figure>

### iOS Integration

The iOS integration uses **Apple Push Notification service (APNs)** to deliver push notifications to iOS devices. The setup consists of:

1. App Details
2. APNS Certificate
3. Integrate & Initialize

#### Step 1: App Details

Select **iOS** and enter:

* **App Name**
* **Bundle ID**

The Bundle ID must match the Bundle ID configured for the iOS application.

<figure><img src="/files/dbjGjh1hb1YB8XBud9BZ" alt="" width="563"><figcaption></figcaption></figure>

#### Step 2: APNS Certificate

The **APNS Certificate** step provides Netmera with the credentials required to communicate with APNs. Netmera supports two certificate types:

* **p8**
* **p12**

It is sufficient to configure **one iOS p8 certificate or one of the iOS p12 certificates**.

#### Using a p8 Certificate

When **p8** is selected, provide the following information:

<figure><img src="/files/14roujGXm86rqZK8J8sk" alt="" width="563"><figcaption></figcaption></figure>

<table><thead><tr><th width="138.8203125">Field</th><th>Description</th></tr></thead><tbody><tr><td><strong>APNS Certificate</strong></td><td>Upload the APNs authentication key with the <code>.p8</code> extension.</td></tr><tr><td><strong>Team ID</strong></td><td>The Apple Developer Team ID associated with the application.</td></tr><tr><td><strong>Key ID</strong></td><td>The Key ID associated with the uploaded APNs authentication key.</td></tr><tr><td><strong>Environment</strong></td><td>Select the APNs environment: <strong>Prod</strong> or <strong>Dev</strong>.</td></tr></tbody></table>

#### Using a p12 Certificate

If **p12** is selected as the certificate type, provide the required p12 certificate information requested by the form. The p12 certificate should belong to the same iOS application identified by the Bundle ID.

Make sure that the certificate is valid and configured for the appropriate APNs environment before uploading it.

<figure><img src="/files/OW0dgCd6yrWbUEdGCsO8" alt="" width="563"><figcaption></figcaption></figure>

> Use a certificate that corresponds to the application and environment being integrated. An invalid, expired, or mismatched APNs certificate can prevent push notifications from being delivered.

#### Environment

Select the APNs environment:

* **Prod** — Use for the production application environment.
* **Dev** — Use for development/testing environments.

The selected environment determines which APNs environment Netmera uses for push delivery.

#### Step 3: Integrate & Initialize

Retrieve the API key required to integrate and initialize iOS. Then follow the [SDK Integration](/netmera-developer-guide/platforms/ios/new-ios-swift/sdk-integration.md) guide.

<figure><img src="/files/ikOZ14cy2kBlYp4c9yCO" alt="" width="563"><figcaption></figcaption></figure>

### Huawei Integration

The Huawei integration is intended for applications using **Huawei Mobile Services (HMS)**. The setup consists of:

1. App Details
2. HMS Configuration
3. Integrate & Initialize

#### Step 1: App Details

Select **Huawei** and enter:

* **App Name**
* **Package Name**

The package name should match the package identifier configured for the Huawei application. Select **Next** to continue.

<figure><img src="/files/iez8NmXfgv5M0en1CVeK" alt="" width="563"><figcaption></figcaption></figure>

#### Step 2: HMS Configuration

The **HMS Configuration** step connects the Netmera integration to the Huawei application.

<figure><img src="/files/v5JB39KLtkYtsP3kupWz" alt="" width="563"><figcaption></figcaption></figure>

#### HMS App ID

Enter the **HMS App ID** assigned to the application in Huawei's developer environment. The HMS App ID identifies the Huawei application that Netmera will use for push notification delivery. For example:

```
111467890
```

The value must correspond to the Huawei application being integrated.

#### Step 3: Integrate & Initialize

Retrieve the API key required to integrate and initialize Huawei. Then follow the [SDK Integration](/netmera-developer-guide/platforms/android/sdk-integration/huawei-integration.md) guide.

<figure><img src="/files/dunl8NONkOcYYnxslpZX" alt="" width="563"><figcaption></figcaption></figure>

### Web Integration

The **Web** integration connects a website to Netmera and enables web-based customer engagement capabilities, including **web push notifications, user tracking, session tracking, and web analytics**.

Unlike Android, iOS, and Huawei integrations, the Web setup does not require a mobile push provider configuration file. Instead, the integration provides the **Netmera API key, JavaScript code, required service worker files, and web push configuration** that must be added to the website.

The Web onboarding flow consists of the following steps:

1. **App Details** — Define the website and its identity.
2. **Core SDK Setup** — Add the Netmera SDK to the website and configure tracking options.
3. **Push Notifications** — Configure web push and VAPID keys.
4. **Safari Push** — Configure push support for Safari.
5. **Permission Prompt** — Configure the browser permission prompt.

> The available configuration and setup requirements may vary depending on the web push capabilities being enabled.

For setup instructions, see [Web Integration](#web-integration).

### Editing an Integration

Existing integrations can be updated from the **Onboarding Integrations** page.

Open the **More options** menu on the integration card and select the edit option.

The edit flow uses the same multi-step structure as creation:

1. **App Details**
2. **Platform Configuration**
3. **Integrate & Initialize**

The existing configuration is displayed so that required values can be updated without creating a new integration.

For example:

* Android integrations open the **Firebase Configuration** step.
* iOS integrations open the **APNS Certificate** step.
* Huawei integrations open the **HMS Configuration** step.

<figure><img src="/files/zud2B8tgm0zMke6Tsreq" alt="" width="563"><figcaption></figcaption></figure>

### Integration Status

The progress indicator on each integration card provides a quick view of the onboarding status.

#### Incomplete integration

An integration with a partially completed progress bar still has configuration or implementation steps remaining.

For example, an Android integration may have its app details configured while the Firebase configuration or SDK initialization is still incomplete.

<figure><img src="/files/b6LEVeIpu6uMsXuE0KhF" alt="" width="563"><figcaption></figcaption></figure>

#### Completed integration

A completed integration displays:

* A full progress bar
* A completion indicator
* The latest update date

<figure><img src="/files/cSVnanatCWpi4q7FgFVy" alt="" width="563"><figcaption></figcaption></figure>

This indicates that the onboarding flow has been completed from the Netmera panel.

> Completing the onboarding flow in Netmera does not replace the required SDK implementation in the application. The application must also include and initialize the appropriate SDK for the integration to function correctly.

### Platform Configuration Summary

<table><thead><tr><th width="124.2109375">Platform</th><th>Required Application Identifier</th><th>Provider Configuration</th><th>Main Configuration</th></tr></thead><tbody><tr><td><strong>Android</strong></td><td>Package Name</td><td>Firebase / FCM</td><td><code>google-services.json</code></td></tr><tr><td><strong>iOS</strong></td><td>Bundle ID</td><td>APNs</td><td><code>.p8</code> or <code>.p12</code> certificate</td></tr><tr><td><strong>Huawei</strong></td><td>Package Name</td><td>HMS</td><td>HMS App ID</td></tr><tr><td><strong>Web</strong></td><td>Web application details</td><td>Web push configuration</td><td>Web integration setup</td></tr></tbody></table>

### Recommended Setup Flow

For a new application, complete the integration in the following order:

1. Open **APP > Onboarding Integrations**.
2. Select **+ Create Integration**.
3. Select the application platform.
4. Enter the application name.
5. Enter the platform-specific application identifier:
   * Package Name for Android/Huawei
   * Bundle ID for iOS
   * Web application information for Web
6. Select **Next**.
7. Complete the platform-specific configuration:
   * Upload `google-services.json` for Android.
   * Configure the APNs certificate for iOS.
   * Enter the HMS App ID for Huawei.
   * Complete the Web configuration for Web.
8. Select **Next**.
9. Follow the **Integrate & Initialize** instructions.
10. Add the appropriate Netmera SDK or integration code to the application.
11. Initialize Netmera in the application.
12. Return to **Onboarding Integrations** and verify that the integration shows as completed.

### Important Considerations

* **Use matching application identifiers.** The Package Name or Bundle ID entered in Netmera should correspond to the application being integrated.
* **Use the correct provider configuration.** Android requires the Firebase configuration associated with the Android app; iOS requires valid APNs credentials; Huawei requires the corresponding HMS App ID.
* **Keep credentials consistent.** For APNs p8 authentication, the Team ID, Key ID, and uploaded key must belong to the same Apple Developer configuration.
* **Select the correct APNs environment.** Use **Dev** for development environments and **Prod** for production environments.
* **Complete both panel and application setup.** Creating an integration only configures the Netmera side. The corresponding SDK must also be added and initialized in the application.
* **Update existing integrations when credentials change.** A new integration does not need to be created simply because provider credentials or configuration files have changed. Use the existing integration's edit flow where applicable.


---

# 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 dynamically by asking a question.

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

```
GET https://user.netmera.com/netmera-developer-guide/netmera-onboarding/onboarding-integrations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.