Android integration testing for ad networks

Complete the prerequisites before beginning to execute the test procedure.

To trigger postbacks:

1. Send the attribution link previously prepared to a test device.
2. Click on the link, install and then open the app.
   The Install Data page displays.

3. Validate the attribution using the following parameters. If the validation fails, see Troubleshooting.

   1. install_time: near the current time. Time is in UTC. 
   2. af_status: Non-organic If this is not the case, the install was not attributed. 
   3. media_source: your ad network 
4. Tap In-App Event Tests.
5. Tap Purchase Event.
   The Purchase Event confirmation displays. 
6. Verify that:
   1. You received install and purchase postbacks.
   2. The event name is mapped correctly (if you mapped in-app events).
   3. You are able to ingest the postback.

The Partner Integrations app is available in Google Play. The app sends install and in-app events to the AppsFlyer platform. 

When the app is opened for the first time, the Install Data page displays the conversion data recorded in the AppsFlyer platform. Test in-app events are triggered in the user interface.

The following functions are available:

• In-App Event Tests
  Send purchase,login, and registration and in-app events. By mapping the app in-app event names to your event names, postbacks are populated using your event names. 

Prepare an attribution link in the AppsFlyer dashboard, using one of the following methods:

• Generate the link in the AppsFlyer dashboard.
• Edit the example link that follows.

To generate a link in the dashboard:

1. In AppsFlyer, from the top menu, select to My Apps.
2. Select adNetworkTest.
3. In AppsFlyer, from the side menu, select Collaborate > Active Integrations > select your ad network > Attribution link tab.
4. In the Attribution link tab, set the parameters listed. You can add additional parameters if required. Link to attribution linkd

   Parameter	Example value	Remark
   Campaign	c-test-2020-12-20	Set a value that is identifiable in your postbacks
   PID	pitestap

5. Copy the resulting link for later use. 

Example attribution link:

https://app.appsflyer.com/com.appsflyer.adNetworkTest?pid=pitestap_int&c=c-test-2020-12-20
    

To verify that the test app is available in your account: 

1. In AppsFlyer, from the top menu, go to My Apps.
2. Verify that the app Partner Integrations adNewtorkTest displays under Available Apps. If this is not the case, contact your Partner Development Manager. 

You can also test retargeting attribution. The process is almost the same except for one parameter that you add to the attribution link.

Generate a new attribution link and add the parameter is_retargeting=true to it.

https://app.appsflyer.com/com.appsflyer.adNetworkTest?pid=YOUR_PID&c=YOUR_CAMPAIGN&af_click_lookback=7d
          &clickid={clickid}&is_retargeting=true
          

Install the app using the retargeting link. The flow is the same as described in testing install attribution.

Viewing retargeted installs in the dashboard

Access your AppsFlyer dashboard and click on Re-targeting in the left-side menu. Allow up to 30 minutes for the retargeted install to appear in the dashboard.

1. In AppsFlyer, go to My Apps.
2. Select adNetworkTest.
3. In AppsFlyer, from the side menu, select Collaborate > Active Integrations > select your ad network > Integration tab.
4. Make sure that Enable view-through attribution is ON.
5. Copy the Impression attribution link.

   https://impression.appsflyer.com/com.appsflyer.adNetworkTest?pid=YOUR_PID&c=YOUR_CAMPAIGN&af_viewthrough_lookback=24h&advertising_id=YOUR_GAID&af_siteid=YOUR_SITEID

   Replace the parameters as follows:

   • YOUR_PID - your partner ID supplied by AppsFlyer (ending with _int)
   • YOUR_CAMPAIGN - any campaign name
   • YOUR_GAID - your Google Advertising ID
   • YOUR_SITEID - any site ID

   Note: the parameters in the link are the basic parameters used here for the purpose of testing. You can have other parameters in the view-through attribution link according to your requirements.

6. Send the view-through attribution link to the test device.
7. Open the link in the browser and install the app from the store.
8. Launch the app.
   The following screen displays:

   

   If you don't see this message, make sure that the view-through attribution link is formatted correctly. Uninstall the app and reinstall using the view-through attribution link with the new test device.

Tip

For more elaborate results, repeat the installation process using the view-through attribution link with the new test device. Uninstall the app, change the parameters in the link (the campaign name, af_siteid, and advertising_id), and install again by clicking the URL.

View installs in the dashboard

Once you install and launch the app, you can see the results in your AppsFlyer dashboard.

Allow up to 30 minutes for the install to appear in the app dashboard.

Data related to apps whose install is attributed to your ad network can be exported in CSV format.

The data includes the following:

• Installs
• In-app events
• Retargeting installs
• In-app events of apps installed from retargeting campaigns

To export raw data:

1. In AppsFlyer go to, Report > Raw data export.
2. Select the date range.
3. Select a report.
   The report downloads within a few minutes.

Every install generates a postback that is sent to your servers. To verify the postback URL, its structure, and the parameters that are appended to it, export the Installation postbacks report.

The Installation postbacks report contains a column titled Postback URL. This column lists the postback URLs as generated for each and every install.

Review the data in that column to verify the following:

• The URL endpoint is the correct one
• The parameters appended to the URL correspond to those appended to the AppsFlyer attribution link
• The Postback Error Message column is empty