Hi Mike,

I know it's been a while, but I was reviewing this feature request and 
realized that I had not suggested using the URL_PERFORMANCE_REPORT 
<https://developers.google.com/adwords/api/docs/appendix/reports/url-performance-report>.
 
That won't give you GCLID-level details, but it will allow you to see the 
full placement URL (in the Url field 
<https://developers.google.com/adwords/api/docs/appendix/reports/url-performance-report#url>)
 
for your impressions. Would that address your use case?

Thanks,
Josh, AdWords API Team

On Friday, February 17, 2017 at 5:09:24 PM UTC-5, Josh Radcliff (AdWords 
API Team) wrote:
>
> Hi Mike,
>
> Appreciate the feedback! I'm not sure if your request is on the roadmap, 
> so I passed it along.
>
> Cheers,
> Josh, AdWords API Team
>
> On Friday, February 17, 2017 at 11:46:59 AM UTC-5, Mike-Indiana wrote:
>>
>> Hi Josh,
>>
>> I certainly appreciate you looking into this. Your response is great to 
>> clarify what we should expect to receive in both valuetrack and reports.
>>
>> I'm not sure if it's on the plate, but it would be helpful to pass the 
>> full URL in ValueTrack and report data (if no-one asks, then no-one may 
>> know).
>>
>> Thank you,
>>
>> Mike
>>
>>
>> On Friday, February 17, 2017 at 11:37:02 AM UTC-5, Josh Radcliff (AdWords 
>> API Team) wrote:
>>>
>>> Hi Mike,
>>>
>>> Thanks for bearing with me while I gathered info on this question. I've 
>>> heard back from the Display network experts, and they informed me that the 
>>> ValueTrack {placement} will be populated as follows:
>>>
>>>    - Managed placements 
>>>    <https://support.google.com/adwords/answer/2470108>: the URL as 
>>>    specified on the placement criterion's url attribute 
>>>    
>>> <https://developers.google.com/adwords/api/docs/reference/v201609/AdGroupCriterionService.Placement#url>
>>>    .
>>>    - Automatic placements 
>>>    <https://support.google.com/adwords/answer/99463>: the full host 
>>>    name of the placement
>>>
>>> In reports and the user interface, *automatic placements* are displayed 
>>> using the *second level domain*, e.g., for {placement} of 
>>> news.domain.com, reports and the user interface will show domain.com.
>>>
>>> I plan to update our documentation to reflect this, but first could you 
>>> confirm that what I described above matches what you're seeing?
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Wednesday, February 8, 2017 at 3:38:55 PM UTC-5, Josh Radcliff 
>>> (AdWords API Team) wrote:
>>>>
>>>> Hi Mike,
>>>>
>>>> Thanks for providing the example re: subdomains. I've passed that along 
>>>> to the engineer looking into this. I'll let you know as soon as I have 
>>>> more 
>>>> info.
>>>>
>>>> Cheers,
>>>> Josh, AdWords API Team
>>>>
>>>> On Wednesday, February 8, 2017 at 1:42:00 PM UTC-5, Mike-Indiana wrote:
>>>>>
>>>>> Sorry for the multiple messages on this. I am seeing that sub-domains 
>>>>> are not being passed in ValueTrack placement clicks, just the domain. 
>>>>> This 
>>>>> must have changed within the past year or so, can you confirm?
>>>>>
>>>>> Thanks again.
>>>>>
>>>>> On Wednesday, February 8, 2017 at 1:19:37 PM UTC-5, Mike-Indiana wrote:
>>>>>>
>>>>>> Hi Josh,
>>>>>>
>>>>>> One more thing. I noticed that subdomains do not exist in the reports 
>>>>>> either. For example, news.domain.com will come in from {placement} 
>>>>>> in ValueTrack, but only domain.com in the reports.
>>>>>>
>>>>>> Thank you,
>>>>>>
>>>>>> Mike
>>>>>>
>>>>>> On Friday, January 13, 2017 at 9:36:43 AM UTC-5, Josh Radcliff 
>>>>>> (AdWords API Team) wrote:
>>>>>>>
>>>>>>> Hi Mike,
>>>>>>>
>>>>>>> No word yet, but I'll keep asking for updates. I'll let you know as 
>>>>>>> soon as I hear back.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Josh, AdWords API Team
>>>>>>>
>>>>>>> On Thursday, January 12, 2017 at 3:25:55 PM UTC-5, Mike-Indiana 
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hi Josh, any word back on this?
>>>>>>>>
>>>>>>>> Thank you,
>>>>>>>>
>>>>>>>> Mike
>>>>>>>>
>>>>>>>> On Wednesday, January 4, 2017 at 10:13:37 PM UTC-5, Josh Radcliff 
>>>>>>>> (AdWords API Team) wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> Thanks for sending over the example. While looking into this, I 
>>>>>>>>> found that one of my colleagues already asked this question, so I'm 
>>>>>>>>> following up with him. I'll send you an update as soon as I have more 
>>>>>>>>> information.
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> Josh, AdWords API Team
>>>>>>>>>
>>>>>>>>> On Wednesday, January 4, 2017 at 11:42:17 AM UTC-5, Mike-Indiana 
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Private reply sent. Thank you Josh
>>>>>>>>>>
>>>>>>>>>> On Wednesday, January 4, 2017 at 9:06:46 AM UTC-5, Josh Radcliff 
>>>>>>>>>> (AdWords API Team) wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> Could you pass along a campaign ID, date range, and domains 
>>>>>>>>>>> where you are seeing the discrepancy so I can investigate further?
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Josh, AdWords API Team
>>>>>>>>>>>
>>>>>>>>>>> On Tuesday, January 3, 2017 at 10:51:33 PM UTC-5, Mike-Indiana 
>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hello, this discrepancy seems to have existed for several 
>>>>>>>>>>>> years, I thought that I would post.
>>>>>>>>>>>>
>>>>>>>>>>>> Pulling AUTOMATIC_PLACEMENTS_PERFORMANCE_REPORT will yield 
>>>>>>>>>>>> non-www. domains in the report for 'Domain'. For example, 
>>>>>>>>>>>> google.com
>>>>>>>>>>>>
>>>>>>>>>>>> However when using valuetrack {placement} in ads, a click may 
>>>>>>>>>>>> yield either google.com or www.google.com. However in the 
>>>>>>>>>>>> reports, it will not return the www. version and assign the click 
>>>>>>>>>>>> data to 
>>>>>>>>>>>> the other.
>>>>>>>>>>>>
>>>>>>>>>>>> *In short*, it would be kind if the API placements report 
>>>>>>>>>>>> would reflect the same variable as valuetrack. Has anyone else 
>>>>>>>>>>>> noticed 
>>>>>>>>>>>> this, or is it an issue on my setup?
>>>>>>>>>>>>
>>>>>>>>>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/a58fd938-89c3-4312-8021-ff97838a3b8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  • Re: Report from A... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum

Reply via email to