At a glance: Find the leading causes and solutions to why your partner isn't receiving expected postbacks. Go through each of the topics below and see if they may be the cause.
Check the integration toggles
Various toggles control different parts of the integration. The state of the toggle could be the reason for not receiving postbacks.
Activate partner is turned off
When the Activate partner toggle is turned off, conversions aren't attributed and postbacks aren't sent to partners.
To activate the integration:
- In AppsFlyer, from the side menu, select Collaborate > Active Integrations.
- Click the Manage integration icon of the partner.
- From the Integration tab, turn on the Activate partner toggle.
Another case may be if the Activate partner toggle is currently turned on but during the time of the event, it was turned off. Use the Audit log to check and see if the partner integration was active at the time of the event:
In-app event postbacks is turned off
The In-app event postbacks toggle is turned off, or it may have been turned off during the time of the event. This means no postbacks are sent.
To turn on In-app event postbacks:
- In AppsFlyer, from the side menu, select Collaborate > Active Integrations.
- Click the Manage integration icon of the partner.
- From the Integration tab, scroll down to the In-app events postbacks toggle and turn it on.
Check the event configuration
The event could be configured in a way that certain postbacks aren't sent.
The event isn't configured
Check that the event is included in the list of in-app events that were configured. If it’s not defined, a postback isn't sent.
- In AppsFlyer, from the side menu, select Collaborate > Active Integrations.
- Click the Manage integration icon of the partner.
- From the Integration tab scroll down to In-app event postbacks and see if the event name appears.
The event is configured incorrectly
Check that the event mapping is correct. Make sure AppsFlyer event (the name of the event as received by AppsFlyer from your mobile app or via S2S) matches the mapped to partner name (the exact event name used by the partner).
The event is configured correctly but with a condition
The event is configured to send postbacks only to the attributed partner
Check to see if the in-app event configuration is set to send postbacks to This partner only or to All media sources, including organic. If it's set to This partner only, only the attributed partner gets the postback.
The event occurred outside of the configuration window
Postbacks are sent according to the postback window setting. Postbacks for events after this period aren't sent to the partner, although the events are still recorded in AppsFlyer.
Note that for SRNs, in-app event postbacks are sent for the duration of the partner data retention period.
The attribution link is configured not to send postbacks for installs
When the attribution link includes the af_installpostback=false parameter, installs are recorded but postbacks aren't sent to the partner.
To view the attribution link:
- In AppsFlyer, from the side menu, select Collaborate > Active Integrations.
- Go to the Attribution link tab and scroll down to see your attribution link.
Privacy restrictions
In the following cases, AppsFlyer doesn't send postbacks due to privacy restrictions.
The partner doesn't support Advanced Privacy or didn't set it up
When Advanced Privacy is turned on but the partner didn't configure Advanced Privacy on their side or they don't support Advanced Privacy, they won't receive Advanced Privacy aggregated postbacks.
Media source restrictions on third-party platforms
Some media sources restrict sharing data with third parties. AppsFlyer doesn't enable the sharing of user-level data acquired through these media sources with any third-party platforms or services. All installs from such media sources are therefore sent as organic. Note that Meta ads doesn't enable the sharing of any data with third-party platforms.
The SDK was set not to share information with the partner
A sharing filter has been implemented in the SDK to prevent the partner from receiving information. This filter may be activated either by a user's explicit opt-out request or at any other point during the app's lifecycle.
For more information see: Prevent data sharing with third parties and setSharingFilterForPartners.
Miscellaneous
The postback was sent but doesn't show on the partner's platform
In some cases, although AppsFlyer sends postbacks to a partner, they aren't showing it on the partner's side. Is such cases, contact the partner.
To see if the postback was sent from AppsFlyer:
- In AppsFlyer, from the side menu, select Reports > Raw Data Export.
- View the relevant report under Postbacks (Installs, In-app events, Retargeting conversions, In-app events retargeting).
The event didn't occur or wasn't sent to AppsFlyer
All events that occurred can be found on the Activity dashboard and in Raw data reports. An event not showing there means it didn’t occur or it wasn't sent to AppsFlyer.
It could be the event wasn't defined in the SDK. In this case, you won't see it on the platform. Check the SDK configuration. defined in the SDK.
If you think the event occurred, check below how to see if it appears in the Activity dashboard or create a Raw data report and look for it there.
To view the Activity dashboard:
- In AppsFlyer, from the side menu, select Analyze > Activity and select the partner and date range.
To create a raw data report:
- In AppsFlyer, from the side menu, select Reports > Raw Data Export.
- Click Create report.
- Select the relevant report.
- Select the date range and any of the necessary fields, and click Create.
- Download the report and look for the event there.
Differences in timezones
There may be discrepancies in receiving postbacks due to a difference in time zones between the AppsFlyer platform and the partner's platform. AppsFlyer dashboards and reports display according to the selected timezone.
To see the app timezone in AppsFlyer:
- In AppsFlyer, from the side menu, select Settings > App settings.
- View the app timezone under Localization.
SRNs missing advertising IDs (IDFA/GAID)
There are a number of specific cases for SRNs in which AppsFlyer doesn't send postbacks for installs, app opens or in-app events.
Media source restrictions on third-party platforms
Some media sources restrict sharing data with third parties. AppsFlyer can't share user-level data acquired through these media sources with any third-party platforms or services. All installs from such media sources are therefore sent as organic. Note that Meta ads doesn't share any data with third-party platforms.