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/2eab4a89-4d87-40ae-a5d8-175a66fdf15f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  • Best practice ... Jonathan Clarke
    • Re: Best ... 'Nadine Sundquist (AdWords API Team)' via AdWords API Forum
      • Re: B... Jonathan Clarke
        • R... 'Nadine Sundquist (AdWords API Team)' via AdWords API Forum
          • ... Jonathan Clarke
            • ... 'Nadine Sundquist (AdWords API Team)' via AdWords API Forum
              • ... Jonathan Clarke
                • ... 'Nadine Sundquist (AdWords API Team)' via AdWords API Forum
                • ... Jonathan Clarke
                • ... 'Nadine Sundquist (AdWords API Team)' via AdWords API Forum
                • ... Jonathan Clarke

Reply via email to