This article shows how to set up an end-to-end test of your ads to make sure they render correctly on a device and to complete test install and conversion validating that all postbacks work well. You will find this useful before launching your first campaign with Kayzen and on a recurring basis when testing new creatives.

Testing of end-to-end ad delivery

1. Create an order and a new app that you’d like to test within this order.

2. Create a 1st party audience with the device id(s) on which you’ll be performing a test install/action. You can use this app (for iOS, Android) to find out your device id. Upload your device id in CSV format without any additional data in the file (you can download sample CSV to check the correct format from Kayzen Console:

3. If you uploaded your device id(s) correctly, you’ll see a number of users in the No. of users column within an hour. Click on Today to see the number of users if the audience was created today.

4. Create a test campaign with the app you want to test, and target the audience that you’ve created in Step 2

  • For whitelisting, pick app(s) with a high amount of daily auctions for the respective creative type/size you are using for your test (e.g., for video creatives, playable ads, banners you can use HelixJump, etc.). If you want to test how your ads render in a specific SDK (e.g. Mopub, Applovin, Unity) make sure to pick an app that monetizes using that SDK.
  • To find out an app that fits best for testing, you can use Kayzen Inventory Discovery & Analytics. Filter available inventory by country from where you’re performing a test, OS, creative type, creative size and all other necessary dimensions (e.g., rewarded/non-rewarded, etc.), then you’ll see apps with the highest amount of auctions available under App Bundle table. If you want to do your test on a specific exchange, look for an exchange-specific app id in Exchange ID – App ID table and use it for whitelisting.

Add app bundles or ExchangeID-AppIDs to a correspondent field in your campaign targeting under App Group section. Don’t save your app group, so you can change the apps you whitelisted later on.

5. We recommend running tests on CPM optimization type (with bid optimization and pacing disabled) and put a high bid of $100-300 CPM for the test. To do that, your campaign’s daily budget should be at least the same as your bid. After some time you’ll see your ad and can do a test install and in-app actions. Don’t worry about the high bid, as long as you target only your own device ID you will only pay for impressions displayed on your device or other test devices you use for this test.

Testing of end-to-end conversion (e.g. install, in-app event)

In order to test conversions end-to-end, you need to follow the above steps plus the following two steps.

1. Integrate MMP or use our API for custom postbacks (you can find MMP integration guides here; and the postback event API documentation here). Follow this article to obtain an API key for the app you are testing conversion for. Make sure you send all the events that you’d like to receive in your Kayzen account. 

2. In order to see post-install in-app actions in Kayzen Console, you need to go to Admin Console, then tick the checkboxes with the relevant action names to show them in the UI (Dashboard, Campaigns pages). Note, that it can take sometimes up to 2 hours for conversion events to be visible in the UI.

Did this answer your question?