For end users

google-ads

Pull paid search performance from Google Ads into the ad_metrics table.

Type: inbound. The runner calls fetch.ts directly; the model is not invoked at fetch time.

What it fetches

• Campaign-level: cost, clicks, impressions, conversions, conversion value, search lost IS (budget + rank).
• Ad-group and keyword-level roll up under campaign for matched analysis with organic search performance from gsc.

What you need

• A Google Ads account the workspace runs paid search through.
• A Google service account with access to the Ads account. Google Ads requires a separate developer token (free, requires application).
• The Google Ads API enabled in your Google Cloud project.

See the Google Ads integration walkthrough for the developer-token application steps.

Configuration

• GOOGLE_ADS_DEVELOPER_TOKEN — install-wide.
• GOOGLE_ADS_LOGIN_CUSTOMER_ID — the manager (MCC) account ID, if you use one.

The CMS Apps surface (/apps/google-ads) collects these and runs a Test connection.

Interpretation

After fetch, apps/google-ads/insights/SKILL.md (when present) turns the raw rows into Insights for weekly-analysis.

Where it lives

pectusai/apps/google-ads/APP.md