Either I am missing something or conversion rate calculation on the AdWords
backend side is incorrect.
The conversion rate field description states: "The number of conversions
divided by total clicks"
So for a specific account (5833006980) and specific time period (20170201 -
20170228) we have
Have you tried searching before creating new
topic:
https://groups.google.com/forum/#!searchin/adwords-api/reporting|sort:date/adwords-api/MfX0XL7G4o4/FxioZYy_AgAJ
On Monday, June 19, 2017 at 7:08:25 AM UTC+2, AdWordsApiUser wrote:
>
> Hello team,
>
> AWQL response times have increased
Also, we see a significant performance decline since few days ago using
reporting API.
On Wednesday, June 7, 2017 at 11:35:48 PM UTC+2, Shwetha Vastrad (AdWords
API Team) wrote:
>
> Hi all,
>
> The team is working on a solution as a top priority. I'll keep you
> notified once I have more
Do you know if it's region specific issue or for all requests?
On Tuesday, June 13, 2017 at 5:18:46 PM UTC+2, Shwetha Vastrad (AdWords API
Team) wrote:
>
> Hi Axel,
>
> I'm afraid I don't have a timeline for when this will be resolved. I'll
> keep you notified when I have more information.
>
Hi,
I am seeing it as well. Can you tell us if there is an actual issue on your
end?
On Monday, September 11, 2017 at 8:35:56 PM UTC+2, Shwetha Vastrad (AdWords
API Team) wrote:
>
> Hi,
>
> Could you provide the report definitions and the clientCustomerId for
> which you observed reduced
We are currently using AdWords reporting, Analytics Reporting API v4 and
Facebook Ads Insights reporting API.
On average AdWords reporting is approximately at least twice as slow as
Analytics Reporting (usually more) and usually three times as slow as
Facebook Ads Insights API. And yes, we have
It's a bit like a closed loop:
1) Reporting API does not support sorters and paging, so you end up getting
data you don't really need which increases response time.
2) All the requests are super slow anyway, so you have to implement caching
with multi-threading. The slower it gets, the more
slowdown first encountered in September seems to be
> permanent.
>
> Thanks for your feedback and best regards,
> Dorian
>
> On Tuesday, 7 November 2017 11:50:10 UTC+1, Tomas R wrote:
>>
>> It's a bit like a closed loop:
>> 1) Reporting API does not support sor
Hi,
Today we noticed an unusual response from AdWords reporting API. One of the
"expanded text ads" in ad performance report segmented by date had an empty
value for the date field. Can you explain why that would happen?
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on
What's the escape character used by AdWords reporting API when exporting
CSV file? Is it backslash or double quote character?
On Friday, September 7, 2018 at 10:32:17 AM UTC+2, Tomas R wrote:
>
> Hi Luis,
>
> We found the problem. The reporting API is returning improperly form
t; you
> used to generate the report? Please reply via *Reply privately to author*.
>
>
> Best Regards,
> Luis
> AdWords API Team
>
> On Thursday, September 6, 2018 at 2:50:44 PM UTC+8, Tomas R wrote:
>>
>> Hi,
>>
>> Today we noticed an unusual re
on the reports is double quotes
> (""). For example your campaign name is (Campaign "36") it would result as
> ("Campaign ""36""") when generated via API.
>
> Hope this clarifies your concern.
>
> Regards,
> Luis
> AdWords API Team
words/api/docs/guides/reporting#supported_download_formats>
> for
> other supported download formats.
>
> Regards,
> Luis
> AdWords API Team
>
> On Friday, September 7, 2018 at 8:24:59 PM UTC+8, Tomas R wrote:
>>
>> What's the escape character used by AdWords reporting API
And they are back again...
Hope the new API will be feature complete soon.
On Tuesday, September 4, 2018 at 10:50:06 PM UTC+2, Nadine Sundquist
(AdWords API Team) wrote:
>
> Greetings Community,
>
> The root cause was identified, and we've been working through resolving it
> and making sure
Use Google Data Studio -> https://datastudio.google.com
On Monday, April 9, 2018 at 11:53:09 AM UTC+2, Tony D wrote:
>
> I am Not a developer and am trying to find out how to get a detailed copy
> of my Click Performance Report for my Adwords Account, and don't know much
> about API's. I have
We are facing this issue as well.
On Thursday, January 10, 2019 at 8:25:53 AM UTC+1, AdWordsApiUser wrote:
>
> Hi Team,
>
> We are seeing an empty value for device segment in reports now. We suspect
> this is due to CONNECTED_TV not being handled correctly by the report API.
> Your help will be
Hi,
Recently we started getting one AdGroup in Ad Group performance report with
empty "AdGroupType" value. Was there any intentional change which resulted
in this behavior? If so, what's the reason for it being empty?
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our
If it's new unsupported by AdWords API AdGroupType ("Display Smart "), how
about just returning "Unknown" instead of empty value until it becomes
supported?
On Wednesday, March 6, 2019 at 9:29:27 PM UTC+1, googleadsapi-forumadvisor
wrote:
>
> Hello Tomas,
>
> We are not aware of any recent
Trying to download geo perfomance report I get one of the region IDs
returned as "--" (country: Denmark (ID: 2208)). Also, the returned data
doesn't quite match the data shown in Google Ads UI.
Here is report definition:
RegionCriteriaId
CountryCriteriaId
Impressions
19 matches
Mail list logo
