Potential bug with 'metrics.phone_calls'

[Oksana Sulyma]

Hi Google Ads API team!

I observe very strange issue for one client of us and DISCOVERY Campaign. 

I work with https://developers.google.com/google-ads/api/fields/v14/campaign report.

If I have https://developers.google.com/google-ads/api/fields/v14/campaign#segments.ad_network_type in my request, I get metrics.phone_calls. If I repeat the same request with no segments.ad_network_type, I get metrics.phone_calls = 2. 

Could there be any explanation for this behaviour? 

Will be happy to share request / response logs in private messaging.

Thanks in advance for any info on this question!

Oksana

[Google Ads API Forum Advisor]

Hi,

Thank you for contacting the Google Ads API support team.

To better understand your concerns, could you please provide us with the complete API logs (request and response with request-id and request header) and uncropped error screenshots to further investigate this 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.!5004Q02q9eBl:ref"

Thanks,
 

Google Ads API Team

[Google Ads API Forum Advisor]

Hi,

Thank you for getting back to us.

We are getting the value of the "metrics.phone_calls" field as 2 in both the scenarios with segments.ad_network_type and without segments.ad_network_type our end. You can try making a request using the Method: customers.googleAds.searchStream.  

[Oksana Sulyma]

Hi team, 

Thanks for quick response. 

Sorry but I’m not sure I understand completely. 

Could you please share your request + request method? 

Is there an explanation about what is wrong with request resulted in 0 phone_calls that I’ve provided? 

Thank you!

Oksana

[Google Ads API Forum Advisor]

Hi Oksana,

Thank you for getting back to us.

We attempted to run the query using the "segments.ad_network_type" and observed that there are three adNetworkType segments: "CONTENT," "MIXED," and "YOUTUBE." Notably, the "CONTENT" segment shows 2 phone calls, while "MIXED" and "YOUTUBE" both report 0 phone calls. Could you specify which adNetworkType segment is yielding 0 phone calls from your end? Also, please provide us with the uncropped UI screenshot of the Google Ads UI where you are facing this issue.

[Google Ads API Forum Advisor]

Hi Oksana,

Thank you for getting back to us.

We have used the same query and got the results of three adNetworkType segments: "CONTENT," "MIXED," and "YOUTUBE." Notably, the "CONTENT" segment shows 2 phone calls, while "MIXED" and "YOUTUBE" both report 0 phone calls. Attaching the screenshot regarding the same results for your reference.

[Oksana Sulyma]

Hi Google Ads API team,

Thanks for your response!

I've compared my request logs (where I get 1 row with mixed network and no calls) and your screenshot (where you get 3 different networks data in response and 2 calls for Content network) and the only difference I see is in call method, please see my attachment.

We use GoogleAdsService.SearchStream method per documentation https://developers.google.com/google-ads/api/fields/v15/overview and I can say that for many years we've download millions of reports for various clients of us with no issues.

Team, could you please explain why do you use  method: customers.googleAds.searchStream, not GoogleAdsService.SearchStream to get report data? 

Isn't it a bug that customers.googleAds.searchStream and GoogleAdsService.SearchStream return different data? 

It's interesting to know that customers.googleAds.searchStream returns correct result, but at this point it's not clear to me how to resolve issue at my end as I use GoogleAdsService.SearchStream method per documentation https://developers.google.com/google-ads/api/fields/v15/overview and I get incorrect result. Please advice!

Thanks again, I reaaly appreciate collaboration in my question!

Oksana 

[Google Ads API Forum Advisor]

Hi Oksana,

Thank you for getting back to us.

Kindly note that the GoogleAdsService.SearchStream and customers.googleAds.searchStream both return all rows that match the search stream query. The Google Ads API can be called either using gRPC or REST. Both interfaces expose a resource-oriented design shared with other Google Cloud APIs. You may see this documentation on Rest Interface for more information.

[Google Ads API Forum Advisor]

Hi Oksana,

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

I see that you have already raised this concern on another thread with the subject “Potential bug with 'metrics.phone_calls'” and we have already responded there for this issue. To avoid multiple threads on the same issue, please take a look at that thread and continue the discussion on the same for further updates on the issue.

 

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

Thanks,
 

Google Ads API Team

[Oksana Sulyma]

Hi team!

Just wanted to update that the question is still actual to us.

