Re: Unexpected Segmentation In GEO_PERFORMANCE_REPORT

Hi Dorian, The behavior you observed was as expected, but this highlighted that our documentation (and ReportDefinitionService ) was incorrect. We've updated the *Behavior* for AdGroupId, AdGroupName,

Re: Unexpected Segmentation In GEO_PERFORMANCE_REPORT

Hi Anthony, I've replied to you privately sending the requested information. Thanks for your support! Best regards, Dorian On Tuesday, August 25, 2015 at 4:29:43 PM UTC+2, Anthony Madrigal wrote: Hi Dorian, I was unable to replicate the results you were getting. Could you please send me

Re: Unexpected Segmentation In GEO_PERFORMANCE_REPORT

Hi Dorian, I was unable to replicate the results you were getting. Could you please send me your SOAP XML request and response where this is happening? Thanks, Anthony AdWords API Team -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+:

Re: Unexpected Segmentation In GEO_PERFORMANCE_REPORT

Hi Dorian, Thanks for sending over the examples. I was able to reproduce the behavior you described. I've passed this along to the reporting team and will post back here as soon as I have any updates. Cheers, Josh, AdWords API Team On Tuesday, August 25, 2015 at 11:16:30 AM UTC-4, Dorian Kind

Unexpected Segmentation In GEO_PERFORMANCE_REPORT

Hey there, I just noticed that adding a predicate based on AdGroupStatus to a GEO_PERFORMANCE_REPORT will result in an implicit segmentation of the report by ad group ID, even if the AdGroupStatus field itself is not included in the report definition. Is this the expected behavior? I'm