Hi Suchit,

Have you tried picking *All time* in the AdWords user interface? It won't 
give you any values, either. So, if you do *All time* for the user using 
the AdWords API, it won't be any different than the AdWords user interface. 
That should at least set an expectation for the users of your tool that 
what you are displaying and what they are seeing through the AdWords user 
interface is the same.

As for breaking down the calls into smaller intervals, that's a cool, 
creative solution to your problem. Unfortunately, there isn't an easy way 
of knowing what <100 is if you're trying to add up all of the days. There's 
an AdWords Help Center article 
<https://support.google.com/adwords/answer/2472714?hl=en> that has an 
explanation on how the reach is calculated. You may be able to take 
advantage of the mathematical explanation. Check it out here 
<https://support.google.com/adwords/answer/2472714?hl=en>.

Hoping that helps,
Nadine, AdWords API Team

On Sunday, April 3, 2016 at 2:39:35 PM UTC-4, Suchit Puri wrote:
>
> Hi Nadine,
>
> So the use case is that the client comes in to Adalyz, he links his 
> adwords account. He then all the analysis, historic and present for his 
> campaigns. Now since its the first time we are fetching the data for him , 
> we fetch the daily data for all time.
>
> Since the Adwords UI shows the unique cookies values, we also need to show 
> it in our tool. Now as you said if we fetch the all time daily data for 
> ImpressionReach/UniqueCookies then we dont get any values. But if we fetch 
> for smaller intervals we might get some values. I will try breaking calls 
> to smaller interval.
>
> Now another problem is that suppose we get UniqueCookies for days as < 100 
> , how do we compute the total unique cookies for that time interval.
>
> Day 1- Unique Cookies = 20
> Day 2- Unique Cookies = < 100
> Day 3 Unique Cookies = 30
> Day 4 Unique Cookies = 30
> Day 5 Unique Cookies = 50
>
> now when show the aggregated values  =* day 1 to day 5 *= 20 + < 100 + 30 
>  + 30 + 30 + 50 = ?
>
>
> Regards
> Suchit
>
>
> On Thu, Mar 31, 2016 at 7:06 PM, 'Nadine Sundquist (AdWords API Team)' via 
> AdWords API Forum <adwords-api@googlegroups.com> wrote:
>
>> Hello Suchit,
>>
>> That does make sense that you would retrieve that information for all 
>> time when someone is connecting for the first time. Yes, some data such as 
>> "Unique Cookies/Impression Reach" will not be calculated when you choose 
>> *All 
>> time*. That is the case for both our user interface and the API. I only 
>> suggested 14 days because your screenshot showed 14 days. I checked your 
>> account, and that account has data from January 1st of this year to present 
>> for that particular field.
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Thursday, March 31, 2016 at 1:18:26 AM UTC-4, Suchit Puri wrote:
>>>
>>> Hi Nadine,
>>>
>>> Thanks for the answer, so we have an analytics tool which is 
>>> importing day wise data for the client from adwords api. Now when the 
>>> client connects is account for the first time we import "all time" data 
>>> segmented by day for him , and there we get “—“ for unique cookies.
>>>
>>> Now once the we get the all time daily data we just fetch only the 
>>> current day data, which seems to work fine.
>>>
>>> Now are you suggesting that All Time segment by day will now show the 
>>> correct “UniqueCookies/ImpressionReach” and we should fetch only 14 days of 
>>> data ?
>>>
>>>
>>> Thanks
>>> Suchit Puri
>>>
>>>
>>> On Thu, 31 Mar 2016 at 1:51 AM "'Nadine Sundquist (AdWords API Team)' 
>>> via AdWords API Forum" <">"'Nadine Sundquist (AdWords API Team)' via 
>>> AdWords API Forum" > wrote:
>>>
>>>> Hi Suchit,
>>>>
>>>> Thanks for providing the screenshots and the report. I noticed that in 
>>>> the AdWords user interface you chose *last 14 days*, while in the API 
>>>> you chose *ALL_TIME*. If you change your choice in the AdWords user 
>>>> interface to be *All Time*, you'll notice that you now get back *'--'* for 
>>>> everything, which matches your API request. When you choose *All time* for 
>>>> any request to AdWords, some fields will not be calculated for various 
>>>> reasons such as processing time to calculate the request. You could also 
>>>> change your API request to say *LAST_14_DAYS* to match your AdWords 
>>>> user interface request. When you do that in your API request, you'll start 
>>>> getting back numbers just like in the AdWords user interface.
>>>>
>>>> Cheers,
>>>> Nadine, AdWords API Team 
>>>>
>>>> On Wednesday, March 30, 2016 at 8:05:57 AM UTC-4, Suchit Puri wrote:
>>>>>
>>>>> Hi Yi,
>>>>> I have sent you the report definition in private reply.
>>>>>
>>>>> The question still remains the same. The ImpressionReach is coming as 
>>>>> '--" when you pull a simple reports from the UI or pull it from the API. 
>>>>> But the UI shows correct values.
>>>>>  
>>>>>
>>>>> Regards
>>>>> Suchit Puri
>>>>>
>>>>> On Tuesday, March 29, 2016 at 7:07:07 PM UTC+5:30, Yin Niu wrote:
>>>>>>
>>>>>> Hi Suchit, 
>>>>>>
>>>>>> Could you please send me the report definition and the 
>>>>>> clientCustomerID? I am not able to find "Interaction Types" field in 
>>>>>> Campaign 
>>>>>> Performance Report 
>>>>>> <https://developers.google.com/adwords/api/docs/appendix/reports/v201601/campaign-performance-report>
>>>>>>  fields 
>>>>>> list. 
>>>>>>
>>>>>> For impressionReach 
>>>>>> <https://developers.google.com/adwords/api/docs/appendix/reports/v201601/campaign-performance-report#impressionreach>,
>>>>>>  
>>>>>> "<100" is special value when the number of cookes is less than 100. 
>>>>>> Notice 
>>>>>> that ImpressionReach field is not compatible with ClickType 
>>>>>> <https://developers.google.com/adwords/api/docs/appendix/reports/v201601/campaign-performance-report#clicktype>
>>>>>> . 
>>>>>>
>>>>>> Thanks,
>>>>>> Yin, 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 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 https://groups.google.com/group/adwords-api.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/adwords-api/dd7eeb8f-c375-401b-8468-868dd0db990f%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/adwords-api/dd7eeb8f-c375-401b-8468-868dd0db990f%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> -- 
>> -- 
>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>> 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 https://groups.google.com/group/adwords-api.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/adwords-api/e8647b89-84bf-4892-9f0e-58f98cfb8fba%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/adwords-api/e8647b89-84bf-4892-9f0e-58f98cfb8fba%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/ac329e1e-0aa9-4c03-b2c9-ed6db6782495%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  • Re: Impression... 'Yin Niu' via AdWords API Forum
    • Re: Impre... Suchit Puri
      • Re: I... 'Yin Niu' via AdWords API Forum
        • R... Suchit Puri
        • R... Suchit Puri
        • R... Suchit Puri
          • ... 'Nadine Sundquist (AdWords API Team)' via AdWords API Forum
            • ... Suchit Puri
              • ... 'Nadine Sundquist (AdWords API Team)' via AdWords API Forum
              • ... Suchit Puri
              • ... 'Nadine Sundquist (AdWords API Team)' via AdWords API Forum

Reply via email to