Hi, Thanet. On Saturday, September 17, 2016 at 7:34:28 AM UTC+3, Thanet Knack Praneenararat wrote: > > Hi Igor, > > And I need criteria performance report in single attribution. This is > mandatory and critical for us. > > Could you please clarify why you need this report type despite the > behavior I explained before, that is, you can't guarantee what to get back? >
We use it for matching with orders using gclid (click performance report) , orders calculated by our own attribution. This report contain all spends on targeting level (keyword_id). Google Analytics do the same. BTW Click performance report contains custom affinity. So currently we cannot match the data correctly. How GA do it? Use different infrastructure, hidden from advertisers, even for big advertiser. > > But the problem is not in attribution. Problem is that API don't return > lines with Custom Affinity, but AdWords script do, GA also show this data. > > API *does* return custom affinity but as I explained before, not in all > situations that it will return custom affinity back, because it's *a > single attribution*. > Besides, GA and AdWords Script doesn't always use the same infrastructure > as AdWords API. > We can't expect the same behaviors across the products. > What do you mean? We've compared result from script and API: it's the same except lines with custom affinity. > > BTW the total costs/clicks/impressions in criteria performance report from > API are less than actual costs! > > If you mean comparing the result from criteria performance report with > that in *Display Network* of UI, then it's as expected. > Those in UI are mainly multiple attribution reports and the total number > of stats mostly can't be matched directly with the single attribution > reports. > > I know that there are only multiply attribution reports in UI. We're using such reports for some specific optimizations (placement, banners, audience and etc). But for matching with gclid I need criteria report. > Feel free to ask more questions, if you feel this is still not clear. > > Best, > Thanet, AdWords API Team > > On Saturday, September 17, 2016 at 5:27:51 AM UTC+9, Igor Selitskiy wrote: >> >> Hi, I understand single and multiply attribution in AdWords. I know the >> difference. We're using both types of attribution. >> And I need criteria performance report in single attribution. This is >> mandatory and critical for us. >> But the problem is not in attribution. Problem is that API don't return >> lines with Custom Affinity, but AdWords script do, GA also show this data. >> BTW the total costs/clicks/impressions in criteria performance report >> from API are less than actual costs! >> >> We provide examples for you in private message, even more I point out on >> one of our AdGroup to illustrate the problem. >> >> >> On Friday, September 16, 2016 at 10:48:25 PM UTC+3, Thanet Knack >> Praneenararat (AdWords API Team) wrote: >>> >>> Hello, >>> >>> Let me summarize some info here again. (I already edited some messages >>> above so that people who happen to read from the beginning don't get >>> confused) >>> >>> First, I'm so sorry to make you misunderstand that CUSTOM_AFFINITY is >>> not returned in CRITERIA_PERFORMANCE_REPORT. >>> Actually, it *does* but *not* in all cases that you can get the data >>> for CUSTOM_AFFINITY back. >>> The reason is that the criteria performance report is a single >>> attribution type >>> <https://developers.google.com/adwords/api/docs/guides/reporting#single_attribution> >>> . >>> In this type of report, we *can't* guarantee that all types of criteria >>> type will appear, nor can we control what kinds of criteria will appear. >>> This is a concept used in AdWords API reporting for a long time. >>> >>> As you may know, one impression (and other stats like click) for display >>> network can be triggered by one or more criteria. >>> For example, an impression might be triggered by *gender male*, *age >>> range 34-43*, and *an affinity with name "A"*. >>> In criteria performance report, however, this impression can be >>> attributed to *only one* of any of gender OR age range OR affinity. >>> We don't know and can't guarantee which one will be reported. >>> If it's reported as attributed to *gender male *already, then this >>> particular impression will not appear again in the report. >>> >>> In your case, it's likely that *all* impressions attributed to *all *custom >>> affinities are reported to be attributed to *other criteria*. >>> That's why you don't see them attributed to custom affinity in your >>> report. >>> >>> The workaround would be to use multiple attribution >>> <https://developers.google.com/adwords/api/docs/guides/reporting#multiple_attribution> >>> report >>> (or criteria-type specific report) like AUDIENCE_PERFORMANCE_REPORT >>> <https://developers.google.com/adwords/api/docs/appendix/reports/audience-performance-report> >>> instead. >>> However, the data for CUSTOM_AFFINITY is not returned in that report yet. >>> I'm following up with engineering to see if we can return data >>> for CUSTOM_AFFINITY in AUDIENCE_PERFORMANCE_REPORT in the near future. >>> Unfortunately, we don't have ETA for this yet. >>> >>> Cheers, >>> Thanet, AdWords API Team >>> >>> On Thursday, September 15, 2016 at 7:07:48 PM UTC+9, Igor Selitskiy >>> wrote: >>>> >>>> Guys, are you sure? >>>> see https://developers.google.com/adwords/api/docs/reference/#whats-new >>>> version v201601 point whats-new >>>> : >>>> "Improvements to reports >>>> >>>> The list of possible enum values for the CriteriaType field on the >>>> CRITERIA_PERFORMANCE_REPORT >>>> <https://developers.google.com/adwords/api/docs/appendix/reports/criteria-performance-report#criteriatype> >>>> has >>>> expanded to include: >>>> >>>> - PARENT - Parental status >>>> - CUSTOM_AFFINITY - Custom affinity" >>>> >>>> >>>> >>>> On Thursday, September 15, 2016 at 11:27:06 AM UTC+3, Thanet Knack >>>> Praneenararat (AdWords API Team) wrote: >>>>> >>>>> Hi Igor, >>>>> >>>>> No. I meant the data itself is not available in AdWords API, not >>>>> related to any client libraries. >>>>> >>>>> Cheers, >>>>> Thanet, AdWords API Team >>>>> >>>>> On Thursday, September 15, 2016 at 4:42:31 PM UTC+9, Igor Selitskiy >>>>> wrote: >>>>>> >>>>>> Feature request? >>>>>> >>>>>> Do you mean that Python library has separate from main API feature >>>>>> list? >>>>>> >>>>>> On Thursday, September 15, 2016 at 9:14:26 AM UTC+3, Thanet Knack >>>>>> Praneenararat (AdWords API Team) wrote: >>>>>>> >>>>>>> Hi Igor, >>>>>>> >>>>>>> Yes, but the data is not fed into that criteria type yet. >>>>>>> That's why you're not seeing anything. >>>>>>> >>>>>>> I know that this is confusing to you. >>>>>>> I've given feedback to engineering as a feature request already. >>>>>>> >>>>>>> Apologize for this inconvenience. >>>>>>> >>>>>>> Best, >>>>>>> Thanet, AdWords API Team >>>>>>> >>>>>>> On Thursday, September 15, 2016 at 3:10:09 PM UTC+9, Igor Selitskiy >>>>>>> wrote: >>>>>>>> >>>>>>>> There is anounce of this criteria type in criteria performance >>>>>>>> report in API v201601. >>>>>>>> >>>>>>>> 15 сент. 2016 г. 9:06 AM пользователь написал: >>>>>>>> >>>>>>>> It's already supported by API itself, but isn't supported by Python >>>>>>>> library. Do you mean there is no support in Python library yet? >>>>>>>> >>>>>>>> 15 сент. 2016 г. 8:57 AM пользователь "'Thanet Knack Praneenararat >>>>>>>> (AdWords API Team)' via AdWords API Forum" < >>>>>>>> adwor...@googlegroups.com> написал: >>>>>>>> >>>>>>>> Hello Igor, >>>>>>>> >>>>>>>> There are no support for this criteria type in AdWords API yet. >>>>>>>> I'm not aware of the plan to support this in the near future. >>>>>>>> >>>>>>>> For the release announcement, you can follow our announcements >>>>>>>> <https://groups.google.com/forum/#!forum/adwordsapi-announcements> >>>>>>>> thread. >>>>>>>> >>>>>>>> Best, >>>>>>>> Thanet, AdWords API Team >>>>>>>> >>>>>>>> On Wednesday, September 14, 2016 at 2:04:12 AM UTC+9, Shwetha >>>>>>>> Vastrad (AdWords API Team) wrote: >>>>>>>>> >>>>>>>>> Hi Igor, >>>>>>>>> >>>>>>>>> Could you provide the complete report definition you are using to >>>>>>>>> download report data along with a sample report in which the custom >>>>>>>>> affinity audience criteria are missing? Please use *Reply >>>>>>>>> privately to author* when responding. >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Shwetha, 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 adwor...@googlegroups.com >>>>>>>> To unsubscribe from this group, send email to >>>>>>>> adwords-api...@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 a topic in >>>>>>>> the Google Groups "AdWords API Forum" group. >>>>>>>> To unsubscribe from this topic, visit >>>>>>>> https://groups.google.com/d/topic/adwords-api/jbW1WQ1iWoM/unsubscribe >>>>>>>> . >>>>>>>> To unsubscribe from this group and all its topics, send an email to >>>>>>>> adwords-api...@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/7cbdad6c-61c8-426b-a20e-823f9ea63ffa%40googlegroups.com >>>>>>>> >>>>>>>> <https://groups.google.com/d/msgid/adwords-api/7cbdad6c-61c8-426b-a20e-823f9ea63ffa%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>> . >>>>>>>> >>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> __________________________________________________________________________ >>>>>>>> CONFIDENTIALITY NOTICE: The information contained in the present >>>>>>>> message (including any information contained in attachments herein) >>>>>>>> may be >>>>>>>> confidential and privileged. It may be read, copied and used only by >>>>>>>> the >>>>>>>> intended recipient. If you have received it in error please contact >>>>>>>> the >>>>>>>> sender (by return e-mail) immediately and delete this message. Any >>>>>>>> unauthorized use or dissemination of this message in whole or in parts >>>>>>>> is >>>>>>>> strictly prohibited. Print this message only if sharp necessary. >>>>>>>> УВЕДОМЛЕНИЕ О КОНФИДЕНЦИАЛЬНОСТИ: Информация, содержащаяся в >>>>>>>> настоящем сообщении (включая любое вложение) может быть >>>>>>>> конфиденциальной и >>>>>>>> охраняться действующим законодательством. Сообщение может быть >>>>>>>> прочитано, >>>>>>>> скопировано и использовано исключительно лицом, которому сообщение >>>>>>>> предназначается. Если Вы получили настоящее сообщение по ошибке, >>>>>>>> пожалуйста, незамедлительно сообщите об этом отправителю (ответным >>>>>>>> письмом >>>>>>>> по электронной почте). Любое несанкционированное использование или >>>>>>>> распространение информации, содержащейся в настоящем сообщении в целом >>>>>>>> или >>>>>>>> в части, строго запрещены. Не распечатывайте настоящее сообщение, если >>>>>>>> в >>>>>>>> этом нет крайней необходимости. >>>>>>>> >>>>>>> -- __________________________________________________________________________ CONFIDENTIALITY NOTICE: The information contained in the present message (including any information contained in attachments herein) may be confidential and privileged. It may be read, copied and used only by the intended recipient. If you have received it in error please contact the sender (by return e-mail) immediately and delete this message. Any unauthorized use or dissemination of this message in whole or in parts is strictly prohibited. Print this message only if sharp necessary. УВЕДОМЛЕНИЕ О КОНФИДЕНЦИАЛЬНОСТИ: Информация, содержащаяся в настоящем сообщении (включая любое вложение) может быть конфиденциальной и охраняться действующим законодательством. Сообщение может быть прочитано, скопировано и использовано исключительно лицом, которому сообщение предназначается. Если Вы получили настоящее сообщение по ошибке, пожалуйста, незамедлительно сообщите об этом отправителю (ответным письмом по электронной почте). Любое несанкционированное использование или распространение информации, содержащейся в настоящем сообщении в целом или в части, строго запрещены. Не распечатывайте настоящее сообщение, если в этом нет крайней необходимости. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/9d3f6a80-94ab-4449-b3d3-d386cde2d692%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
