We're working on a mini-guide explaining how to approach this. In the meantime, here's a draft:
Test accounts will not serve impressions, therefore they will not have any metrics. It is still possible to download
structural reports - but you will only see zero-impression rows, which means that segments will not work. To get around this limitation, we suggest displaying fake data. The Token Review team needs to see that your application can interact with and display report data. By mocking out the report call (i.e. pretending the report call succeeded and using a locally stored file containing fake report data), you can work with report data without actually having such data come back from the API.
The reports come back in a predictable format. Let's say you wanted to run a Campaign Performance Report pulling Date, Campaign Name, Id, Impressions, Clicks, Cost. An example file could look like this:
"CAMPAIGN_PERFORMANCE_REPORT (Mar 20, 2013-Mar 23, 2013)"
Day,Campaign,Campaign ID,Impressions,Clicks,Cost
20130320,Widgets,123,1211,19,14.92
20130320,Sprockets,456,300,4,2.92
20130321,Widgets,123,901,12,9.86
20130321,Sprockets,456,340,5,3.86
20130322,Widgets,123,1065,16,11.23
20130322,Sprockets,456,509,6,5.23
20130323,Widgets,123,1005,15,10.12
20130323,Sprockets,456,287,3,1.12
By constructing such a file and storing it locally, you could have your application mock the call to the API - when the report is requested, return the stored file and process that rather than making an actual API call. You can create one file like this for each report you’d like to display.
- Kevin Winter
AdWords API Team