> For the complete documentation index, see [llms.txt](https://help.branch.io/llms.txt).

# Enable Mobusi (New)

> Connect Mobusi to Branch to attribute clicks and installs on performance-based user acquisition campaigns.

## Overview

[Mobusi](https://www.fibonad.com/) is a Spain-based mobile advertising network offering performance-based user acquisition and app monetization, part of the Fibonad group. Connect Mobusi to Branch to attribute clicks and installs and configure Postbacks.

For more information about integrating ad partners in general, visit our [Ad Partner Integration Guide](https://help.branch.io/marketer-hub/ad-partner-integration-guide-new.md).

> **Note: this guide is for new Branch**
>
> Please note that this guide is about integrating Mobusi in the [new Branch experience](https://help.branch.io/marketer-hub/new-branch-overview.md). For information on Mobusi in legacy Branch, visit our [legacy guide](https://help.branch.io/marketer-hub/mobusi.md).

### Partner capabilities

| Capability | Details |
| --- | --- |
| Company type | Ad network, DSP, exchange |
| Deep linking | Supported |
| Attribution | Click-through attribution, View-through attribution |
| Ad campaign types | Acquisition campaigns, Retargeting campaigns |
| Ad formats | Contact Mobusi for details. |
| Click types | Client-side click |
| Supported platforms | iOS, Android |
| Link wrapping | Not supported |
| Cost ingestion support | Not supported |
| Pricing models | CPI, CPC, CPM, CPA |

## Before you begin

To set up the Mobusi integration, you need:

- Ad partner integrations enabled for your Branch account. Availability varies by Branch plan. See [Branch pricing](https://www.branch.io/pricing/) or contact your Branch representative.
- A Branch account with access to **Configuration > Ad Partners** and admin permissions to enable and configure integrations.
- A Mobusi account with admin access. You'll need the following credential, available from your Mobusi account manager: Mobusi Service ID.
- [PAM](https://help.branch.io/marketer-hub/predictive-aggregate-measurement.md) enabled (recommended).

> **Note: PAM uses two separate toggles**
>
> The **PAM for Publishers** toggle for this partner, found under **Partner settings** > **Manage account**, is separate from the account-level **PAM switch**. **PAM for Publishers** must be enabled to reconcile conversion events with your partner. To attribute events with PAM, you also need PAM enabled on the [Attribution page](https://help.branch.io/account-hub/attribution-page-new.md) under **Configuration** > **Attribution**. Learn more in our [PAM Overview](https://help.branch.io/marketer-hub/predictive-aggregate-measurement.md#pam-for-publishers).

## Enable Mobusi

To begin, navigate to **Configuration > Ad Partners > Mobusi**.

Enter your **Mobusi Service ID**, then select **Enable Mobusi** on the Mobusi page. Contact your Mobusi account manager if you need this value.

## Configure attribution

To configure attribution windows, select the **Attribution windows** tab on the Mobusi page.

To minimize discrepancies when comparing Branch and Mobusi reporting, match your Branch attribution windows to the settings in your Mobusi account.

| Attribution type | Default | Mobusi's recommendation |
| --- | --- | --- |
| Click to start session | 1 day | 90 days |
| Click to install | 7 days | 30 days |
| Click to conversion event | 30 days | 90 days |
| Impression to start session | 1 day | 1 day |
| Impression to install | 1 day | 1 day |
| Impression to conversion event | 7 days | 1 day |
| Deep linking duration | 120 minutes | — |

For more information, follow [Configure attribution](https://help.branch.io/marketer-hub/ad-partner-integration-guide-new.md#configure-attribution) in the general [Ad Partner Integration Guide](https://help.branch.io/marketer-hub/ad-partner-integration-guide-new.md).

## Configure postbacks

Enabling Mobusi automatically activates postbacks for `INSTALL` and `OPEN`. The default postback URL template is:

```
http://pixel.leadzu.com/pixel.php?service=${ (ad_network.credentials.service_id)! }&hash=${ (last_attributed_touch_data.~click_id)! }&type=EVENT&transaction_id=${ (id)! }&id_event=${ (ad_network.goal_ids["OPEN"])! }
```

To add postbacks for additional events or to customize behavior, follow [Configure postbacks](https://help.branch.io/marketer-hub/ad-partner-integration-guide-new.md#configure-postbacks) in the general [Ad Partner Integration Guide](https://help.branch.io/marketer-hub/ad-partner-integration-guide-new.md).

## Create a Branch Ad Link

Create a Branch Ad Link to use in your Mobusi campaigns. Branch uses the link to attribute clicks and deep link users into your app.

Follow [Create Ad Links](https://help.branch.io/marketer-hub/ad-links-new.md).

## Verify your data

After your integration is connected and events are flowing, you can verify data is reaching Branch:

- **In Branch** [**Liveview**](https://app.branch.io/testing-and-monitoring/events): confirm that events from your app appear in real time. This is the fastest way to confirm SDK events are firing.
- **In Branch** [**Analysis dashboards**](https://help.branch.io/marketer-hub/analysis-data-sources-new.md): review attributed installs and events where `Ad Partner Name = Mobusi`.
- **In Mobusi**: confirm that forwarded events are appearing in your Mobusi attribution reporting.

## Data mappings

### Campaign data

Branch populates the following fields from Mobusi campaign data.

| Branch field | Partner data |
| --- | --- |
| `~advertising_partner_name` | `"Mobusi"` (static) |