Attributing app installs to their rightful advertising source is one of the key features of Attribution Analytics. Setting up your Attribution Analytics account to accurately measure installs and notify your advertising partners (publishers) and any third-party analytic providers is an integral step in using Attribution Analytics to its fullest capabilities.
If partners or third-party analytic providers do not receive install notifications, then you can try the following steps to troubleshoot, isolate, and resolve the issue.
First, log in to Attribution Analytics and make sure that a postback URL has been set up for the partner/third-party in question. If you have multiple traffic sources, then configure or verify the postback URLs for each one (perhaps one of the configurations is not set up properly). For information about adding a postback URL, visit Setting Up Postback URLs.
Is the postback URL set up for the “Install” event?
If an advertiser sets up a postback URL for notification of in-app events (instead of the install event), then change it to the install event and notify the advertiser that the partner optimizes on install events and not other events.
Is “Partner” set to the correct partner and “Only send data attributed to PartnerXYZ” checked?
When using a custom postback template for an integrated partner, Attribution Analytics always defaults to “Partner:PartnerXYZ” and “Only send data attributed to PartnerXYZ“. If you’re not using the postback template, then make sure you select the partner from the “Partner” drop-down list.
Only deselect “Only send data attributed to PartnerXYZ” when the postback URL is for a third-party analytic system, or for a partner who is setup to receive all data (and has specifically requested it). Deselecting “Only send data attributed to PartnerXYZ” for a partner who is not setup correctly can cause reporting discrepancies and the partner to claim credit for installs attributed to someone else on the last-click. Selecting “Data:Attributed” prevents partners from claiming Duplicate Installs.
Check aggregated stats to see if there are clicks associated with your installs.
Go to the actuals report, find the partner, and filter the view by partner.
- If Attribution Analytics reports no clicks or installs, then check gross clicks:
- If only gross clicks, then the partners are not replacing the macros in their TUNE link. Attribution Analytics does not attribute installs on gross clicks, we need unique clicks for an install to be attributed to a partner.
- If there are clicks but no installs, then contact the partner (via email or phone) for the device identifiers (such as the device MAC address or iOS IFA value) that they used for testing. You can only request device identifiers from the partner that the Attribution Analytics SDK is set to collect.
Did the partner test the postback URL using their own mobile device?
If so, Attribution Analytics blocks/rejects duplicate installs from the same device. So if they already used that device to install the app, then Attribution Analytics rejects subsequent install attempts and no event is logged in the Attribution Analytics platform. First set up a test profile for each testing device.
Are you using macros that the partner system is setup to process?
If your TUNE link for the partner contains macros that their system is not set up to process, then they cannot replace these values and pass them back via the postback URL.
Is the partner system returning an HTTP error?
In your postback URL logs, look at the HTTP results of your postbacks. You can provide the partner with the postback URL and the error, and they can tell you what you need to change for the postback URL to function properly: