Update Google Ads billing cadence

<Info>This API is in beta. Endpoints, fields, and behavior may still change, so avoid depending on it in production.</Info>

Changes how often the account is charged for ad spend.

Send 1w for weekly, 2w for fortnightly, or 1m for monthly.

<Warning>This only changes when charges happen on an account whose charge_trigger_mode is cadence. On a legacy threshold account the value is stored and the call still returns a 200, but charging keeps following the spend ladder and ignores it. Read charge_trigger_mode from Get Google Ads account before relying on this.</Warning>

<Warning>On a cadence account the new setting applies to spend that has already accrued, not only to spend from here on. The next charge is calculated from the account's existing creation or last-charge timestamp using the cadence you just set, so shortening it can bring forward a charge for spend accrued under the old one, and lengthening it can delay that charge.</Warning>

<Warning>The response includes fields beyond the ones documented here. Don't rely on undocumented response fields, as they can change at any time. Send only the fields documented here. Other request fields are not supported and their behavior can change.</Warning>

patch/api/apps/{app_id}/google-ads/accounts/{account_id}/cadence

Path parameters

app_idstring required

ID of the app whose Google Ads campaigns to manage.

ID of the app whose Google Ads campaigns to manage.

account_idstring required

ID of the Google Ads account, as returned in id by Get Google Ads account. An account that belongs to a different app returns a 404.

ID of the Google Ads account, as returned in id by Get Google Ads account. An account that belongs to a different app returns a 404.

Request body

billing_cadence'1w' | '2w' | '1m' required

How often to charge the account: weekly, fortnightly, or monthly.

Response

Successful Response

billing_cadencestring required

The cadence now in effect: 1w, 2w, or 1m.

Example response

{
  "billing_cadence": "1w"
}

Changes

No recorded changes to this endpoint across all 1 revision of this API.