Re: Discrepancy between API and UI for bidding_strategy

Hello, Glad to see that substituting those attributes got the desired results. If you aren't having any other issues, there is no need to send the request and response -- sometimes it can be necessary to get a full picture of the request. Regards, Matt Google Ads API Team Matt Google Ads API

Re: Discrepancy between API and UI for bidding_strategy

Hello Matt, I just found a solution - instead of using `bidding_strategy.type`, `bidding_strategy.name` in the query, I just used `campaign.bidding_strategy_type`, `campaign.bidding_strategy`, and got the correct output, so I have what I need. However, if you'd like to proceed with further

RE: Discrepancy between API and UI for bidding_strategy

Hello, Thanks for reaching out. Can you please reply to us privately with your complete request and response logs? As the message will be private, you won't need to redact any of the IDs, which our team can use to troubleshoot. Regards, Matt Google Ads API Team Matt Google Ads API Team

Re: Discrepancy between API and UI for bidding_strategy

Additional info - I just successfully updated a shopping campaign through the Google Ads API to switch to tROAS with specified value, and I saw the campaign Target ROAS change in the Google Ads UI. However, when I queried the Google Ads API for the same campaign, I again get "Unspecified"

Re: discrepancy between API and UI

Hello, I apologize for the slow response again. The team seems to have identified the underlying issue but we're still working on exactly how we want to handle it. I will update here when I have more information to share. Regards, Mike, AdWords API Team On Wednesday, December 26, 2018 at

Re: discrepancy between API and UI

Hey, just wanted to follow up. Is there any update on this issue? On Monday, November 19, 2018 at 10:47:39 AM UTC-5, Michael Cloonan (AdWords API Team) wrote: > > Hello, > > I'm sorry for the slow response time here. I've reached out again to try > to get a status update, and will let you know

Re: discrepancy between API and UI

ok. cool. Thanks you! On Monday, November 19, 2018 at 10:47:39 AM UTC-5, Michael Cloonan (AdWords API Team) wrote: > > Hello, > > I'm sorry for the slow response time here. I've reached out again to try > to get a status update, and will let you know as soon as I find out > anything. > >

Re: discrepancy between API and UI

Hello, I'm sorry for the slow response time here. I've reached out again to try to get a status update, and will let you know as soon as I find out anything. Regards, Mike, AdWords API Team On Monday, November 19, 2018 at 10:18:14 AM UTC-5, Xiaoyun Yang wrote: > > Hello, > > Just want to

Re: discrepancy between API and UI

Hello, Just want to follow up to see what's the status for this issue - Thanks On Wednesday, November 7, 2018 at 2:21:03 PM UTC-5, Xiaoyun Yang wrote: > > That would be greatly appreciated. Thank you! > > On Wednesday, November 7, 2018 at 2:01:11 PM UTC-5, Michael Cloonan > (AdWords API Team)

Re: discrepancy between API and UI

That would be greatly appreciated. Thank you! On Wednesday, November 7, 2018 at 2:01:11 PM UTC-5, Michael Cloonan (AdWords API Team) wrote: > > Hello, > > Thanks for the screenshot! I am going to investigate and get in touch with > the team in charge of this column to try to figure out why it's

Re: discrepancy between API and UI

Hello, Thanks for the screenshot! I am going to investigate and get in touch with the team in charge of this column to try to figure out why it's showing in the web interface but not in the API. I will let you know when I have any information to share. Regards, Mike, AdWords API Team On

Re: discrepancy between API and UI

I just sent a screenshot to you. Thanks very much for taking a look! On Wednesday, November 7, 2018 at 12:40:50 PM UTC-5, Michael Cloonan (AdWords API Team) wrote: > > Hello, > > Can you include a screenshot that has more context, including column names > and filters, to help us investigate?

Re: discrepancy between API and UI

Hello, Can you include a screenshot that has more context, including column names and filters, to help us investigate? You can reply privately to me rather than post publicly by using the drop-down arrow at the top-right of my post. Regards, Mike, AdWords API Team On Wednesday, November 7,

Fwd: Data discrepancy between API and UI

-- Forwarded message - From: Xiaoyun Yang Date: Tue, Nov 6, 2018 at 2:58 PM Subject: Data discrepancy between API and UI To: Trying to get the search lost is (rank) from adgroup performance report; But most of my ad groups, even high performance groups get undefined search lost

discrepancy between API and UI

Trying to get the search lost is (rank) from adgroup performance report; But most of my ad groups, even high performance groups get undefined search lost is while the UI shows actual numbers. The query I am using is: SELECT CampaignId, AdGroupId, Device, Date, AveragePosition, Impressions, >

Re: Traffic estimator service: discrepancy between API and UI results

Hello All, Should I get Results same as UI using TrafficEstimatorService, If yes, How I can get Top Estimated results like clicks, impressions, cost etc.. which is set under daily forecast and there predictions like Clicks 185 – 226 Is this value possible using API? Also Is all platform

Re: Traffic estimator service: discrepancy between API and UI results

Hi, If you haven't done so already, I'd recommend checking out our Estimating Traffic guide , which gives a nice overview of the service including how the various API options map to the Keyword Planner tool.

Re: Traffic estimator service: discrepancy between API and UI results

Joao, Could I trouble you to send me the full SOAP request/response log (with sensitive information removed) using the Reply to Author feature? Secondly, for the same criteria, could I trouble you to also send me the result you get in the UI? This will help me investigate this question

Re: Discrepancy between API and UI Cost Data - Placement Performance Report

Hi Charlie, I know that supporting app placement data via the API is something we want to do, but unfortunately I cannot provide any kind of estimate as to when that would be available. We announce new features on our bloghttp://googleadsdeveloper.blogspot.com/, so subscribing to that will

Re: Discrepancy between API and UI Cost Data - Placement Performance Report

Mike, That's quite alright, thank you for your response. If possible, could give me an approximate timeline as to when we will be able to get mobile app placement data via the API, please? Thanks again, Charlie On Monday, January 13, 2014 9:48:29 AM UTC-5, Michael Cloonan (AdWords API Team)

Traffic estimator service: discrepancy between API and UI results

Hi all, I am using the most recent version of Adwords API (v201309) and I am having problems with Traffic Estimator service. When I perform the a query through API, results don't match with UI. For example, I want to do a query to find the estimated traffic for the keyword sapato masculino

Re: Discrepancy between API and UI Cost Data - Placement Performance Report

Hi Charlie, This looks like it's probably because the Placement Performance Reporthttps://developers.google.com/adwords/api/docs/appendix/reports#placementis a multi-attribution reporthttps://developers.google.com/adwords/api/docs/guides/reporting-concepts#single-and-multi-attribution.

Re: Discrepancy between API and UI Cost Data - Placement Performance Report

Hi Michael, We investigated this further, and it looks like mobile app placements are being excluded from the Placement Performance Report. In the UI, these are shown with a placement beginning with mobileapp::. Should data for mobile app placements be included in the Placement Performance

Discrepancy between API and UI Cost Data - Placement Performance Report

Hi All, We've noticed a discrepancy in the cost reported by Placement Performance Reports compared to the cost shown in the UI. I've given some examples of the data, below, to show that it is non-negligible for one client, but minimal for another, that it is present for both recent and older