Resolving Rejected Installs and Events

Introduction

If your reports show that Attribution Analytics rejected some installs or events, then it’s likely that these events are duplicate event requests because Attribution Analytics helps prevent duplicate attributions by limiting installs to one per user per mobile app, ever. Attribution Analytics also limits events to one per user per 60 minutes. You can get more information about why Attribution Analytics rejected a specific install or event by viewing its status code.

Viewing Status Codes for Rejected Installs

To find more details about a rejected install, view its status code:

  1. Login to Attribution Analytics.
  2. In the navigation (on the left side), under the Reporting section, click Logs.
  3. On the Logs page (on the right side), click Edit (to open the parameter options), and in the Data section, check the box for Status Code as shown in the following screenshot.What_does_it_mean_if_an_install_or_event_is_rejected_1_Status_Code_Checkbox
  4. Scroll down to the Filter section, and remove the filter for Status: Approved as shown in the following screenshot.What_does_it_mean_if_an_install_or_event_is_rejected_2_Remove_Filter
  5. From the filter drop-down list, select Status, and from the Select Status drop-down list that appears, select Rejected, and then click Add as shown in the following screenshot.What_does_it_mean_if_an_install_or_event_is_rejected_3_Add_Rejected_Filter
  6. After replacing the Status: Approved filter with the Status: Rejected filter, click Apply as shown in the following screenshot.What_does_it_mean_if_an_install_or_event_is_rejected_4_Apply_Filters
  7. In the resulting report, you can get more information about your rejected installs by viewing the Status Code column as shown in the following screenshot.What_does_it_mean_if_an_install_or_event_is_rejected_5_Report

Status Code Reference

The following table lists the available status codes that Attribution Analytics may display for rejected installs.

Status Code Value
Duplicate by Device ID 1
Duplicate by Device ID MD5 2
Duplicate by Device ID SHA1 3
Duplicate by Mac Address 4
Duplicate by Mac Address MD5 5
Duplicate by Mac Address SHA1 6
Duplicate by OS ID 7
Duplicate by User ID 8
Duplicate by ODIN 9
Duplicate by Open UDID 10
Duplicate by TPID 11
Duplicate by MAT ID 12
Duplicate by iOS IFV 13
Duplicate by iOS IFA 14
Duplicate by UNID 16
Duplicate for other reason 17
Duplicate by iOS IFV MD5 18
Duplicate by iOS IFV SHA1 19
Duplicate by iOS IFA MD5 20
Duplicate by iOS IFA SHA1 21
Duplicate by IAP Receipt MD5 23
Duplicate by Google AID 24
Duplicate by Google AID MD5 25
Duplicate by Google AID SHA1 26
Missing iTunes App Store Receipt 27
Duplicate Open 28
Duplicate Post Conversion 29
OS Jailbroke 50
Invalid iTunes App Store Receipt 51
Invalid Google Play Receipt 52
Invalid Currency 70
Bad Device 71
Organic Already Attributed 72
Publisher Already Attributed 73
Update prior to Install 74
Re-attributing from Organic 75
Deactivated Test Profile 76
Receipt Date over 30 Days old 77
IsUnique Cookie Parameter 78
Bot Detected 79
Re-install Detected via Google Referrer 80
iTunes Receipt over 30 Days old 81

* Status Code 77 does not necessarily indicate that an install is rejected.

 

In the resulting report (that includes the Status Code column), you can mouseover a status code to reveal its code value in the tooltip, as shown in the following screenshot.

What_does_it_mean_if_an_install_or_event_is_rejected_6_View_Status_ID

Rejecting Duplicate Events

Attribution Analytics lists an install or event as ‘rejected’ if it considers the event a duplicate (for example, if fraudulent users try to install an app multiple times on their device). The measurement engine automatically rejects these conversions because Attribution Analytics limits installs to one per user per mobile app, ever. Attribution Analytics rejects any subsequent install requests (after the first install) as a duplicate request. If you’re using a test profile, then make sure you set the status to Active.

Attribution Analytics also limits events to one per user per 60 minutes. Attribution Analytics rejects any event request that is exactly the same for a user and mobile app within the 60-minute time window. Attribution Analytics approves the same event request after 60 minutes, and then again, any subsequent event requests within the next 60 minutes are rejected as duplicate requests.

If the event is in fact a new and unique event, then you can measure the duplicate events within the 60-minute window by setting the advertiser reference id. For each event request with a unique reference id, Attribution Analytics measures it as approved. But Attribution Analytics rejects duplicate event requests (with the same reference id) within the 60-minute window.

If the event request includes an items payload, then Attribution Analytics takes into account the event items when determining if the event request is a duplicate request. If the event items are not the same, then Attribution Analytics measures the event as approved. If the same event request occurs with the same event items, then Attribution Analytics rejects any duplicate requests within the 60-minute window.

While Attribution Analytics does not allow or permit duplicate install requests (except for test profiles), we can manually set the time frame for a duplicate event in the Attribution Analytics platform to as low as 10 seconds. To adjust this Block Duplicate Request setting for events, send an email to [email protected] and include the name of your mobile app, event name, and the desired duplication time frame.

For more information about blocking duplicate requests, please visit Block Duplicate Request Setting for Events.

1 Comment

Leave a reply