Please let me know if you need me to provide any more details.

Thanks!

Oksana

On 6 Nov 2023, at 17:49, Oksana Sulyma <oks...@tapclicks.com> wrote:

Hi team,

Thanks for your response.

Kindly request to check my log attached.

Please explain why this query return 1 row with Network = mixed when you guys get 3 Network rows in your experiment. 

Expected result is 3 Networks, but it's not clear what is wrong with the query I run. 

From previous comparison we run the same query. Methods are different, but you say the GoogleAdsService.SearchStream and customers.googleAds.searchStream both return all rows that match the search stream query. 

So it's just not clear why I don't get expected result running my query in log and I really need your help to understand how to fix it.

Thanks a lot!

Oksana

Kindly note that the GoogleAdsService.SearchStream and customers.googleAds.searchStream both return all rows that match the search stream query.

<google-ads-with-network.log>

[Google Ads API Forum Advisor]

Hi,

Thank you for providing the logs.

In order to assist you further, could you please provide us the uncropped UI screenshot of where you're seeing the issue?

[Google Ads API Forum Advisor]

Hi Oksana,

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

I see that you have already raised this concern on another thread with the subject “Potential bug with 'metrics.phone_calls'” and we have already responded there for this issue. To avoid multiple threads on the same issue, please take a look at that thread and continue the discussion on the same for further updates on the issue.

 

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

Thanks,
 

Google Ads API Team

[Oksana Sulyma]

Hi team, my apologies, can https://groups.google.com/u/1/g/adwords-api/c/kwNWgFhy0cI/m/EHtobqPeAAAJ be closed or deleted? 

I’ve opened duplicated question after not getting answers for 7 days, and I don’t know how to delete duplicated question. 

However it seems that we are going in circles here. 

Do you want me to re-send previous correspondence on my issue here? 

Thanks,

Oksana

[Google Ads API Forum Advisor]

Hi,

Thank you for getting back to us.

As requested, we can continue our discussion on this thread only. I would like to inform you that both GoogleAdsService.SearchStream and customers.googleAds.searchStream should return the same response. GoogleAdsService.SearchStream is a service available in client libraries which is used to fetch the data and metrics across resources and you can find the request and response body of the service in the reference document, where as customers.googleAds.searchStream is the REST interface which can used to run the query using API explorer without the use of a Google-supported client library.

I would request you to provide us with the latest complete API logs using GoogleAdsService.SearchStream and customers.googleAds.searchStream, so that we can further investigate this issue further.

[Oksana Sulyma]

Hi Google Ads API team!

That’s been 6 days since my last email answer. Can you please confirm it’s in progress at your side? 

Thanks,

Oksana

On 14 Nov 2023, at 17:27, Oksana Sulyma <oks...@tapclicks.com> wrote:

Hi team,

Thanks so much for your response and sorry for delay here. 

We don’t use customers.googleAds.searchStream in our project, I’m fine with the statement that both GoogleAdsService.SearchStream and customers.googleAds.searchStream should return the same response.

Let me provide the simplest query showing issue with API response, complete fetch logs are also attached. 

1. "query":"SELECT customer.id, customer.descriptive_name, campaign.id, campaign.name, segments.ad_network_type, segments.date, metrics.impressions, metrics.clicks, metrics.phone_impressions, metrics.phone_calls FROM campaign WHERE segments.date>='2023-09-14' AND segments.date<='2023-09-14'  AND campaign.id IN (19639027572) ORDER BY segments.date DESC”

Result: 

{

    "campaign": {

        "resourceName": "customers\/7280281992\/campaigns\/19639027572",

        "id": "19639027572",

        "name": "Discovery - Inventory Expansion"

    },

    "customer": {

        "resourceName": "customers\/7280281992",

        "id": "7280281992",

        "descriptiveName": "Palmetto57 Nissan"

    },

    "metrics": {

        "clicks": "3",

        "impressions": "226",

        "phoneCalls": "0",

        "phoneImpressions": "0"

    },

    "segments": {

        "adNetworkType": "MIXED",

        "date": "2023-09-14"

    }

}

2. "query":"SELECT customer.id, customer.descriptive_name, campaign.id, campaign.name, segments.date, metrics.impressions, metrics.clicks, metrics.phone_impressions, metrics.phone_calls FROM campaign WHERE segments.date>='2023-09-14' AND segments.date<='2023-09-14'  AND campaign.id IN (19639027572) ORDER BY segments.date DESC”  (only segments.ad_network_type was removed)

