StackOSWork, organized
LibraryWorkflowsAgentsOrchestratorsIntegrationsArticles

Google Ads API provider contract for customers, budgets, campaigns, ad groups, assets, ads, reporting, and conversions.

10 listed actions3 capability groups

Connection facts

What the Google Ads connector actually exposes.

These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.

Connection method
OAuth connection
Setup
Enable Google Ads API and obtain a developer token. Choose OAuth or grant a service account access in Google Ads and enter its JSON key locally. Service accounts do not need a delegated user. Use Manager Account Ref for the login-customer-id header when accessing customers through a manager.
Capability groups
Campaign Management, Creative Operations, Media Measurement
Action boundaries
2 read actions8 write actions

Action catalog

Actions listed for Google Ads.

Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.

10 matching actions

Create Google Ad Group

Campaign ManagementCan make changes

Create a Google Ads ad group from explicit bidding, targeting, and status fields.

Create Google Ad Group Ad

Campaign ManagementCan make changes

Create a Google Ads ad group ad from explicit ad content and safe asset refs.

Create Google Asset

Creative OperationsCan make changes

Create a Google Ads asset from an explicit provider-native asset object.

Create Google Campaign

Campaign ManagementCan make changes

Create a Google Ads campaign from an explicit campaign object and campaign budget ref.

Create Google Campaign Budget

Campaign ManagementCan make changes

Create a Google Ads campaign budget from explicit budget fields and safe customer refs.

Create Google Conversion Action

Media MeasurementCan make changes

Create a Google Ads conversion action from explicit tracking and attribution fields.

List Google Ads Customers

Campaign ManagementReads data

Read accessible Google Ads customer metadata for the configured credential.

Search Google Ads Report

Media MeasurementReads data

Run one Google Ads GAQL search page. Read body.next_page_cursor from the response file and pass it as page_cursor with the same customer_ref and query to continue; no cursor means the final page.

Update Google Campaign Budget

Campaign ManagementCan make changes

Update a Google Ads campaign budget from explicit budget changes.

Upload Google Click Conversions

Media MeasurementCan make changes

Upload approved Google Ads click conversions from safe event refs and daemon-side PII handling.

Direct answer

How does the Google Ads integration work?

People continue using Google Ads as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.

  1. 01Your requestStart in your AI
  2. 02StackOS planExpands the steps
  3. 03Google AdsDoes its bounded part
  4. 04Checked resultKeeps the proof

More from Media Buying

Related integrations.

See the plugin →

Common questions

Google Ads and StackOS.

What can the Google Ads integration do in StackOS?

The current catalog includes 10 Google Ads actions across Campaign Management, Creative Operations, Media Measurement. The exact actions used depend on the workflow and approval rules.

Does StackOS replace Google Ads?

No. Google Ads remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.