Use the Partner Configuration page to tell the Singular attribution tracker which networks and services to work with.
If you are a Singular partner or want to become one, see Information for Partners instead.
The partners in the Partner Configuration page are all the networks and services that you configure to work with Singular's attribution service.
Note: This is not where you tell Singular which sources to pull campaign data from in order to present the data in Singular reports. For that, you need to set up ad networks and other media sources separately in the Data Connectors page (see the Data Connectors FAQ).
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 Partner Settings 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 choose to 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.
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.
Singular integrates with attribution partners by templatizing and standardizing the partners supported postbacks during the integration process. When the Partner Configuration for a partner is saved, Singular creates postbacks from our templates with partners.
Partners can contact us to integrate. In the case where a partner has gone through the process of updating their integration with Singular, they may reach out to ensure you're using the updated postback integration.
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||The name of the partner|
|App||The display name of the app|
|Long Name||The long name or bundle ID of the app|
|OS||The OS of the app (iOS or Android)|
|Click-through attribution lookback window||The lookback window configured for this partner and app site.|
|Postback Type||Install or Event.|
|Events||The name of the event that triggers the postback.|
|Attributed Only||Whether the postback is sent for all events of this type or only if the install has been attributed to the specific partner.|
|Postback URL||The full URL of the postback, including Singular macros.|
Configuring Partner Settings
Partner settings are configured for each app site separately.
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).
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:
|All||Send this partner postbacks about all in-app events|
|Only if install was attributed to...||Only send this partner postbacks about in-app events if the app install was attributed to this partner.|
|Off||Never send this partner postbacks about in-app events.|
Next, add your in-app events as follows:
|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).|
|Send Revenue||For revenue events, include the revenue information in the postback (if you do not check this checkbox, Singular will only send a count of the events).|
Singular's integration team is always working with partners to have the latest and greatest integration with partners and their postbacks.
Occassionally a partner may ask you to update the postback integration that is current being used have configured. Most of the time, updating your integrations with partners is done by re-saving the Partner Configuration screen.
Some integration updates may require more steps, such as if a partner is asking for a new user provided field that didn't exist before. In those cases, the partner or our Singular customer success manager will provide additional instructions.
If you have any questions, please reach out to your Singular customer success manager or firstname.lastname@example.org.
- Adwords: Learn about configuring Adwords as a partner.
- Twitter: Learn about configuring Twitter as a partner.
- Facebook: No special configuration is required. Read more about Facebook attribution.
- Apple Search Ads: Learn about configuring Apple Search Ads.
- Snapchat: Learn about configuring Snapchat.
- Chartboost: Since Chartboost requires receiving postbacks for all installs, you must check the box Send postbacks to Chartboost on all installs in order to save the configuration. Read more about Chartboost.