Landing page view API data not matching with GoogleAds UI

[rahul...@decision-tree.com]

Hello,

We are trying to get landing page view data using google ads API but the data is not matching with the UI. 

E.g for the date 2023-10-24, this is what we get from API:

click: 405

impressions: 50644

cost: $1372.31

And in the API, data for the same day shows:

click: 488

impressions: 50644

cost: $1,717.05

For reference, the query looks like this:

SELECT   segments.date,metrics.impressions,metrics.cost_micros,metrics.clicks,landing_page_view.unexpanded_final_url,landing_page_view.resource_name,campaign.advertising_channel_type,campaign.id,campaign.name,campaign.status
            FROM landing_page_view
            WHERE metrics.impressions > 0 AND segments.date between '2023-10-21' and '2023-10-23';

Can you guys help us understand why is this so? Thanks

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.

By reviewing your concern, I understand that you are retrieving data from the landing_page_view resource, and you've noticed disparities between the information displayed in the Google Ads user interface and what is obtained through the Google Ads API. Kindly note that the Google Ads API mirrors the Google Ads UI. We would like to specify first the following when comparing the value of the Google Ads UI and the Google Ads API.

• The segments and fields of the API and UI should be the same.
• The date range should also be the same.
• Comparing the API and UI at the same level as possible.

With that, please provide us with the complete API logs (request and response with request-id and request header) generated at your end and uncropped UI screenshot of the Google Ads account where you are facing the issue.

If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.

You can send the details via Reply privately to the author option, or direct private reply to this email.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02q9ct2:ref"

Thanks,
 

Google Ads API Team

[Dominik Raffetseder]

Is there a Solution?

Regards,
Dominik

[Google Ads API Forum Advisor]

Hello - 

Unfortunately there isn't a resolution here yet. The team is still investigating, and I'll follow up here with more details as soon as possible.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02q9ct2:ref"

Thanks,
 

Ben Karl Google Ads API Team

[rahul...@decision-tree.com]

Guys,

Any updates on this? Waiting for any resolution possible. Thanks

[Google Ads API Forum Advisor]

Hi All - 

The engineering team is still investigating this one, unfortunately. I'm checking in with them to see what we can do to get this expedited. I'll let you know as soon as I have more information.

[Rahul Kumar]

Hi Ben,

Thank you for the information. Actually we have a client who is waiting on this so any new info would be helpful to us. 

Regards,

Rahul

[Google Ads API Forum Advisor]

Hi Rahul,

Thanks for the details. I'm coordinating directly with the assigned engineer, who has told me this is their priority, so I'm hoping to have more details today.

[Dominik Raffetseder]

Are there any news?

[Google Ads API Forum Advisor]

Hi Dominik,

The engineering team is still working on the issue. Right now they're working through our logs for more details. Unfortunately things are still ongoing so I don't have an update yet, but will let you know when I have more details.