Before Singular can track installs and events for an ad network, you must configure the network as a partner to receive conversion event data via postback requests. Postback requests are automated notifications sent from Singular to an ad network when a tracked event, such as an install, in-app event, or conversion event occurs.

To do this, navigate to the Attribution > Partner Configuration page and set up the sending of attributed event data in real-time to the network. Once configured, you need to create a tracking link in Manage Links*, which will be used to attribute clicks and impressions (if supported by the partner) through Singular.

*Exceptions:

Web campaigns: Instead of using Manage Links, create a tracking link under Web Links if your only goal is to drive users to web conversions. (For attributing PC and console conversions, please see this guide.)
Custom Advertising Sources: If the source does not require postbacks, use Custom Links to generate your tracking link (e.g., mail, SMS, QR codes, etc.)

Guide for	Project Managers, UA Team
Prerequisites	Singular's attribution service has been enabled for your organization.

Note on Types of Partners

There are 4 types of partners you can configure in the Partner Configuration page:

Non-Self Attributing Partners (e.g., Moloco or ironSource): These are partners that you will work with using Singular tracking links (Singular Links). To configure this type of partner, proceed to Configuration Steps below.
Self-Attributing Networks (SANs): These partners each have a slightly different integration with Singular. To configure them, see the respective guide: Amazon Ads, Apple Search Ads, Facebook Ads, Google Ads (AdWords), Snapchat Ads, and X Ads (formerly Twitter).
Internal BI: This "partner" is just your own BI platform that you want Singular to send automatic postbacks to about installs, re-engagements, and other events. To configure internal BI postbacks, see the Internal BI Postbacks FAQ.
Third-party services (e.g., analytics platforms or fraud analyzing services): Singular is integrated with many third-party services, and you can configure them as partners in the Partner Configuration page so that they receive postback.

Configuration Steps

Select the Partner

In the Singular platform, go to Attribution > Partner Configuration. Find the partner in the list on the left sidebar (you can type the partner name in the filter box to help you find it faster) and click to select.

Tip: If there are certain partners you configure more than others, click the star next to the partner name. Starred partners always appear at the top of the list.

What if the partner isn't listed?

Singular has existing integrations with over 1000 partners, and we keep developing new integrations to cater to our customers' needs.

If you want to run campaigns with a partner that is not integrated with Singular's attribution service, and the partner wants to receive postbacks, ask the partner to get integrated with us. They can learn all about it in the following guides:

If the partner is not listed and is NOT interested in receiving postbacks, you can just run campaigns with that partner by using custom Singular Links.

Edit or Add an App Site Configuration

To edit an existing configuration:

Hover over the app site you want to edit, and click the edit button on the right.

To add a new configuration:

Click Add App Site.
In the Configuration window that opens, select the App for which you want to configure partner settings/postbacks, and then select the App Site (platform version). You configure partners separately per app site.

screenshot-2020.02.09-14_35_34.png

Set Up Conversion Postbacks

The App-Specific Configuration section lets you choose which conversion postbacks (callbacks) you want to send to the partner about this app. Note that Singular always sends postbacks about installs.

Note: The settings differ from partner to partner based on the specific integration they have with Singular. If you're looking for a specific setting and can't find it, we encourage you to discuss your options with the partner.

Enable Re-engagement Postbacks: Check this box to allow Singular to send postbacks about re-engagements (in addition to installs). For more information, see the Re-engagement FAQ.
Include View-Through Attributions: Check this box to allow Singular to send postbacks about conversions stemming from view-through ads (impressions). If you don't check the box, Singular will only send postbacks for click-through attributions.
Send Postbacks to Network on All Installs: Check this box to have Singular send postbacks on any app installs for this app regardless of whether they are attributed to this partner or not.
Postback URL: Enter the URL where the partner wants Singular to send the postback. If you don't have the URL, contact the partner.

Set Up Fraud Postbacks

If the option is supported for the partner, you will also see a checkbox to Enable fraud postbacks.

Fraud postbacks include information about decisions made by Singular's fraud detection system. To learn more, see Fraud Postbacks. Also see Singular Fraud Prevention for an introduction to Singular fraud protection tools.

Set Up Event Postbacks

If you are sending postbacks about conversions to a partner, you can choose whether to also send them postbacks about in-app events.

In-app events can include any events that you have defined and implemented in the SDK (see Defining In-App Events) as well as the predefined events offered by Singular: sessions and revenue events.

Under Send in-app events to <partner>, you have the following options:

Off: Don't send any postbacks to the partner about in-app events.
All: Send this partner postbacks about all events that users trigger in your app, whether the events are attributed to this partner or not.
Only if install was attributed to <partner>: Send event postbacks when the respective install was attributed to this partner

If you choose to send event postbacks to the partner, you have to specify which events to send postbacks for. Add each event to the list as follows:

Field	Meaning
In-app (SDK) event name	The name of the event as it is sent from your app through the Singular SDK integration.
Event Name	The event name or ID as recognized by the partner (the partner would usually have a list of events that it can recognize).
Lookback	Set a lookback window to limit the event postbacks to a specified time frame, e.g., 5 days after the install. If the event occurs after the specified number of days has passed, no postback will be sent. Lookback window options: • Touchpoint: Time frame starts from the ad click/view to which the install was attributed. • Install: Time frame starts from the install. • None: No time limit on event postbacks.
Days	The length of the lookback window in days.
Include Revenue Value	For in-app purchases and other revenue events, check this box to include the revenue amount in the postback.

Note: The SDK event list includes the events __IAP__ and __REVENUE__.

__IAP__ is any in-app purchase event that wasn't given a custom name.
__REVENUE__ includes:
1. All in-app purchase events (__IAP__ + events with custom names, if any).
2. Ad revenue events reported by the SDK (if you have set up ad revenue attribution using the method of sending SDK events).

Selecting to send __REVENUE__ postbacks may cause problems if you have ad revenue events and the network is not set up to receive this type of postback. Before sending ad revenue events, check with the network that it is able to receive ad revenue postbacks.

Partner configuration is one step in setting up Singular Attribution.

More questions about partners and postbacks? See the Partner Configuration FAQ.

How to Configure Partner Settings and Postbacks