agentleFS
gomarble-aigomarble-ai/marketing-agent/skills/google-ads-pmax-evaluation/SKILL.md

google-ads-pmax-evaluation

Skill15 starsChanged 37 days agoMITView on GitHub

Use when evaluating Google Ads Performance Max campaigns: maturity gate, PMax vs Search comparison, asset performance labels, device/location thresholds.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always check for technical/usability issues before excluding a device or location.

    line 80
  2. Distinctive:

    No budget per asset group

    line 87
  3. Distinctive:

    No channel-level budget control

    line 90
  4. Distinctive:

    Search term data is aggregated categories only, not individual terms

    line 91
  5. Very specific:

    If campaign is profitable and ready to scale, read the google-ads-pmax-scaling skill for budget scaling, location expansion, and asset …

    line 97

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Google Ads PMax — Evaluation & Optimization

Evaluate PMax campaign readiness, compare to Search, analyze assets and segments.

Maturity Gate (BLOCKING)

Campaign must meet ONE of:

  • Age ≥ 30 days (ideally 60)
  • Total conversions ≥ 50

If neither met → WAIT. Do not optimize. ML has not stabilized. Exception: if campaign is clearly burning money (ROAS < 0.3× target after spend ≥ 3× AOV), recommend pausing.


Data Pull

Query using google_ads_run_gaql:

  1. Campaign performance: id, name, status, start_date, impressions, clicks, ctr, cost, conversions, conv_value. Filter: PERFORMANCE_MAX, LAST_30_DAYS, ENABLED.
  2. Asset group details: campaign id, asset_group id/name/status. Filter: PERFORMANCE_MAX.
  3. Asset performance labels: campaign id, asset_group name, field_type, performance_label, asset type, image URL, youtube video ID. Filter: PERFORMANCE_MAX, asset types IMAGE, YOUTUBE_VIDEO, TEXT. Limit 200.
  4. Device performance: campaign id, device, cost, conversions, conv_value, clicks, impressions. Filter: PERFORMANCE_MAX, LAST_30_DAYS.
  5. Geographic performance: campaign id, geo_target_region, cost, conversions, conv_value. Filter: PERFORMANCE_MAX, LAST_30_DAYS. Sort by cost DESC, limit 200.
  6. PMax vs Search comparison: campaign id/name, channel_type, cost, conversions, conv_value. Filter: PERFORMANCE_MAX and SEARCH, LAST_30_DAYS, ENABLED.
  7. Search term insights (limited for PMax): category_label, clicks, impressions, conversions, cost from campaign_search_term_insight. Filter: PERFORMANCE_MAX, LAST_30_DAYS. Limit 200.

Step 1: PMax vs Search Comparison

Calculate ROAS for both channel types and compare:

PMax ROAS RatioAssessmentAction
< 0.5× Search ROASPoorMonitor closely, consider pausing if not improving
0.5–0.9× Search ROASBelow parOptimize assets and negatives before any scaling
≥ 0.9× Search ROASHealthyProceed with optimization, eligible for scaling
> Search ROASOutperformingPrioritize scaling

Step 2: Asset Performance Analysis

Google provides performance labels per asset (NOT cost/conversion data per asset):

LabelAction
BESTCreate variations with similar style/messaging. This is working — make more like it.
GOODKeep, monitor. No changes needed.
LOWRemove from asset group. Replace with variations of BEST performers.
PENDING / UNSPECIFIEDWait for more data (typically 14+ days).

Group by asset type (images, videos, headlines, descriptions) when reporting.


Step 3: Device & Location Analysis

Device

Device CPA vs AccountAction
> 1.5× account CPACheck site/funnel usability on that device first. If no issues → consider -50% bid adjustment or exclusion
> 2× account CPAStrong candidate for exclusion after confirming no technical issues
CVR < 0.5× account CVRCheck landing page experience on that device

Location

Location CPA vs AccountAction
> 1.5× account CPAConsider excluding
> 2× account CPAExclude
Spend but 0 conversionsWait for more data OR exclude if spend ≥ 2× AOV

Always check for technical/usability issues before excluding a device or location.


PMax Limitations (do NOT recommend these)

  • No keyword targeting
  • No budget per asset group
  • No placement control
  • No demographic control
  • No channel-level budget control
  • Search term data is aggregated categories only, not individual terms

Next Steps

If campaign is profitable and ready to scale, read the google-ads-pmax-scaling skill for budget scaling, location expansion, and asset expansion rules.

Output must include: maturity status, PMax vs Search comparison, asset label summary (BEST/GOOD/LOW counts), device/location flags, scaling eligibility assessment.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.