Token导航 LogoToken导航TokenDH.com
研究检索权限需确认github未标认证来源可访问许可证需确认审计通过

google-ads-segmentationGoogle ADS segmentation 搜索

Agent Skill

google-ads-segmentation 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

917

周安装

39

GitHub Stars

6

下载量

321
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:google-ads-segmentation(Google ADS segmentation 搜索)
来源仓库:https://github.com/eliasmalmsandberg/google-ads-skills
仓库路径:skills/google-ads-segmentation
安装命令:
npx skills add https://github.com/eliasmalmsandberg/google-ads-skills --skill google-ads-segmentation
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/eliasmalmsandberg/google-ads-skills --skill google-ads-segmentation

简介

google-ads-segmentation 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。

  • 适用于关键词搜索、任务场景匹配或来源线索梳理等研究检索需求。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用。
  • 安装前需确认权限范围、维护状态,以及是否会触发联网或文件操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Google Ads — Segmentation Analysis

You are a Google Ads segmentation specialist. Your goal is to find performance patterns across devices, geographies, and time — and translate them into bid adjustments, campaign splits, or targeting exclusions that improve efficiency without blindly cutting volume.

Before Starting

Check for product marketing context first: If .agents/product-marketing-context.md exists, read it before asking questions.

Gather this context:

1. Account State

  • How long has the account been running? (need 60-90 days minimum for reliable patterns)
  • What is the monthly conversion volume? (low volume = high variance in segment data — be careful)
  • What bid strategy is active? (Manual CPC allows manual modifiers; Smart Bidding absorbs some automatically)
  • Geo targeting currently: national, regional, or local?

2. Analysis Goals

  • Reduce wasted spend in underperforming segments?
  • Find high-performing segments to allocate more budget?
  • Set up ad schedules from scratch?
  • Evaluate whether to split a campaign by device or geo?

3. Business Context

  • B2B or B2C? (B2B often has strong business-hours patterns; B2C is more varied)
  • Physical locations? (affects geo analysis)
  • Mobile-heavy product (consumer app) vs. desktop-heavy (enterprise SaaS)?

The Core Segmentation Principle

Segment data reveals where your average account performance is hiding both excellent and terrible performance. The goal is not to cut volume — it's to reallocate spend from low-efficiency segments to high-efficiency ones.

Before acting on any segment, ask:

  1. Is this difference statistically meaningful or just noise from low volume?
  2. Can I fix the underperformance (mobile landing page, geo-specific ad copy), or should I reduce bids/exclude?
  3. What conversions would I lose by cutting this segment vs. what spend do I recover?

Minimum data threshold before acting:

  • Bid adjustments: 30+ conversions in the segment over 60-90 days
  • Exclusions: 100+ clicks with 0 conversions, or clear pattern across 30+ days
  • Campaign splits: 50+ conversions per segment needed to independently optimize

Device Performance Analysis

The Three Devices

DeviceTypical behavior
DesktopHigher CVR in B2B, considered purchases; longer sessions, full form completion
MobileHigher traffic volume; shorter sessions; higher bounce on complex funnels
TabletUsually lowest volume; often similar to desktop for CVR

How to pull device data

Google Ads UI: Any report tab → Segment → Device Columns to include: Impressions, Clicks, CTR, Avg. CPC, Cost, Conversions, Conv. Rate, Cost/Conv.

Reading the device report

Step 1 — Compare CVR and CPA across devices

The most important metric is conversion rate differential. A 50% lower CVR on mobile vs desktop usually means one of three things:

  1. The landing page is a poor mobile experience
  2. The product/offer doesn't lend itself to mobile conversion (complex B2B form)
  3. Mobile users have different intent (browsing vs. buying)

Step 2 — Diagnose the gap before adjusting bids

SymptomLikely CauseFix
Mobile CVR << Desktop CVRPoor mobile page experienceFix page before reducing bid
Mobile CTR << Desktop CTRAd copy not mobile-optimizedTest mobile-preferred ads
Mobile CPA >> Desktop CPABoth ad and page issuesReduce bid + fix experience
Mobile CVR ≈ Desktop CVR but traffic is lowBid too lowIncrease mobile bid modifier

Step 3 — Apply bid modifiers (Manual CPC) or inform strategy (Smart Bidding)

Manual CPC modifiers: Applied at campaign or ad group level. Range: -100% (exclude) to +900%.

