From google-ads
Verify that campaigns use the correct location targeting method ("Presence" vs "Presence or Interest") based on business type.
npx claudepluginhub trueclicks/claude-plugins --plugin google-adsThis skill is limited to using the following tools:
For local businesses, "Presence" targeting is typically preferred to avoid wasted spend on users who cannot physically visit. This skill verifies campaigns use the correct location targeting method based on business type and flags potentially misconfigured campaigns.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Builds scalable data pipelines, modern data warehouses, and real-time streaming architectures using Spark, dbt, Airflow, Kafka, and cloud platforms like Snowflake, BigQuery.
Builds production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. For data pipelines, workflow orchestration, and batch job scheduling.
For local businesses, "Presence" targeting is typically preferred to avoid wasted spend on users who cannot physically visit. This skill verifies campaigns use the correct location targeting method based on business type and flags potentially misconfigured campaigns.
Data Source: Standard
Standard Data:
data/account/account_summary.md - Account context and business typedata/account/campaigns/*/campaign.md - Campaign settings including geo targeting typedata/account/campaigns/*/bid_adjustments.md - Location targeting detailsReference GAQL:
SELECT
campaign.id,
campaign.name,
campaign.geo_target_type_setting.positive_geo_target_type,
campaign.geo_target_type_setting.negative_geo_target_type,
campaign.status
FROM campaign
WHERE campaign.status != 'REMOVED'
Use /google-ads:get-custom if geo target type settings are not in standard export.
Load campaign data: Read account summary to understand business type, read each campaign.md for geo targeting settings.
Identify location targeting settings: Extract positiveGeoTargetType and negativeGeoTargetType values (Presence vs PresenceOrInterest).
Classify by business type: Local Service/Retail = should use Presence. E-commerce/Travel = can use PresenceOrInterest.
Flag potential issues: Local business using PresenceOrInterest (wasted spend), e-commerce using Presence only (missing researchers), inconsistent settings across similar campaigns.
| Condition | Severity |
|---|---|
| Local service business with PresenceOrInterest | Critical |
| Local retail with PresenceOrInterest | High |
| Inconsistent settings across similar campaigns | Warning |
| E-commerce with Presence only | Info |
Short (default):
## Location Targeting Method Audit
**Account:** [Name] | **Campaigns Analyzed:** [X] | **Potentially Misconfigured:** [Y]
### Critical ([Count])
- **[Campaign]**: Local business using "Presence or Interest" → Change to "Presence"
### Warnings ([Count])
- **[Campaign]**: Inconsistent with other campaigns → Review for consistency
### Recommendations
1. [Priority action]
2. [Secondary action]
Detailed adds: