If a partner network says they are not receiving postbacks for installs/conversions or in-app events:

1. Go to Attribution > Export Logs and download the postbacks logs for the partner. For help downloading logs, see the Export Logs and User-Level Data FAQ.

• Make sure to filter the postbacks with Response HTTP Code = 200. If the Response HTTP Code is "200", it means that the partner confirmed that they received the postback. 
• Also select the field Response HTTP Body as it may help pinpoint a tech issue at the partner's end. 
• Share the log with the partner to validate the data internally. If there are many postbacks with other response codes, inform them that there might be a technical issue with them receiving postbacks from Singular.

Some possible reasons are:

• Lookback windows: One or more events may have a different lookback window configured for postbacks. Check the settings in the Partner Configuration page.
• Technical issues: The partner may not have received one or more postbacks due to technical issues on the partner's end. To check, see Why is my network partner not receiving postbacks?
• Duplicate events: The Singular SDK in your app auto-generates an event called __REVENUE__, which is triggered on any in-app purchase. In addition, you can also create your own SDK revenue events for different types of in-app purchases. When you configure event postbacks, make sure to send postbacks either for __REVENUE__ or for your custom-named revenue event(s) - but not both. Otherwise, Singular will send two postbacks for each in-app purchase.

If a network partner says they are receiving postbacks without event attributes:

1. Go to Attribution > Export Logs and download the postbacks logs for the partner. Check the postback HTTP Body or Target URL fields to see if they include event attributes. For help downloading logs, see the Export Logs and User-Level Data FAQ.
2. If the logs show that postbacks are indeed being sent without event attributes, double-check the postback settings in the Partner Configuration page. If you have not configured added attributes to be sent along with events, change the settings now.
3. If the settings are correct and postbacks are still being sent with missing attributes, contact Singular support.

If your billing with a network is based on the number of install/event postbacks that Singular has sent to them during the period, you can double-check what postbacks were sent to a partner by downloading raw postback logs at Attribution > Export Logs.

For general help with the Export Logs page, see the Export Logs and User-Level Data FAQ.

For postback validation, we recommend downloading a log with the following settings:

Be sure to filter for the value "200" in Response HTTP Code to see the postbacks successfully received by the Postback Recipient.

Don't get confused between the Partner and Postback Recipient fields:

• Partner is the network to which the event was attributed.
• Postback Recipient is the partner that received the postback for the event. The event is not necessarily attributed to that partner (remember, some partners ask to receive postbacks on all of your events, whether they are attributed to that partner or another network, and you can enable that option in the Partner Configuration page).

An additional field, Is Attributed, further clarifies whether the postback recipient is the network to which the event was attributed ("Y" means it's the same network, "N" means the event was attributed to another partner which you can see in the Partner field).

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 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 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 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.

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 downloads a CSV file with information about each postback that has been configured:

See above.

Partner settings are configured for each app site separately.

Singular usually requires certain credentials 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 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 The Attribution Lookback Window.

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:

In the In-App (SDK) Events dropdown, you will see several different revenue-related events, some of which are overlapping.

To prevent duplicate postbacks being sent for the same in-app event follow the instructions below.

What to do if you have only in-app purchase revenue:

• Set up mappings for __IAP__  and any custom purchase events.
• Or, alternatively, use __REVENUE__, which encompasses all your in-app purchase events.

What do do if you have both in-app purchase revenue and ad revenue:

• Set up mappings for __IAP__, any custom purchase events, and __ADMON_USER_LEVEL_REVENUE__.
• We don't recommend using the general event __REVENUE__ in this case, as it includes both purchases and ad revenue events, and mapping both types of revenue to the same revenue event on the network side may cause problems.
• Instead, map in-app purchase events to the network's purchase event, and the __ADMON_USER_LEVEL_REVENUE__ event to the network's admon or ad revenue event.
• If you're not sure what events to use on the network's side, contact the network for details.

Singular's integration team is in constant contact with partners to ensure 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.

No. Although partner configuration settings may appear similar, each configuration is uniquely integrated within Singular. It is not possible at this time to update multiple configurations at the same time.