differences between Overview and API for conversions metric

[Olivier Clémence]

Hello,

i don't understand something.

Every night at 3:00 AM i call the API to get data using this query : 
"SELECT
                    segments.date,
                    campaign.advertising_channel_type,
                    campaign.id,
                    metrics.cost_micros,            
                    metrics.clicks,            
                    metrics.impressions,            
                    metrics.ctr,            
                    metrics.cost_per_conversion,            
                    metrics.conversions,            
                    metrics.average_cpc,            
                    metrics.average_cpm
                FROM
                    campaign
                WHERE
                    segments.date >= '" . $startDate . "'
                AND
                    segments.date <= '" . $endDate . "'
                ORDER BY
                    segments.date";

Where startDate and endDate are identical and representing the day before.
Someday everything is ok but sometimes conversions are not accurate.

For example, on 2024-01-06 the the overview display 4.18 for one of my campaign and the api got me 4.019

But, today if i call again the api on the same day (2024-01-06) it got me the right value : 4.18

How is that possible, and why ? Do you have explanation and a solution to fix this ? 

[Google Ads API Forum Advisor]

Hi,

Thank you for contacting the Google Ads API support team.

By reviewing your concern, I understand that you have encountered data discrepancy in the campaign. Kindly provide us with the complete API logs (request and response with request-id and request header) generated at your end and uncropped UI screenshot with better visibility of the customer ID of where you are facing the discrepancies.

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.!5004Q02ryrBf:ref"

Thanks,
 

Google Ads API Team

 

[Olivier Clémence]

hello i can't have logs because my server do not accept grpc extension for php.
There is another solution ?

[Google Ads API Forum Advisor]

Hi,

Thank you for getting back to us.

Kindly note that uploaded conversions can take up to 24 hours for conversions to show up in Google Ads, depending on the attribution model you are using. Please refer to this article About data freshness for more information.

If you still observe the data discrepancy on uploading conversions even after 24 hours, kindly provide us with the complete API logs (request and response with request-id and request header) generated at your end and uncropped UI screenshot with better visibility of the customer ID of where you are facing the discrepancies. Without the complete logs, it would be difficult to analyze the issue for us.

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 guide PHP to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.