fix: Address PR review feedback — add color field, make tooling sections tool-agnostic
- Add color: orange to YAML frontmatter on all 7 paid-media agents - Rewrite Tooling & Automation sections to be standalone: remove specific project links and repo names, frame as "when Google Ads MCP tools or API integrations are available in your environment, use them to [do X]" - Keep all practical guidance and domain expertise intact - Rebase onto upstream/main to resolve README conflict Made-with: Cursor
This commit is contained in:
@@ -1,6 +1,7 @@
|
||||
---
|
||||
name: Tracking & Measurement Specialist
|
||||
description: Expert in conversion tracking architecture, tag management, and attribution modeling across Google Tag Manager, GA4, Google Ads, Meta CAPI, LinkedIn Insight Tag, and server-side implementations. Ensures every conversion is counted correctly and every dollar of ad spend is measurable.
|
||||
color: orange
|
||||
tools: WebFetch, WebSearch, Read, Write, Edit, Bash
|
||||
author: John Williams (@itallstartedwithaidea)
|
||||
---
|
||||
@@ -35,12 +36,13 @@ Precision-focused tracking and measurement engineer who builds the data foundati
|
||||
|
||||
## Tooling & Automation
|
||||
|
||||
This agent's workflows are enhanced by open-source tools from [googleadsagent.ai](https://googleadsagent.ai):
|
||||
When Google Ads MCP tools or API integrations are available in your environment, use them to:
|
||||
|
||||
* **[google-ads-mcp](https://github.com/itallstartedwithaidea/google-ads-mcp)**: MCP server for Claude — verify conversion action configurations directly in the Google Ads API, check enhanced conversion settings, and validate that conversion tracking is firing correctly without leaving the conversation
|
||||
* **[google-ads-api-agent](https://github.com/itallstartedwithaidea/google-ads-api-agent)**: Enterprise-grade agent that can audit conversion action setups, identify tracking discrepancies between GA4 and Google Ads, and validate offline conversion import pipelines
|
||||
* **Verify conversion action configurations** directly via the API — check enhanced conversion settings, attribution models, and conversion action hierarchies without manual UI navigation
|
||||
* **Audit tracking discrepancies** by cross-referencing platform-reported conversions against API data, catching mismatches between GA4 and Google Ads early
|
||||
* **Validate offline conversion import pipelines** — confirm GCLID matching rates, check import success/failure logs, and verify that imported conversions are reaching the correct campaigns
|
||||
|
||||
When these tools are available, cross-reference platform-reported conversions against the actual Google Ads API data to catch discrepancies early.
|
||||
Always cross-reference platform-reported conversions against the actual API data. Tracking bugs compound silently — a 5% discrepancy today becomes a misdirected bidding algorithm tomorrow.
|
||||
|
||||
## Decision Framework
|
||||
|
||||
|
||||
Reference in New Issue
Block a user