provider "google_ads"

The provider block declares which Google Ads account bidsmith is operating against. Every .bid project needs exactly one provider block; convention is to put it at the top of your top-level account.bid (or in the first file of a single-file project).

Note

customer_id is optional here. For live commands the target account resolves in order: GOOGLE_ADS_CUSTOMER_ID env var → bidsmith.toml in your project → this provider block → your saved sign-in. Leave it out of the provider block to keep .bid files account-agnostic and target them with a per-folder bidsmith.toml — ideal when one set of campaigns is applied to several accounts. (export also accepts --customer-id / --login-customer-id; plan and apply do not — use bidsmith.toml or the env vars for those.)

Example

provider "google_ads" {
  customer_id       = "1234567890"
  login_customer_id = "9876543210"
}

Owning the account’s extensions

An extension attached to the account rather than to a campaign shows up under every campaign you run. owns says that your files are the complete list of them, so a live one nothing declares is removed:

provider "google_ads" {
  customer_id = "1234567890"
  owns        = ["sitelinks", "callouts"]
}

Accepted values are sitelinks, callouts, structured_snippets, and calls — each naming one kind of google_ads_customer_asset — plus automatically_created_assets, which claims the account-level assets Google’s automation attached rather than a kind you could declare. Those are paused rather than removed, since Google reattaches anything bidsmith deletes; the same claim written on a campaign covers that campaign’s own automation assets. Anything you leave out of the list is left alone, and an empty or absent owns is today’s behaviour: nothing account-wide is ever removed.

Caution

This is the widest-reaching removal bidsmith can make — one destroy changes what every campaign in the account serves. Declare what you want to keep before adding owns, and read the - destroy rows in bidsmith plan carefully. Full walkthrough: Serve only the extensions you declared.

Schema

Optional

• customer_id ( String )
• login_customer_id ( String )
• owns ( List of String )

See also

• Connect to Google Ads — how to mint the credentials behind these IDs.
• Glossary: customer ID — what the 10-digit number means.