> For the complete documentation index, see [llms.txt](https://help.branch.io/llms.txt).
# MAAS (Powered by Affle)
> Connect MAAS by Affle to Branch for attribution and deep linking on mobile commerce and marketing campaigns.
## Overview
[Affle](http://www.affle.com/) is a Singapore headquartered Mobile Audience as a Service (MAAS) platform company. Affle delivers end-to-end mobile commerce & marketing solutions with greater ROI and transparency for marketers, commerce marketplaces, app developers, and publishers through unique intent insights derived from behavioral signals, attribution and transaction data. Since 2006, Affle has been a pioneer in the field of mobile technology and has built significant scale and intelligence backed by its robust profile data and insights about millions of users growing larger and richer by the day. Affle's investors include Microsoft, D2C (An NTT DoCoMo subsidiary), Itochu, Bennett Coleman & Company Ltd. (BCCL), Centurion Private Equity amongst others.
### Partner Capabilities
| Capability | Details |
| --- | --- |
| Deep Linking | Supported |
| Attribution | • Click-Through Attribution |
| Ad Campaign Types | • Acquisition campaigns
• Retargeting campaigns |
| Ad Formats | Contact support at MAAS (Powered by Affle) for more information. |
| Click Types | • Client-side click |
| Supported Platforms | • iOS
• Android |
| Link Wrapping | Supported |
| Cost Ingestion Support | Supported |
| Cost Ingestion Types | • Click/impression tracking link |
| Pricing Models | • CPI
• CPM
• CPA |
## Before you begin
In order to enable MAAS, you need to have completed the following:
1. Created a [Branch Dashboard](https://dashboard.branch.io/).
2. Have Branch's Performance [product](https://help.branch.io/marketer-hub/products.md) enabled for your Branch Account.
3. Implemented the Branch SDK into your mobile app ([iOS](https://help.branch.io/developer-hub/ios-sdk-overview.md) | [Android](https://help.branch.io/developer-hub/android-sdk-overview.md))
- [Track events](https://help.branch.io/developer-hub/track-branch-events.md)
4. Running campaigns through MAAS.
## Enable MAAS
### 1. Enable MAAS in Branch
In the Branch Dashboard under **Ads** > [**Partner Management**](https://dashboard.branch.io/ads/partner-management), find/search for MAAS. If you're already logged into the Branch Dashboard, you can also click [here](https://dashboard.branch.io/ads/partner-management/a_affle?tab=settings) to go there directly.
Click the **Save & Enable** button.
### 2. Configure Postbacks
> **Note: PAM uses two separate toggles**
>
> The **PAM for Publishers** toggle on the **Postback Config** tab is separate from the PAM switch in your attribution settings. **PAM for Publishers** must be enabled to reconcile conversion events with your partner. To attribute events with PAM, you also need PAM enabled at the org-level or app-level under **Configure** > **App Settings** > **Attribution**. Learn more in our [PAM Overview](https://help.branch.io/marketer-hub/predictive-aggregate-measurement.md#pam-for-publishers).
Enabling MAAS will automatically enable the following postbacks:
- INSTALL
You can configure these postbacks or add more under the [**Postback Config**](https://dashboard.branch.io/ads/partner-management/a_affle?tab=postback) tab.
#### Send All Events
Optionally, you can check the checkbox for a given postback for sending all events. When checked, all events will be sent regardless of attribution. Otherwise, the postback will only fire for events attributed to MAAS.
#### Adding Postbacks
Click the **Add New Postback** button at the bottom of the screen. A modal will appear that will allow you to select an event that you are tracking with the Branch SDKs (including Custom Events).
For more in-depth postback configurations, view our guides:
- [Basic Postback Configuration](https://help.branch.io/marketer-hub/basic-postback-configuration.md)
- [Advanced Postback Configuration](https://help.branch.io/developer-hub/advanced-postback-configuration.md)
- **Recommended** 👍 [Test Postbacks](https://help.branch.io/marketer-hub/testing-postbacks.md)
### 3. Configure Attribution Windows
After configuring your events, navigate to the [**Attribution Windows**](https://dashboard.branch.io/ads/partner-management/a_affle?tab=attribution_windows) tab to set windows by attribution type.
#### Recommended Attribution Windows
| Attribution Type | Window |
| --- | --- |
| click to session start | 90 days |
| click to install | 30 days |
| click to conversion event | 90 days |
| impression to session start | 1 day |
| impression to install | 1 day |
| impression to conversion event | 1 day |
### 4. Create Branch Ad Link
Next, you'll need to create a Branch Ad Link for your MAAS campaigns in order for Branch to properly attribute conversions.
[Create Ad Links](https://help.branch.io/marketer-hub/ad-links.md)
The Branch Ad Link you create will be placed in your MAAS campaign.
### 5. Verify Data in Branch
After launching your Clinch campaigns, and conversions begin to happen, you'll want to verify data is being sent from Branch to Clinch. You can look at the [Branch Dashboard's Liveview Webhook Records](https://dashboard.branch.io/liveview/webhooks) and apply the following filter:
| Filter | Operator | Value |
| --- | --- | --- |
| ad partner (3p) | equals | `a_affle` |
Once applied, data should flow through the Liveview, and you can see the data being sent to MAAS from Branch.