Before Singular can track installs and events for an ad network, you need to set up that network as a partner in the Attribution > Partner Configuration page. This is where you set up real-time postbacks (also known as callbacks) to let the partner know about installs and other events.
Remember that Partner configuration is a separate process from setting up a data connector for a network. A data connector pulls data from a network so you can analyze the information in Singular. Partner configuration sets up attribution tracking settings and postbacks.
|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., Vungle 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: Twitter Ads, Apple Search Ads, Facebook Ads, Google Ads (AdWords), Snapchat Ads.
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., BI systems 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.
Find the Partner
In the Singular web app, go to Attribution > Partner Configuration. Start typing the partner's name in the Search Partners text box and select it from 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.
Select an App
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.
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.
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:
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:
Note: The SDK event list includes the events __IAP__ and __REVENUE__.
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.