> ## Documentation Index
> Fetch the complete documentation index at: https://moengage.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Singular

> Import paid install attribution data from Singular into MoEngage to power lifecycle campaigns, segmentation, and acquisition analytics.

## Introduction

[Singular](https://www.singular.net/) is a unified marketing analytics platform that delivers attribution, cost aggregation, marketing analytics, creative reporting, and workflow automation.

## MoEngage × Singular

The MoEngage and Singular integration allows you to import paid install attribution data from Singular into MoEngage to use intelligently within your campaigns.

## Integration

<Info>
  **Prerequisites**

  * Ensure you have an active Singular account.
  * Ensure you have access to the **Settings** section on your MoEngage dashboard.
</Info>

Follow these setup instructions to turn on the Singular integration and send callbacks to MoEngage.

### Step 1: Get the MoEngage attribution tracking app key

1. Navigate to **Settings** > **Analytics** > **Acquisition tracking** in the MoEngage Dashboard.
2. Turn on **Acquisition Tracking**, and select **Singular** from the dropdown. This generates an **App Key**.
   <img src="https://mintcdn.com/moengage/7iGV38YjgdBKSU0B/images/partner_22025549296020.png?fit=max&auto=format&n=7iGV38YjgdBKSU0B&q=85&s=7a49f7505896192f90abc433662129b9" alt="Acquisition Tracking settings with Singular selected and App Key generated" width="1110" height="752" data-path="images/partner_22025549296020.png" />
3. Click **Save**.
4. Copy the **App Key**. You will need it to configure MoEngage on Singular.

### Step 2: Configure MoEngage on Singular

On your Singular dashboard, follow these steps:

1. Navigate to **Attribution** > **Partner Configuration**.
2. Start typing the partner's name (`MoEngage_Partner`), and select **MoEngage** from the list.
3. In the Configuration window, select the **App** you want to configure, and then select **App Site** (platform version).
4. Select the following checkboxes:
   * **Send Postbacks to Network on All Installs**
   * **Send Event Postbacks on any app installs for this app**
     <img src="https://mintcdn.com/moengage/pjxkCVVFj_C6dGcn/images/partner_8998442096532.png?fit=max&auto=format&n=pjxkCVVFj_C6dGcn&q=85&s=8676a91bf707ac1b29c1be02c0686244" alt="MoEngage partner configuration with postback checkboxes enabled in Singular" width="1386" height="932" data-path="images/partner_8998442096532.png" />
5. Enter the following details regarding your MoEngage app:
   | Field       | Description                                                                                                                                                                  |
   | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   | **App ID**  | Workspace ID of your MoEngage account. You can find this by navigating to **Settings** > **Account** > **APIs** > **API keys**.                                              |
   | **App Key** | Acquisition tracking key of your MoEngage account. This is the key that you copied in the previous step.                                                                     |
   | **Region**  | Region of your MoEngage data cluster. For details, refer to [Data Centers in MoEngage](https://www.moengage.com/docs/user-guide/data/key-concepts/data-centers-in-moengage). |
6. Click **Save**.

## How to use the acquisition data in MoEngage

After MoEngage starts receiving data from Singular, you can leverage this data in the following ways.

### User attributes

MoEngage tracks two user attributes: **Campaign Name** and **Publisher Name**. You can use these attributes in your campaigns, segmentation, and analytics. The Publisher Name and Campaign Name of install give you added insight into the persona of the user. You can leverage this data to enhance your onboarding campaigns and user funnels, and to personalize your marketing automation activities on MoEngage. The next sections list a few popular use cases for leveraging this data.

<img src="https://mintcdn.com/moengage/syqICryKE0qygh49/images/partner_19899387367572.png?fit=max&auto=format&n=syqICryKE0qygh49&q=85&s=25b5d27f651af809fdb54a79cd41f6b9" alt="Campaign Name and Publisher Name user attributes in MoEngage" width="410" height="231" data-path="images/partner_19899387367572.png" />

### Analyze the performance of different publishers

The Singular integration helps you analyze the effectiveness of your app install campaigns and sources in MoEngage. Using data already tracked in MoEngage—user events, conversion goals, and uninstalls—you can compare the performance of different app install campaigns and analyze the relative performance of installs from different publishers to optimize your marketing spend.

To analyze this data, view the [MoEngage acquisition dashboard](https://app.moengage.com/v3/#/acquisition).

<img src="https://mintcdn.com/moengage/V7W8fvZbxtTmKTAn/images/partner_11286820226452.png?fit=max&auto=format&n=V7W8fvZbxtTmKTAn&q=85&s=eede4b141661ac63245820c1d25f3acf" alt="Acquisition analysis dashboard grouped by publisher" width="1351" height="338" data-path="images/partner_11286820226452.png" />

If you use MoEngage Analytics, you can also leverage the Publisher Name and Campaign Name information of installs to analyze your user funnels.

### Analyze the performance of different campaigns

After the integration is enabled, you can also view your acquisition data analysis on the acquisition dashboard by navigating to **Analyze** > **Acquisitions** in the dashboard sidebar.

<img src="https://mintcdn.com/moengage/syqICryKE0qygh49/images/partner_19899387369108.png?fit=max&auto=format&n=syqICryKE0qygh49&q=85&s=8f36436240d0c8b7d0d124e9b7be72fd" alt="Acquisition analytics dashboard grouped by campaign" width="1199" height="354" data-path="images/partner_19899387369108.png" />

### Enhanced onboarding campaigns

You can use the Publisher Name and Campaign Name of install—available as user properties in MoEngage—to create segments and personalize the push notifications, in-app messages, emails, and SMS that you send through MoEngage.

Install attribution data gives you an insight into how users could progress in their lifecycle right when they install the app. This is a very useful piece of information and can help you enhance the performance of your onboarding campaigns by improving retention, reducing the time to first conversion, and driving a higher LTV per user.

| Publisher category                                 | Use case                                                                                                                                                    |
| -------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Publishers where average sessions per user are low | Send push notifications periodically to increase the average number of sessions per user, right from the time users install the app.                        |
| Publishers where average LTV is high               | These are your potential premium users. Implement a campaign strategy to nurture them into your premium-user segment.                                       |
| Publishers where the uninstall rate is high        | Identify users with a higher propensity to churn immediately after install, and incentivize them to make a first purchase—which can reduce your churn rate. |

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="Can I see the install data from Facebook in MoEngage?">
    According to Facebook data sharing policies, install data from Facebook can only be viewed in Singular and not sent to other platforms. These appear as **Organic Installs** in MoEngage. You can alternatively use the MoEngage APIs to send Facebook install data to MoEngage separately.
  </Accordion>
</AccordionGroup>
