Hi Jonathan, I probably should have explained a little further. The fields that you see in the API also exist in the UI, which is why you can get help from general AdWords support as well. For example, the Placement report also maps to the UI. Our documentation has a section <https://developers.google.com/adwords/api/docs/guides/uireports#managed_placements_report> in our Mapping Report to the AdWords UI guide <https://developers.google.com/adwords/api/docs/guides/uireports#managed_placements_report> on how that mapping works. That means it's not just an API issue. It's more of a product issue because people would be struggling with the same kind of issue in the UI as well.
Unfortunately, I don't have the answer to your focused question because there are so many caveats that aren't API specific. That's why I'm trying to direct you to other avenues that most likely would have the answer. Best, Nadine, AdWords API Team On Thursday, October 12, 2017 at 8:42:34 AM UTC-4, Jonathan Clarke wrote: > > Hi Nadine, > > Thanks for looking into this. I do feel our question is directly relevant > to the AdWords API. We only want to map API data to ValueTrack data. Please > allow me to re-phrase and focus the question: > > How do we map AdWords mobile app placement data from the API to ValueTrack? > > Best Regards, > Jonathan Clarke > > On Wednesday, October 11, 2017 at 5:21:35 PM UTC-4, Nadine Sundquist > (AdWords API Team) wrote: >> >> Hello Jonathan, >> >> I have a feeling that part of the differences are appearing because of >> this: >> >> - The content site where your ad was clicked (for keyword-targeted >> campaigns), or the matching placement targeting criteria for the site >> where >> your ad was clicked (for placement-targeted campaigns). >> >> I've searched around for a clear-cut answer for your particular >> situation, since I haven't bumped into this particular issue before, but I >> can't seem to find the perfect solution. I'm looking at the problem you're >> trying to solve, and I'm wondering if Google Analytics >> <https://developers.google.com/analytics/> might be a good fit for you >> because it can tie a lot of this kind of information together. Have you >> looked into that? >> >> Another avenue you could try is posting on the general AdWords Community >> forum >> <https://www.en.advertisercommunity.com/t5/Google-AdWords/ct-p/Google_AdWords>. >> >> This same issue would also show up in reporting in the UI, so they may >> already have an answer for you. Could you also give that a try? At this >> point, it's more of a general AdWords problem to solve than intrinsic to >> the API, so at least there are other support channels you can try like that >> one. >> >> Regards, >> Nadine, AdWords API Team >> >> On Wednesday, October 11, 2017 at 11:11:03 AM UTC-4, Jonathan Clarke >> wrote: >>> >>> Hi Nadine! >>> >>> Sorry for the delay, I didn't get a notification about your reply. >>> >>> To illustrate further: >>> >>> We have an example where ValueTrack {placement} reported the following >>> value: *411092.iphone.com.weather.twcipadmax.adsenseformobileapps.com >>> <http://411092.iphone.com.weather.twcipadmax.adsenseformobileapps.com>*. >>> >>> But the AdWords API reports fields (PlacementPerformanceReport.Criteria, >>> CriteriaPerformanceReport.Criteria, >>> AutomaticPlacementsPerformanceReport.DisplayName and >>> UrlPerformanceReport.domain or url) all returned it as >>> *mobileapp::1-364252504*. >>> >>> The only way we were able to figure out the relationship between the two >>> was because they happened to be our two biggest unmatched fields from each >>> data set, but we have many other fields that we can't figure out like that. >>> >>> How can we consistently map *xxxx.adsenseformobileapps.com >>> <http://xxxx.adsenseformobileapps.com>* from ValueTrack to *mobileapp::* >>> from AdWords reports? >>> >>> And just to make things a little more interesting... >>> >>> Sometimes ValueTrack gives us *xxx.adsenseformobileapps.com >>> <http://xxx.adsenseformobileapps.com>* format placements but other >>> times it gives us in the *mobileapp::* format we can actually match to >>> the AdWords reports. So some placements can be mapped and others can't. >>> >>> On Tuesday, October 10, 2017 at 11:14:39 AM UTC-4, Nadine Sundquist >>> (AdWords API Team) wrote: >>>> >>>> Hello Jonathan, >>>> >>>> Unfortunately, I don't know of a set workflow, but I do have a couple >>>> of resources to help you out. >>>> >>>> It looks like you may have found our Mapping ValueTrack Parameters to >>>> Report Fields >>>> <https://developers.google.com/adwords/api/docs/guides/valuetrack-mapping> >>>> guide >>>> as you were mapping the ValueTrack parameter to our report fields. >>>> >>>> What you're seeing are criteria prefixes. We have a list of them here >>>> <https://developers.google.com/adwords/api/docs/guides/reporting#criteria_prefixes>. >>>> >>>> Please try taking a look at those to see if they match what you're seeing. >>>> If you need further help, feel free to reach out. >>>> >>>> Cheers, >>>> Nadine, AdWords API Team >>>> >>>> On Monday, October 9, 2017 at 5:59:07 PM UTC-4, Jonathan Clarke wrote: >>>>> >>>>> We've been working successfully with the AdWords API (Google Ads >>>>> Python Client Library: >>>>> https://github.com/googleads/googleads-python-lib) for a good while >>>>> building internal reports for our application. Until, that is, we hit >>>>> placements… >>>>> >>>>> I define placements as anywhere an AdWords ad is shown. The placement >>>>> might be a domain, page, ad unit, app you name it! Placements are a very >>>>> broad definition. >>>>> >>>>> For our app to work for placements we need to join API spend data with >>>>> activity on our website. >>>>> >>>>> To do this we are running AdWords API reports and then collecting >>>>> session data using AdWords ValueTrack parameters. >>>>> >>>>> The ValueTrack parameters are easy enough, as there seems to be only 1 >>>>> option: `{placement}`. >>>>> >>>>> However, it's on the API where things get interesting, the API has >>>>> numerous options for getting placement data. For example: >>>>> >>>>> - >>>>> >>>>> https://developers.google.com/adwords/api/docs/reference/v201708/AdGroupCriterionService.MobileApplication >>>>> >>>>> >>>>> - >>>>> >>>>> https://developers.google.com/adwords/api/docs/appendix/reports/url-performance-report >>>>> - >>>>> >>>>> https://developers.google.com/adwords/api/docs/appendix/reports/placement-performance-report#criteria >>>>> - >>>>> >>>>> https://developers.google.com/adwords/api/docs/appendix/reports/automatic-placements-performance-report#domain >>>>> - >>>>> >>>>> https://developers.google.com/adwords/api/docs/reference/v201708/AdGroupCriterionService >>>>> >>>>> After spending some time going back and forth on the various options, >>>>> and burning lots of dev time, we've come to the conclusion that there >>>>> must >>>>> be some best practice advice out there for joining placement data from >>>>> the >>>>> API and ValueTrack. One that works for all types of placements, including: >>>>> >>>>> - Websites >>>>> - Apps >>>>> - AdSense >>>>> - Blogspot >>>>> - AMP >>>>> >>>>> An example of where we are running into a matching problem is " >>>>> 10060.android.com.nytimes.android.adsenseformobileapps.com"... this >>>>> is a placement we see coming in from ValueTrack but has no match in any >>>>> of >>>>> our spend reports. (In fact there are many many >>>>> adsenseformobileapps.com traffic sources for which there are no spend >>>>> items). >>>>> >>>>> Also seeing strings like "mobileapp::2-com.mobilesrepublic.appy". >>>>> These show up on our spend side but only appear in our ValueTrack around >>>>> 10% of the time. Some match. The vast majority don't. >>>>> >>>>> A definitive workflow on this would be SO useful for ourselves and no >>>>> doubt other users… >>>>> >>>>> Thanks! >>>>> >>>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/f34f47c4-3b57-48b4-9eea-6d5de5da3d82%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
