RE: adgroup cpc, cpm, and cpv default values

[Google Ads API Forum Advisor]

Hi,

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

I have raised your concern with the rest of our team and one of my teammates will reach out to you once we have an update. Meanwhile, your patience is appreciated.

Thanks,
 

Google Ads API Team

Feedback
How was our support today?

               
[2025-02-20 06:56:16Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH2ha:ref" (ADR-00288938)

[Google Ads API Forum Advisor]

Hello,

The ad group inherits the bidding strategy from its campaign if it's not set at the ad group level. Please double-check the campaign bidding strategy and you should see that the numbers match.

Thanks,
 

Michael Cloonan Google Ads API Team

Feedback
How was our support today?
               

[2025-02-20 15:51:43Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH2ha:ref" (ADR-00288938)

 

[Hwansang Cho]

Hi,

It does not match your campaign bidding strategy. Please check again.

In addition, the original message was deleted. Did you delete it on purpose?

{
  "results": [
    {
      "campaign": {
        "resourceName": "customers/4428838782/campaigns/22253255885",
        "status": "ENABLED",
        "adServingOptimizationStatus": "ROTATE",
        "advertisingChannelType": "SEARCH",
        "networkSettings": {
          "targetGoogleSearch": true,
          "targetSearchNetwork": true,
          "targetContentNetwork": true,
          "targetPartnerSearchNetwork": false,
          "targetYoutube": false,
          "targetGoogleTvNetwork": false
        },
        "servingStatus": "SUSPENDED",
        "biddingStrategyType": "TARGET_SPEND",
        "targetSpend": {
          "cpcBidCeilingMicros": "10000000000"
        },
        "geoTargetTypeSetting": {
          "positiveGeoTargetType": "PRESENCE_OR_INTEREST",
          "negativeGeoTargetType": "PRESENCE"
        },
        "paymentMode": "CLICKS",
        "name": "rotationTest",
        "id": "22253255885",
        "startDate": "2025-02-18",
        "endDate": "2037-12-30",
        "biddingStrategySystemStatus": "PAUSED",
        "primaryStatus": "NOT_ELIGIBLE",
        "primaryStatusReasons": [
          "NO_KEYWORDS",
          "NO_AD_GROUP_ADS"
        ]
      },

Thank you.

2025년 2월 21일 금요일 오전 12시 52분 20초 UTC+9에 Google Ads API Forum Advisor님이 작성:

[Google Ads API Forum Advisor]

What I meant with the previous response was that the bidding strategy set at the campaign level influences the automatic bidding set at the ad group level. For example, in this campaign, the strategy type is "TARGET_SPEND". Google Ads will attempt to adjust the bids of the ad groups to ensure that the entire budget is spent within the timeframe specified.

When you fetch the bids, it's likely just an initial bid to gauge performance and it may be adjusted over time depending on how things are going.

Thanks,
 

Michael Cloonan Google Ads API Team

Feedback
How was our support today?
               

[2025-02-24 15:20:44Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH2ha:ref" (ADR-00288938)

[Hwansang Cho]

Hi, Thank you for your reply.

I understand what you conveyed.
However, if it's a search ad and the bidding strategy is TARGET_SPEND, can it affect not only cpcBid but also cpm and cpv?

advertisingChannelType: SEARCH
targetCpmMicros: 1000000
targetCpvMicros: 1000000

Thank you.

2025년 2월 25일 화요일 오전 12시 21분 21초 UTC+9에 Google Ads API Forum Advisor님이 작성:

[Google Ads API Forum Advisor]

Hello,

For search campaigns, the CPC bid is obviously the most important, but there may be some circumstances where other bid types are relevant. My team's primary focus is on configuring your account on the API, not on the nuances of the bidding scheme, so unfortunately I don't have specific details on that. Rest assured that this behavior is expected and normal.

Thanks,
 

Michael Cloonan Google Ads API Team

Feedback
How was our support today?
               

[2025-02-25 13:45:11Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH2ha:ref" (ADR-00288938)