Paid and organic query report percentages instead of doubles

[Paul Ingles]

Hi,

We've noticed that some of the XxxPerQuery fields in this report are expressed as percentages rather than doubles.

We're using the 1.36.0 releases of com.google.api-ads/ads-lib and com.google.api-ads/adwords-axis to interact with the reporting service.

We build a ReportDefinition and request the ReportDefinitionReportType/PAID_ORGANIC_QUERY_REPORT. The ReportDefinition's Selector is configured to retrieve the following fields:

• Date
• SearchQuery
• Impressions
• Clicks
• OrganicClicksPerQuery
• OrganicQueries
• OrganicClicks
• CombinedAdsOrganicClicksPerQuery
• CombinedAdsOrganicClicks
• CombinedAdsOrganicQueries

The customer ID we're requesting this for is 125-850-9086 and we're using the ReportDownloader to download the data as a gzipped CSV.

The OrganicClicksPerQuery and CombinedAdsOrganicClicksPerQuery values contained within the CSV are formatted as percentages. For example:

{"Day" "....",

 "Organic Clicks/Query" "16.67%",

 "Organic Queries" "6",

 "Organic Clicks" "1",

 "Combined Clicks/Query" "16.67%",

 "Combined Clicks" "1",

 "Combined Queries" "6"

...}

Thanks,

Paul

uSwitch is a trading name of uSwitch Ltd. Registered in England and Wales (Company No. 03612689). Registered Address: Notcutt House, 36 Southwark Bridge Road, London, SE1 9EU

This communication and any attachments contains information which is confidential and may be subject to legal privilege. It is for intended recipients only. If you are not the intended recipient you must not copy, distribute, publish, rely on or otherwise use it without our consent. Some of our communications may contain confidential information which it could be a criminal offence for you to disclose or use without authority. If you have received this email in error please notify the sender immediately and delete the email from your computer.

uSwitch Ltd reserves the right to monitor all email communications for compliance with legal, regulatory and professional standards.

[Danial Klimkin]

Hello Paul,

I've confirmed this behavior and logged an internal issue for this. We'll schedule the fix for a future API release.

Thank you for reporting this issue.

-Danial, AdWords API Team.