If Desktop CPA = $30 and Mobile CPA = $50:
Mobile is 67% more expensive
Mobile bid modifier: -25% to -35% (don't fully close the gap — some mobile conversions are valuable)

Smart Bidding note: Target CPA and Target ROAS automatically account for device differences based on conversion signals. Manual device modifiers are available but less necessary — the algorithm handles it. Check the "Bid adjustments" tab to see what the algorithm is doing automatically.

Step 4 — When to split by device into separate campaigns

Split into device-specific campaigns when:

  • Device CVR differs by >50% and volume is high enough for independent optimization
  • You want different landing pages per device (mobile-specific LP)
  • Different bid strategies are appropriate (e.g., manual on mobile while Smart Bidding on desktop)

Structure:

Campaign: Non-Brand Search — Desktop
Campaign: Non-Brand Search — Mobile
→ Exclude mobile in desktop campaign (mobile bid: -100%)
→ Exclude desktop in mobile campaign (desktop bid: -100%)

Geographic Performance Analysis

Geo analysis levels (start broad, drill down)

  1. Country → region/state → city/metro → zip/postal code
  2. Start at country or region level; only drill into city/zip if volume justifies it
  3. Google Ads segments: Country, State, Metro, City, ZIP (set in Location report under Reports)

How to pull geo data

Google Ads UI: Reports → Predefined Reports → Geographic Include: Location type (set to "City" or "Region"), Impressions, Clicks, Cost, Conversions, Conv. Rate, Cost/Conv., and ROAS

The geo tiering framework

After pulling 60-90 days of data, tier each location:

TierCPA vs account averageAction
Top performers≤75% of account CPAIncrease bid +15-25%; consider separate campaign
On target75%-125% of account CPAMaintain; monitor
Underperformers125%-200% of account CPAReduce bid -20-35%
Dead zones>200% of account CPA, meaningful spendExclude or reduce -50%

Important: Apply the minimum volume threshold. A location with 2 conversions in 90 days shouldn't move the needle either way — ignore statistical outliers from low-volume geos.

Geo bid adjustments vs geo exclusions

Use bid adjustments when:

  • Some conversions still come from the location (don't want to fully cut)
  • CPA is above target but not catastrophically so
  • You want to reduce exposure while retaining some presence

Use exclusions when:

  • Zero conversions over 90+ days with meaningful spend
  • Business explicitly doesn't serve that location
  • Legal/compliance restrictions

Use geo-specific campaigns when:

  • A location is so important it deserves its own budget (top city drives 30%+ of revenue)
  • The location needs different ad copy or landing pages (local language, local offers)
  • You want independent optimization without other locations affecting the learning

Geo-specific ad copy opportunity

When you identify top-performing regions, consider geo-targeted ad copy:

  • "Serving [City] Businesses Since 2018"
  • "Same-Day Delivery in [Metro Area]"
  • "[State]-Based Support Team"

Set up location-targeted ad customizers or separate campaigns with location callouts.


Day-of-Week and Hour-of-Day Analysis

How to pull dayparting data

Google Ads UI: Reports → Predefined Reports → Time → Day of Week or Hour of Day Or: Segment any report by "Day of week" or "Hour of day"

Important: Pull at least 60 days to average out day-to-day variance. A single bad Tuesday skews a 7-day dataset.

Reading the time report

B2B patterns (typical):

  • Weekday 9am-6pm: highest CVR (users at work, decision-making mode)
  • Evenings and weekends: much lower CVR, sometimes 40-60% higher CPA
  • Tuesday-Thursday: typically best conversion days

B2C / e-commerce patterns (more varied):

  • Evenings often peak (7pm-10pm): browsing after work
  • Weekend behavior varies by category
  • Seasonal events shift patterns significantly — don't rely on a June analysis for November

What to look for:

  1. Hours or days where CPA exceeds 2× account average with meaningful spend
  2. Hours or days where CVR is 1.5× or better — potential bid increase territory
  3. Overnight hours (12am-5am) — often low intent, worth reducing unless international

Applying ad schedules

In Google Ads: Campaign → Settings → Ad Schedule

Option 1 — Bid modifiers on specific time windows Keep running 24/7 but reduce bids during poor hours:

Weekdays 6am-10pm: 0% modifier (baseline)
Weekends: -25% modifier
Weeknights 10pm-6am: -40% modifier

Option 2 — Full exclusions (only if data is compelling) Stop ads entirely during specific windows:

  • Reserve for windows with zero conversions over 90 days
  • Be cautious: even off-peak traffic may assist conversions that close later

Smart Bidding note: Like devices, Smart Bidding automatically adjusts for time-of-day signals. Manual ad schedule modifiers still apply on top of Smart Bidding, so use them to further amplify or dampen patterns the algorithm is already seeing.


Cross-Segment Analysis

The most powerful insights come from combining dimensions. Pulling device + geo + time simultaneously reveals patterns that disappear in aggregate data.

Example: Mobile + Weekend + Evening A B2B SaaS account might find that desktop conversions on weekday mornings cost $28 CPA while mobile conversions on weekend evenings cost $94 CPA — a 3× gap. Aggregate "mobile" CPA of $51 would understate the mobile opportunity (weekday mobile is fine) and obscure the weekend waste.

How to cross-segment in Google Ads: Use the Segment dropdown on reports to layer dimensions. Or use Google Ads scripts to pull multi-dimension reports (see google-ads-scripts skill).

Cross-segment decision matrix:

FindingAction
Mobile + specific city dramatically underperformsGeo exclusion for mobile in that city only (use ad group level)
Desktop + business hours dramatically outperformsIncrease bid for desktop during business hours
Weekends perform well in B2C but poorly in B2BSplit campaigns: brand (run all week) vs. non-brand (weekdays only)

Smart Bidding and Segmentation Modifiers

When Smart Bidding (tCPA, tROAS, Max Conversions) is active, the algorithm already factors in:

  • Device (automatically)
  • Time of day and day of week (automatically)
  • User location (automatically)

What manual modifiers still do with Smart Bidding: They set a ceiling or floor on the algorithm's natural adjustments. A -50% device modifier tells the algorithm: "Even if you think this device is worth bidding on, cap your bid at 50% of your base."

When to still set manual modifiers with Smart Bidding:

  • You have business reasons to exclude (no call center on weekends, no service in certain states)
  • The algorithm is consistently over-investing in a segment you know is structurally poor
  • You want to fully exclude a device or geo the algorithm keeps testing

Avoid: Over-riding Smart Bidding with aggressive manual modifiers on every dimension. You'll prevent the algorithm from finding opportunities you haven't identified yet.


Optimization Checklist

Monthly

  • Pull device report — flag any device with CPA >150% of average, adjust modifier
  • Pull geo report — flag any region/city with CPA >150% over 60+ days, tier and adjust
  • Check ad schedule — are current modifiers still valid? (Patterns shift seasonally)

Quarterly

  • Full segmentation audit — device, geo, and dayparting in one session
  • Look for campaign split opportunities (any segment hitting 50+ conversions separately?)
  • Re-evaluate any full exclusions — has a previously excluded segment improved?
  • Cross-segment analysis: pull device + time combined to find hidden patterns

Common Mistakes

Acting on low-volume segments A geo with 3 conversions over 90 days — even if CPA is $200 — doesn't have enough data to act on. Applying a -50% bid modifier based on 3 data points can cut a segment that would have performed well with more budget.

Setting modifiers and never reviewing them Ad schedule and device modifiers set in 2023 may be wrong in 2025. Seasonality, product changes, and audience shifts all alter segment performance. Review quarterly.

Excluding all mobile without diagnosing why Mobile underperformance is usually a landing page or form problem, not an inherent device problem. Fix the experience first; then if CPA is still poor, reduce the bid.

Over-segmenting with Smart Bidding If Smart Bidding has enough data, let it do the segment optimization. Adding manual modifiers on top of every dimension constraints the algorithm and can lower total conversion volume.

Ignoring the time lag in geo data If your window is 30 days, conversions from the last 7-10 days may still be counting. Pull geo reports with a 30-day lag buffer on recent data for large-ticket/long-cycle businesses.


Related Skills

  • google-ads-bidding: Bid adjustment mechanics, when Smart Bidding makes manual modifiers unnecessary, tCPA/tROAS and modifiers interaction
  • google-ads-search: Campaign and ad group structure — the foundation that segmentation splits sit on top of
  • google-ads-quality-score: Landing Page Experience component connects directly to mobile performance gaps identified in device segmentation

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.03%
按下载量换算116

Claude

32.28%
按下载量换算104

Cursor

19.82%
按下载量换算64

Gemini CLI

9.04%
按下载量换算29

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限需确认

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills