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

# Enable Mobupps (New)

> Connect Mobupps to Branch to attribute clicks and installs on performance and real-time bidding campaigns.

## Overview

[Mobupps](https://mobupps.com/) is an Israel-based mobile advertising company that provides performance-based user acquisition, programmatic, and real-time bidding services. Connect Mobupps 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 Mobupps in the [new Branch experience](https://help.branch.io/marketer-hub/new-branch-overview.md). For information on Mobupps in legacy Branch, visit our [legacy guide](https://help.branch.io/marketer-hub/mobupps.md).

### Partner capabilities

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

## Before you begin

To set up the Mobupps 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 Mobupps account with admin access.
- [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 Mobupps

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

Mobupps doesn't require credentials to activate. The integration is enabled automatically when you select **Enable Mobupps** on the Mobupps page.

## Configure attribution

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

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

| Attribution type | Default | Mobupps'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 Mobupps automatically activates postbacks for `INSTALL`. The default postback URL template is:

```
http://wmadv.go2cloud.org/aff_lsr?transaction_id=${ (last_attributed_touch_data.~click_id)! }&android_id=${ (user_data.android_id)! }&google_aid=${ (user_data.aaid)! }&ios_ifa=${ (user_data.idfa)! }&adv_sub5=${ (name)! }&adv_sub4=${ (user_data.language)! }&adv_sub3=${(app_id)!}&country_code=${ (user_data.geo_country_code)! }&customer_id=${(organization_id)!}&time=<@urlencode><@dateformat output_date_format="TIMESTAMP_SECONDS">${install_activity.timestamp}</@dateformat></@urlencode>&revenue=${ (event_data.revenue)! }&ip=${ (user_data.ip)! }&device_os=${ (user_data.os)! }&device_os_version=${ (user_data.os_version)! }&user_id=${ (user_data.developer_identity)! }
```

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 Mobupps 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 = Mobupps`.
- **In Mobupps**: confirm that forwarded events are appearing in your Mobupps attribution reporting.

## Data mappings

### Campaign data

Branch populates the following fields from Mobupps campaign data.

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