Hello, Thank you for the additional information. That confirms my theory. We're looking into it, and I'll keep you updated on our progress.
Cheers, Nadine, AdWords API Team On Monday, March 7, 2016 at 8:39:14 AM UTC-5, suvod...@adnabu.com wrote: > > Hi Nadine > > Any update on this? I had sent you the details you had asked for. > > On Saturday, March 5, 2016 at 4:40:22 AM UTC+5:30, Nadine Sundquist > (AdWords API Team) wrote: >> >> Hi, >> >> One other thing would really help me out. Could you also click *Reply >> privately to author* in the forum and send me your customer ID? That >> would be a huge help. >> >> Best, >> Nadine, AdWords API Team >> >> On Friday, March 4, 2016 at 6:07:53 PM UTC-5, Nadine Sundquist (AdWords >> API Team) wrote: >>> >>> Hello, >>> >>> So, it looks like this value related to AdGroupBidModifier.bidModifier >>> <https://developers.google.com/adwords/api/docs/reference/v201601/AdGroupBidModifierService.AdGroupBidModifier#bidmodifier>. >>> >>> The only time I can possibly think of this being blank (--) would be if >>> there was no AdGroupBidModifier set. Is that the case with some of your >>> campaigns? We'll start looking into it in the meantime. I just want to >>> verify that's the case here. >>> >>> Thanks, >>> Nadine, AdWords API Team >>> >>> On Friday, March 4, 2016 at 3:51:04 PM UTC-5, suvodhoy sinha wrote: >>>> >>>> I see an inconsistency in the data in Ad Group Performance Report. We >>>> have four variations of setting mobile bid modifier in the adwords >>>> interface. For each of these I have mentioned the value which comes in the >>>> report under the column *mobileBidAdj* >>>> >>>> 1. 0% : 1.0 >>>> 2. 20% (this is an example value can be in -90% to 300%) : 1.2 >>>> 3. leave blank (*--*) : 0.0 >>>> 4. -100% : 0.0 >>>> >>>> As you will notice the value is same for the 3rd and 4th option which >>>> makes it very difficult to distinguish. As per my knowledge, if you >>>> are leaving the modifier blank ,ie, --, it means you are using the same >>>> bid >>>> for mobile. So 0% and -- both mean the same and should ideally return 1.0 >>>> for both if not 1.0 and -- respectively. Is this behaviour expected or >>>> am I missing something? >>>> >>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/bdb35a88-cff0-4ff6-8864-c1ab1b642d56%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
