Hello MG,

We normally avoid making changes into launched API versions. Scripts users 
(those specifying API version) should not be affected, unless they didn't 
read the release notes when migrated to v201502.

Please note while we are going to discuss this issue, I can't promise this 
change will be implemented.


-Danial.



On Friday, April 17, 2015 at 4:57:31 PM UTC+3, AdWordsApiUser wrote:
>
> Hi Danial,
>
> Thanks for your quick response. Is there a chance that this might change 
> in v201502? If yes, then we'd like to hold off the internal upgrade waiting 
> for this to happen. My guess is must already be affecting scripts, and as 
> this is pretty much a silent change, script users might not even realize 
> that the data they are fetching is not complete anymore.
>
> Cheers,
> MG
>
> On Friday, April 17, 2015 at 9:08:26 AM UTC-3, Danial Klimkin wrote:
>>
>> Hello,
>>
>>
>> Reporting filters out removed entries for the level of the report only. 
>> So, account level report will return stats for all objects (and you can't 
>> actually add CampaignStatus predicate while requesting it).
>>
>> In general, I see your point. We may want to take another look on how 
>> this is handled.
>>
>>
>> -Danial, AdWords API Team.
>>
>>
>> On Friday, April 17, 2015 at 2:59:53 PM UTC+3, AdWordsApiUser wrote:
>>>
>>> In the new version of the API, when using AdHoc reports, data for 
>>> artifacts that are marked removed is not included by default, even if they 
>>> had impressions, clicks etc. in the chosen date range. This makes the 
>>> reports incorrect. If an entity was active in the past, its statistics 
>>> should be included, irrespective of whether it is active or not now. 
>>>
>>> This also makes me wonder - when I ask for an account performance 
>>> report, would it not include data for campaigns that were deleted? Or, it 
>>> would? Both cases create a discrepancy - the first one is obviously wrong, 
>>> and in the second one, the campaign report does not add up to the account 
>>> performance report, unless the special condition is included.
>>>
>>> This particular change in behavior has made the transition to the new 
>>> version of the API particularly painful, and I have to remember to include 
>>> "WHERE CampaignStatus IN [ACTIVE, PAUSED, REMOVED]" in all my awqls. It 
>>> probably makes sense for most services, but not for reporting stats.
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/415b8dc8-376c-4891-9c86-ce1afb828437%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to