Indeed it looks like an inconsistent handling of the case "not applicable". 
Excerpt from the AdWords forum thread 
<https://www.en.advertisercommunity.com/t5/AdWords-Tracking-and-Reporting/Average-Position-0-0/td-p/1664329#.Wq94HrQPFkU.link>
:

"For the Shopping case I agree and this is what I assumed as well. But in 
such a situation the report (pulled via API) should return "not 
applicable", i.e. n/a, NULL, or "--" (two dashes 
<https://developers.google.com/adwords/api/docs/guides/reporting#two_dashes>) 
as for other fields in the report. This is not a proper handling the "not 
applicable" case.

I also see Average Position = 0.0 for Search and Display campaigns. In 
those cases it always seems that the impressions = 0 but clicks > 0. So are 
these "just" data inconsistencies? Having clicks but no impressions and no 
average position in Search does not sound very reasonable to me."

I think 0.0 for average position is just the default value for the case 
"not applicable" for a numeric value on your side. Can you confirm this? 
Because then I can handle it properly again on our side in the database and 
convert the 0.0 values to NULL.

Are there other fields that have such a special "not applicable" case 
handling? Because for string fields it seems the reports always return "--" 
(two dashes) as per documentation 
<https://developers.google.com/adwords/api/docs/guides/reporting#two_dashes>. 
If this is the case, the documentation should probably expanded in order to 
cover this case as well.

On Friday, 16 March 2018 21:12:51 UTC+1, Dhanya Sundararaju (AdWords API 
Team) wrote:
>
> Hi Marcel,
>
> Thanks for posting in the advertiser community forum. With an answer from 
> the product expert, we will be able to troubleshoot API side better, for 
> this case. Incase you opt to come back to this thread, please reply with 
> your client customer id and report definition. Please let me know if you 
> have further questions.
>
> Regards,
> Dhanya, AdWords API Team
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
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 [email protected].
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/da4616d4-bd9c-4332-b914-b99647c1df74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  • Average Posi... Marcel Zemp
    • Re: Ave... Zweitze
      • Re:... 'Dhanya Sundararaju (AdWords API Team)' via AdWords API Forum
        • ... Marcel Zemp
          • ... 'Dhanya Sundararaju (AdWords API Team)' via AdWords API Forum
            • ... Marcel Zemp
              • ... 'Dhanya Sundararaju (AdWords API Team)' via AdWords API Forum

Reply via email to