Impressions data doesn't match after migration to Google Ads API

[Margarita Veshtort]

Hi,

I was migrating the URL Performance report mentioned here  https://ads-developers.googleblog.com/2021/06/deprecating-url-performance-report-and.html and i can see that  Google Ads API returns different metric values rather than the old report type. 

For the AdWards api SELECT DisplayName Impressions FROM URL_PERFORMANCE_REPORT

And detail_placement_view.display_name field + impressions were requested from detail_placement_view

[Google Ads API Forum Advisor]

Hi Margarita,

"SELECT detail_placement_view.display_name, metrics.impressions FROM detail_placement_view" is the correct translation. There may be discrepancies based on some factors, if you send us privately your full request/response logs from both API's we can determine why.

Regards,

Aryeh Baker Google Ads API Team

ref:_00D1U1174p._5004Q2JWnSj:ref

[Margarita Veshtort]

Hi,

I'm sorry for such a late reply, your email went to spam for some reason. 

Below you can see 2 requests one to Ads API and another to adwards API.

Request
https://googleads.googleapis.com/v6/customers/8733197711/googleAds:search
{
    "query": "SELECT metrics.impressions,detail_placement_view.display_name FROM detail_placement_view WHERE segments.date BETWEEN '2021-06-19' AND '2021-06-20'",
    "page_size": 10000
}

Request
https://adwords.google.com/api/adwords/reportdownload/v201809
query=SELECT+DisplayName%2C+Impressions+FROM+URL_PERFORMANCE_REPORT+DURING+20210619%2C20210620&__fmt=TSV

Response
And here the result set where Placement URL is a DisplayName. It's not so critical that DisplayName values do not match but where it matches impressions values do not match at all. 


Thank you!

--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
 
You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads API Forum" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/adwords-api/5WR0wgSpqAk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to adwords-api...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/Pqda2000000000000000000000000000000000000000000000QVHCI400cIdghGknSK6MdVhnI0Ng7Q%40sfdc.net.

[Google Ads API Forum Advisor]

Hi Margarita,

Thank you for sending over additional information.

Before I raise the discrepancy issue to the rest of our team, could you also provide the complete request and response logs, and request-id of your Google Ads API report request?

If you haven't yet, logging can be enabled by navigating to the Client libraries > Your client library (ex. Java) > Logging documentation, which you can access from this link.

You may then send the requested information via the Reply privately to author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias instead.

Best regards,

Peter Laurence Napa Oliquino Google Ads API Team

ref:_00D1U1174p._5004Q2JWnSj:ref

[Muhsen Hawlere]

--

--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
 
You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 the Google Groups "AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/j6F50000000000000000000000000000000000000000000000QX1CP100L6kVux9AQn2db17pQ6877A%40sfdc.net.

[Google Ads API Forum Advisor]

Hi Mushen,

Thank you for raising your concern.

Could you confirm if you have the same issue with what was initially posted on this forum post? If yes, then please provide the information below that my colleague has requested to further investigate the issue.

"Thank you for sending over additional information.

Before I raise the discrepancy issue to the rest of our team, could you also provide the complete request and response logs, and request-id of your Google Ads API report request?

If you haven't yet, logging can be enabled by navigating to the Client libraries > Your client library (ex. Java) > Logging documentation, which you can access from this link.

You may then send the requested information via the Reply privately to author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias instead."

Regards,

Ernie John Blanca Tacata Google Ads API Team

ref:_00D1U1174p._5004Q2JWnSj:ref

[Google Ads API Forum Advisor]

Hello Margarita,

We received an update from our team regarding those discrepancies. See below:

The reason there's a difference between the two (URL Performance Report against the detail_placement_view) is because Url Performance Report is a single attribution report. This means that one criterion is picked to be given credit for the click or view. In some cases, one URL may not be given credit because another criterion elsewhere was given all the credit.

The whole Google Ads API does not use single attribution because we found it can be confusing, so each view will show every single criterion that was in play at the time, which gives more of an all encompassing picture of what was being used while serving.

This is working as intended, and it's expected that there will be some differences between the two reports since attribution is done differently.

Regards,

Mark Kevin Albios Google Ads API Team

ref:_00D1U1174p._5004Q2JWnSj:ref