Analyze Google Ads paid-search quality-to-pipeline signals with Claude

Write a one-page operating charter for paid-search lead quality and downstream pipeline signals before exporting any data. State the exact decision this workflow supports: which campaigns, queries, conversion actions, and bidding inputs should be scaled, corrected, limited, or investigated. Define the in-scope business units, pipelines, regions, date window, record types, and exclusions, then name one analysis owner, one Google Ads data owner, and one final approver. Record the review cadence as weekly or biweekly and specify where evidence, approvals, and exceptions will be stored. Review the charter with the approver and do not proceed until the scope and decision rights are accepted.

Convert the operating policy into a rule register that can be checked against Google Ads campaigns, search terms, assets, and conversion actions. Create one row per rule with rule_id, rule_name, business_reason, required_fields, calculation_or_test, pass_condition, exception_code, severity, owner, and policy_version. Start with these minimum checks: primary and secondary conversions are separated, conversion values reflect approved business meaning, search-term and campaign data use the same date and attribution settings, offline imports are monitored for delay and coverage, and small downstream samples are not used for aggressive bidding changes. Give every rule an example that should pass and an example that should fail so reviewers interpret it consistently. Have the business owner approve the rule register and record any unresolved policy questions before data is scored.