DGen Ad-Level Automation Disable

Purpose: Programmatically set all Demand Gen ad-level asset automation settings to OPTED_OUT across one or many accounts — the auto-generated design versions, generated videos, and landing-page previews that trade creative control for Google's guesses.

Type: Mutation skill — two-step approval required, always. The mutation-safety pattern (dry-run preview → human reads → execute with the code from that preview) is implemented directly in the shipped script.

This skill deliberately does NOT:

• Decide whether disabling is right for the account — that judgment (accounts leaning on generated video, shared management, mid-flight experiments) lives in rules.md § "When NOT to disable" and belongs to the operator.
• Touch campaign-level automation — PMax automation is campaign-level and belongs to pmax-asset-automation; DGen automation is per-ad, which is why this tool exists separately.
• Enable anything, ever — one direction only, toward OPTED_OUT.
• Execute without a human-read dry-run — no code, no mutation; and the code only proves the account hasn't changed since the preview you read.
• Normalize CIDs — dashes are NOT stripped; a dashed CID errors rather than matching (contract).

Background (one paragraph)

Demand Gen asset automation operates at the ad level — settings live on each ad, new ads arrive with automation ON, and two ad types carry five settings between them (the exact taxonomy and defaults: references/mutation-contract.md). One default matters at read time: GENERATE_LANDING_PAGE_PREVIEW ships OFF, so finding it ON in a diff means someone turned it on — attribute before you overwrite (rules.md, reading the diff).

Two-Step Mutation Flow

Step 1 — Dry-run preview (free, writes nothing)

# Single account
python scripts/fix_dgen_ad_automation.py --cid 1234567890

# Multiple accounts (comma-separated CIDs)
python scripts/fix_dgen_ad_automation.py --cids "1234567890,2345678901"

# All enabled accounts under the MCC
python scripts/fix_dgen_ad_automation.py --all

Prints per-account diffs (each ad's settings with current -> OPTED_OUT lines), a summary (accounts / ads / settings), and an APPROVAL CODE.

Then READ the diff — the five checks in rules.md § "Reading the dry-run diff": error lines (an erroring account silently drops out — All accounts are compliant can be false), ad counts vs. expectation, settings-per-ad sanity, the landing-page-preview tell, and unexpected current values. Approve only what you can explain.

Step 2 — Execute with the approval code

python scripts/fix_dgen_ad_automation.py --cid 1234567890 APPROVE-A3F9B2C1

The code is a deterministic hash of the pending work, recomputed from current account state at execute time — ANY drift since your dry-run (new ads, a Google-side reset, a colleague's fix) refuses with a mismatch. A mismatch is information, not an error: re-run the dry-run and read what changed (rules.md, "the mismatch is a feature"). Full hash semantics: the contract.

Execution is one all-or-nothing mutation per account; failed accounts log and the batch continues. Every execute appends to ./logs/mutations_log.jsonl (success and failure) — dry-runs write nothing.

Step 3 — Verify (optional, execute-mode, single account)

python scripts/fix_dgen_ad_automation.py --cid 1234567890 APPROVE-A3F9B2C1 --verify

Re-queries and confirms every in-scope DGen ad is OPTED_OUT. Three no-op cases for --verify (silent on dry-run and already-compliant runs; a printed note on multi-account runs) are in the contract — for a no-mutation compliance check, use a plain dry-run instead.

CLI Reference

Selection scope (what "in scope" means — enabled campaigns and ads, ended campaigns excluded, paused ad groups' enabled ads INCLUDED), logging shapes, and the sheet-log token requirement are all in references/mutation-contract.md.

One implementation fact worth knowing even if you never read the contract: the API replaces the whole settings list on update — the script always sends every applicable setting per ad type, and any tooling you write against this field must do the same, or unspecified settings silently reset to OPTED_IN.

Prerequisites

1. Google Ads API credentials — google-ads.yaml at project root (see google-ads-api-setup)
2. Python: pip install google-ads google-auth google-api-python-client pyyaml
3. For --log-sheet-id only: the refresh token inside google-ads.yaml must carry the spreadsheets scope (the api-setup generator's default token does). The local JSONL log needs nothing extra.

Installation

mkdir -p .claude/skills/dgen-automation-disable/scripts .claude/skills/dgen-automation-disable/references
for f in SKILL.md README.md rules.md examples.md; do
  curl -o .claude/skills/dgen-automation-disable/$f \
    https://raw.githubusercontent.com/fourteenwm/ppc-ai-skills/main/dgen-automation-disable/$f
done
curl -o .claude/skills/dgen-automation-disable/references/mutation-contract.md \
  https://raw.githubusercontent.com/fourteenwm/ppc-ai-skills/main/dgen-automation-disable/references/mutation-contract.md
curl -o .claude/skills/dgen-automation-disable/scripts/fix_dgen_ad_automation.py \
  https://raw.githubusercontent.com/fourteenwm/ppc-ai-skills/main/dgen-automation-disable/scripts/fix_dgen_ad_automation.py

Files in This Skill

Runtime artifacts (gitignore them): logs/mutations_log.jsonl — appended on every execute; dry-runs write nothing.

After a Run

logs/mutations_log.jsonl is the durable record — one line per account per execute, success or failure. No row = no mutation through this script. The API-side record is the account's change history. When a run mutated anything, calendar the follow-ups from rules.md § Cadence: the monthly drift re-run, and a re-run after any paused campaign re-enables.

When to Load Something Else