Result:

{

    "campaign": {

        "resourceName": "customers\/7280281992\/campaigns\/19639027572",

        "id": "19639027572",

        "name": "Discovery - Inventory Expansion"

    },

    "customer": {

        "resourceName": "customers\/7280281992",

        "id": "7280281992",

        "descriptiveName": "Palmetto57 Nissan"

    },

    "metrics": {

        "clicks": "3",

        "impressions": "226",

        "phoneCalls": "2",

        "phoneImpressions": "0"

    },

    "segments": {

        "date": "2023-09-14"

    }

}

My question is why do we get "phoneCalls": “0” having  segments.ad_network_type in query? Expected result is "phoneCalls": “2”. 

Note we didn’t observe similar issues for other accounts we pull Google Ads API reports data for. 

Please help to understand what is wrong here.

Thanks again,

Oksana

<logs_no_network.zip>

<logs_network.zip>

[Google Ads API Forum Advisor]

Hi Oksana,

Thank you for getting back to us.

Please be informed that I have removed your response from the forums as it contains the PII information.

By reviewing your concern, I understand that you are getting issues with the “phoneCalls'' field while adding the segments.ad_network_type in the GAQL query. Could you kindly provide us the UI screenshot of the Google Ads account and highlight the fields that you want to retrieve via the API?

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

Please find your message with redacted information: 

Hi team,

Thanks so much for your response and sorry for delay here. 

We don’t use customers.googleAds.searchStream in our project, I’m fine with the statement that both GoogleAdsService.SearchStream and customers.googleAds.searchStream should return the same response.

Let me provide the simplest query showing issue with API response, complete fetch logs are also attached. 

1. "query":"SELECT customer.id, customer.descriptive_name, campaign.id, campaign.name, segments.ad_network_type, segments.date, metrics.impressions, metrics.clicks, metrics.phone_impressions, metrics.phone_calls FROM campaign WHERE segments.date>='2023-09-14' AND segments.date<='2023-09-14'  AND campaign.id IN (XXXXXXXXXX) ORDER BY segments.date DESC”

Result: 
{
    "campaign": {
        "resourceName": "customers\/XXXXXXXXXX\/campaigns\/XXXXXXXXXX",
        "id": "XXXXXXXXXXX",

        "name": "Discovery - Inventory Expansion"
    },
    "customer": {

        "resourceName": "customers\/XXXXXXXXXX",
        "id": "XXXXXXXXXX",

        "descriptiveName": "Palmetto57 Nissan"
    },
    "metrics": {
        "clicks": "3",
        "impressions": "226",
        "phoneCalls": "0",
        "phoneImpressions": "0"
    },
    "segments": {
        "adNetworkType": "MIXED",
        "date": "2023-09-14"
    }
}

2. "query":"SELECT customer.id, customer.descriptive_name, campaign.id, campaign.name, segments.date, metrics.impressions, metrics.clicks, metrics.phone_impressions, metrics.phone_calls FROM campaign WHERE segments.date>='2023-09-14' AND segments.date<='2023-09-14'  AND campaign.id IN (XXXXXXXXXX) ORDER BY segments.date DESC”  (only segments.ad_network_type was removed)

Result:
{
    "campaign": {
        "resourceName": "customers\/XXXXXXXXXX\/campaigns\/XXXXXXXXXXX",
        "id": "XXXXXXXXXXXXX",

        "name": "Discovery - Inventory Expansion"
    },
    "customer": {

        "resourceName": "customers\/XXXXXXXXXX",
        "id": "XXXXXXXXXXX",

        "descriptiveName": "Palmetto57 Nissan"
    },
    "metrics": {
        "clicks": "3",
        "impressions": "226",
        "phoneCalls": "2",
        "phoneImpressions": "0"
    },
    "segments": {
        "date": "2023-09-14"
    }
}

My question is why do we get "phoneCalls": “0” having  segments.ad_network_type in query? Expected result is "phoneCalls": “2”. 
Note we didn’t observe similar issues for other accounts we pull Google Ads API reports data for. 
Please help to understand what is wrong here.
 

[Oksana Sulyma]

Thanks so much team!

Provided details in private message.