Singular sends every partner network a postback when an app install is attributed to that network. You cannot disable these postbacks.

Other types of postbacks are optional and depend on the preferences of the partner network:

• Re-engagement postbacks
• In-app event postbacks
• Postbacks about conversions (installs/re-engagements) and events that are not attributed to the partner

See Postback Server IP Addresses.

• Singular retries sending a postback if we receive an HTTPS response code between 500 and 559.
• The mechanism has a maximum of 5 retries.
• Retries are in intervals of 1, 5, 15, 30, and 60 minutes from the original attempt.

The partners in the Partner Configuration page are all the networks and services that you configure to work with Singular's attribution service.

The Partner Configuration page lets you configure the following things per partner and site:

• The lookback window for click-through attribution
• Which postbacks to send to the partner
• This is also where you enter your login credentials to the partner's platform, if Singular needs them in order to connect to the partner. This varies from partner to partner.

For more details, see Configuring Settings and Postbacks below.

• Some partners are ad networks, ad agencies, etc. You configure attribution settings for these partners, and then you create tracking links that incorporate the partners' custom macros. You can also have Singular send these partners information about attributed installs, fraud decisions etc. in the form of automated postbacks.

• Other partners are third-party BI systems, fraud analyzing services, etc. If you work with such services, you can set them up in the Partner Configuration page so that they can receive postbacks.

"Internal BI" is a special type of partner that you can configure if you want your own internal platform to receive postbacks about attribution decisions, fraud decisions, etc. See Configuring Internal BI Postbacks for more information.

A site (or an app site) is a version of your app developed for a specific platform. You configure partner settings for each app site separately.

For example, if you have an app that runs on Android and on iOS, you have two app sites and you can configure the partner settings for each one.

See also:

• App Configuration FAQ
• Setting Up Your Apps for Attribution Tracking

As part of the process of developing integrations with an attribution partner, Singular creates a postback template that contains all the fields supported by the partner. When you save a new partner configuration, Singular starts creating postbacks based on that template.

To export postback settings for all partners, click Export All on the top right corner of the Partner Configuration page.

To export postback settings for selected partners, first select one or more partners by clicking the checkbox to the left of the partner, and then click Export Selected.

This will download a CSV file with information about each postback that has been configured:

Partner settings are configured for each app site separately.

Singular usually needs certain credentials in order to send postbacks to the partner. Ask the partner for the appropriate credentials.

These are postbacks that notify the partner about a successful re-engagement. The option to enable these postbacks is only available for partners that support re-engagement campaigns (retargeting campaigns).

View-through attributions are attributions determined based on an ad view rather than an ad click. If you run any view-through campaigns, select Include View-Through Attributions in order to have Singular send postbacks to the partner about these attributions as well (otherwise Singular will only send postbacks about click-through attributions).

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's advanced fraud detection methods.

See our Attribution Lookback Window guide.

In-app events are any user events that happen in your app post-conversion. For example, a user who installs your app may then log in or register to your platform, watch the tutorial, or level up if it's a gaming app. Some partners want to receive postbacks about these events from Singular's attribution service.

First, choose which postbacks you want to send:

Next, add your in-app events as follows:

The __REVENUE__ event postback is triggered whenever an in-app purchase is reported, including:

• The system default __iap__ event
• If you are reporting revenue via an SDK/S2S integration with a custom name such as "ProductPurchase".

This means that if you set up postbacks for both __REVENUE__ and __iap__, the partner may receive duplicate postbacks for the same revenue.

We recommend setting up a __REVENUE__ postback and removing the __iap__ postback, unless you have a specific need for it.

Singular's integration team in constant contact with partners to make sure we have the best integration possible. Occasionally a partner may ask you to update the integration, for example, due to changes to how the partner wants to receive postbacks from Singular.

In most cases, you can update the integration by logging into Singular, going to the Partner Configuration page, opening the integration, and re-saving it.

In some rare cases, an update may require more steps, such as providing a new field or setting that didn't exist before. In such cases, the parter or Singular will contact you to provide instructions.