Account Performance Report - Measures Vastly Overstated

43 views
Skip to first unread message

k2atotc

unread,
Feb 26, 2018, 3:24:17 PM2/26/18
to AdWords API Forum
Hi,

I'm running an 'Account Performance Report' API request using AWQL via Python 3.6. 
  • We have basic access against a production MMC account.  Seems to work fine.
  • I'm pulling for several child clients and appending the results into a single file.  Seems to work fine.
  • I'm pulling for duration 'YESTERDAY' - which also seems to work fine.  The day field is coming correctly and the report header also shows the expected values.
  • Everything seems to execute correctly - I get a populated TSV file for all the child clients but the impressions/cost are vastly overstated.
  • This same thing is happening for my KEYWORDS_PERFORMANCE_REPORT.
  • I've attached a CSV of what I get when pulling the same request from the portal - which is more in line with reality.  This is production data.
 Here is my report builder statement:

  # Initialize appropriate service.
 
try:
    report_downloader
= client.GetReportDownloader(version='v201710')


   
# Create report query.
    report_query
= (adwords.ReportQueryBuilder()
                 
.Select(  'AccountDescriptiveName'
                         
, 'Date'
                         
, 'Impressions'
                         
, 'Clicks'
                         
, 'Cost')
                 
.From('ACCOUNT_PERFORMANCE_REPORT')
                 
.Where('Clicks').GreaterThan(0)
                 
.During('YESTERDAY')
                 
.Build())
 
except Exception as e:
   
print (e)
    logger
.exception(e)
    sys
.exit(1)

Here's what my down loader looks like:

    # Download the report data
    report_downloader
.DownloadReportWithAwql(
        report_query
, 'TSV', file, skip_report_header=False,
        skip_column_header
=True, skip_report_summary=True,
        include_zero_impressions
=False)


Here is what's returning in my report TSV file.  I replaced our company name with XXX at the beginning of each header line.
  • Each child account is represented as it should be.
  • The dates in the report header line and day field are correct.
  • The impressions, clicks, and cost are incredibly high (bold and underlined the first example).  We've never spent that much in our entire time with Google.
  • I noticed in the Keywords Performance versions (also pulled for yesterday) that the cost measures are very odd - 30000, 100000 - very even and large.
"ACCOUNT_PERFORMANCE_REPORT (Feb 25, 2018)"
XXX PLA
2018-02-25 5871848 60698 25662830000
"ACCOUNT_PERFORMANCE_REPORT (Feb 25, 2018)"
XXX
Brand 2018-02-25 44766 23918 1382870000
"ACCOUNT_PERFORMANCE_REPORT (Feb 25, 2018)"
XXX
Product 2018-02-25 514570 5985 3358990000
"ACCOUNT_PERFORMANCE_REPORT (Feb 25, 2018)"
XXX
- Product - Mobile 2018-02-25 611296 7905 2354500000
"ACCOUNT_PERFORMANCE_REPORT (Feb 25, 2018)"
XXX
Seasonal Occasion 2018-02-25 52871 706 630970000
"ACCOUNT_PERFORMANCE_REPORT (Feb 25, 2018)"
XXX
- Seasonal Occasion - Mobile 2018-02-25 110549 959 275630000
"ACCOUNT_PERFORMANCE_REPORT (Feb 25, 2018)"
XXX
Evergreen 2018-02-25 81661 2488 2186640000
"ACCOUNT_PERFORMANCE_REPORT (Feb 25, 2018)"
XXX
- Evergreen - Mobile 2018-02-25 98888 2054 1021680000

Please let me know if there's something I'm doing wrong and how I should adjust my code.

Thank you in advance.



account balance report.csv

Peter Oliquino

unread,
Feb 27, 2018, 12:22:50 AM2/27/18
to AdWords API Forum
Hi,

It seems that everything is working perfectly on your code. The issue with the large value of costs that you are encountering is due to the Cost and other "money" fields are represented in micros. This means that the actual value will still need to be calculated or converted by dividing 1,000,000 from the cost value you got from the report. However, as for the impressions, you can consider them as is.

Let me know if this helps or if you have any further clarifications.

Thanks and regards,
Peter
AdWords API Team

k2atotc

unread,
Feb 27, 2018, 8:41:28 AM2/27/18
to AdWords API Forum
Oh, excellent!  Thanks for the explanation - I missed that somewhere in the process.  Marking as complete.
Reply all
Reply to author
Forward
0 new messages