← Camberstack: Google AdsCONTENT HISTORY

Update to Camberstack: Google Ads

Snapshot Nov 12, 2026 · 06:08 UTC · version 0.19.1

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for get-started

Full description — Now says: Console, Google Analytics 4, Merchant Center and Tag Manager, and make only the changes the user approves. Use at the start of any Google Ads, Search...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Camberstack: Google Ads and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Full description

Before

Nov 5, 2026 · 00:56 UTC

Console and Google Analytics 4, and make only the changes the user approves. Use at the start of any Google Ads, Search Console or GA4

After

Nov 12, 2026 · 06:08 UTC

Console, Google Analytics 4, Merchant Center and Tag Manager, and make only the changes the user approves. Use at the start of any Google Ads, Search Console, GA4, Merchant Center or Tag Manager

Skill instructions

Before

Nov 5, 2026 · 00:56 UTC

Console and Google Analytics 4, and make only the changes the user approves. Use at the start of any Google Ads, Search Console or GA4 task. Camberstack connects the user's Google Ads account and, optionally, Search Console, Google Analy...

After

Nov 12, 2026 · 06:08 UTC

Console, Google Analytics 4, Merchant Center and Tag Manager, and make only the changes the user approves. Use at the start of any Google Ads, Search Console, GA4, Merchant Center or Tag Manager task. Camberstack connects the user's Goog...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,11 +1,11 @@
 ---
 name: get-started
-description: How to use Camberstack to read a Google Ads account, Search Console and Google Analytics 4, and make only the changes the user approves. Use at the start of any Google Ads, Search Console or GA4 task.
+description: How to use Camberstack to read a Google Ads account, Search Console, Google Analytics 4, Merchant Center and Tag Manager, and make only the changes the user approves. Use at the start of any Google Ads, Search Console, GA4, Merchant Center or Tag Manager task.
 ---
 
 # Using Camberstack
 
-Camberstack connects the user's Google Ads account and, optionally, Search Console, Google Analytics 4 and Merchant Center (for products and Shopping, start with `merchant_accounts`, not `list_accounts`).
+Camberstack connects the user's Google Ads account and, optionally, Search Console, Google Analytics 4, Merchant Center (for products and Shopping, start with `merchant_accounts`, not `list_accounts`) and Tag Manager (for tags and conversion tracking, start with `tag_manager_containers`).
 
 1. **Start with `list_accounts`.** Answer questions with `account_overview` and `run_gaql` (read-only GAQL `SELECT`).
 2. **To change something:** call the `propose_` tool for that change (`propose_pause_campaign`,
@@ -15,11 +15,14 @@
    Applied proposals can be reversed with `propose_undo`, which makes a reversing proposal to approve and apply, except
    deletions Google can't reverse: their summary says so with a ⚠, so tell the user before they approve;
    `change_history` lists what was applied.
-4. **Each Google service is added separately.** When a result says Search Console, Analytics or Merchant Center isn't part of the
+4. **Each Google service is added separately.** When a result says Search Console, Analytics, Merchant Center or Tag Manager isn't part of the
    connection, give the user its `grant_url` (one click adds it). Never tell them to reconnect.
 5. For `keyword_ideas` and `keyword_metrics`, pass the account's own market: `location_ids` default to the United States.
 6. **Search Console:** lead with `search_console_summary` (per-query rows leave out rare queries). Sitemaps and
    properties change through proposals (`propose_submit_sitemap`, `propose_delete_sitemap`, `propose_add_site`,
    `propose_remove_site`). Camberstack can't request indexing or verify a property; the user does those in Search Console.
-7. **Account 000-000-0001 is a demo** with sample data: anyone can try every tool on it, and changes there never
+7. **Tag Manager:** `tag_manager_setup` checks a container's tags and lists tracking `issues`. Tag changes
+   (`propose_add_conversion_linker`, `propose_pause_tag`, …) stay in the workspace until `propose_publish_container`
+   is approved and applied; say so when proposing them.
+8. **Account 000-000-0001 is a demo** with sample data: anyone can try every tool on it, and changes there never
    touch Google. Always say when you are using it.
Full technical diff · 2 changed fields

changed /description

BEFORE
"How to use Camberstack to read a Google Ads account, Search Console and Google Analytics 4, and make only the changes the user approves. Use at the start of any Google Ads, Search Console or GA4 task."
AFTER
"How to use Camberstack to read a Google Ads account, Search Console, Google Analytics 4, Merchant Center and Tag Manager, and make only the changes the user approves. Use at the start of any Google Ads, Search Console, GA4, Merchant Center or Tag Manager task."

changed /skill_md_contents

BEFORE
"---\nname: get-started\ndescription: How to use Camberstack to read a Google Ads account, Search Console and Google Analytics 4, and make only the changes the user approves. Use at the start of any Google Ads, Search Console or GA4 task.\n---\n\n# Using Camberstack\n\nCamberstack connects the user's Google Ads account and, optionally, Search Console, Google Analytics 4 and Merchant Center (for products and Shopping, start with `merchant_accounts`, not `list_accounts`).\n\n1. **Start with `list_accounts`.** Answer questions with `account_overview` and `run_gaql` (read-only GAQL `SELECT`).\n2. **To change something:** call the `propose_` tool for that change (`propose_pause_campaign`,\n   `propose_set_daily_budget`, `propose_mark_key_event`, …), show the user the summary, including any ⚠ line, and ask\n   for approval. Only then call `apply_changes`.\n3. **Never call `apply_changes` unless the user has explicitly approved that specific proposal in this conversation.**\n   Applied proposals can be reversed with `propose_undo`, which makes a reversing proposal to approve and apply, except\n   deletions Google can't reverse: their summary says so with a ⚠, so tell the user before they approve;\n   `change_history` lists what was applied.\n4. **Each Google service is added separately.** When a result says Search Console, Analytics or Merchant Center isn't part of the\n   connection, give the user its `grant_url` (one click adds it). Never tell them to reconnect.\n5. For `keyword_ideas` and `keyword_metrics`, pass the account's own market: `location_ids` default to the United States.\n6. **Search Console:** lead with `search_console_summary` (per-query rows leave out rare queries). Sitemaps and\n   properties change through proposals (`propose_submit_sitemap`, `propose_delete_sitemap`, `propose_add_site`,\n   `propose_remove_site`). Camberstack can't request indexing or verify a property; the user does those in Search Console.\n7. **Account 000-000-0001 is a demo** with sample data: anyone can try every tool on it, and changes there never\n   touch Google. Always say when you are using it.\n"
AFTER
"---\nname: get-started\ndescription: How to use Camberstack to read a Google Ads account, Search Console, Google Analytics 4, Merchant Center and Tag Manager, and make only the changes the user approves. Use at the start of any Google Ads, Search Console, GA4, Merchant Center or Tag Manager task.\n---\n\n# Using Camberstack\n\nCamberstack connects the user's Google Ads account and, optionally, Search Console, Google Analytics 4, Merchant Center (for products and Shopping, start with `merchant_accounts`, not `list_accounts`) and Tag Manager (for tags and conversion tracking, start with `tag_manager_containers`).\n\n1. **Start with `list_accounts`.** Answer questions with `account_overview` and `run_gaql` (read-only GAQL `SELECT`).\n2. **To change something:** call the `propose_` tool for that change (`propose_pause_campaign`,\n   `propose_set_daily_budget`, `propose_mark_key_event`, …), show the user the summary, including any ⚠ line, and ask\n   for approval. Only then call `apply_changes`.\n3. **Never call `apply_changes` unless the user has explicitly approved that specific proposal in this conversation.**\n   Applied proposals can be reversed with `propose_undo`, which makes a reversing proposal to approve and apply, except\n   deletions Google can't reverse: their summary says so with a ⚠, so tell the user before they approve;\n   `change_history` lists what was applied.\n4. **Each Google service is added separately.** When a result says Search Console, Analytics, Merchant Center or Tag Manager isn't part of the\n   connection, give the user its `grant_url` (one click adds it). Never tell them to reconnect.\n5. For `keyword_ideas` and `keyword_metrics`, pass the account's own market: `location_ids` default to the United States.\n6. **Search Console:** lead with `search_console_summary` (per-query rows leave out rare queries). Sitemaps and\n   properties change through proposals (`propose_submit_sitemap`, `propose_delete_sitemap`, `propose_add_site`,\n   `propose_remove_site`). Camberstack can't request indexing or verify a property; the user does those in Search Console.\n7. **Tag Manager:** `tag_manager_setup` checks a container's tags and lists tracking `issues`. Tag changes\n   (`propose_add_conversion_linker`, `propose_pause_tag`, …) stay in the workspace until `propose_publish_container`\n   is approved and applied; say so when proposing them.\n8. **Account 000-000-0001 is a demo** with sample data: anyone can try every tool on it, and changes there never\n   touch Google. Always say when you are using it.\n"
Full snapshot data
{
  "description": "How to use Camberstack to read a Google Ads account, Search Console, Google Analytics 4, Merchant Center and Tag Manager, and make only the changes the user approves. Use at the start of any Google Ads, Search Console, GA4, Merchant Center or Tag Manager task.",
  "included_files": [],
  "name": "get-started",
  "skill_md_contents": "---\nname: get-started\ndescription: How to use Camberstack to read a Google Ads account, Search Console, Google Analytics 4, Merchant Center and Tag Manager, and make only the changes the user approves. Use at the start of any Google Ads, Search Console, GA4, Merchant Center or Tag Manager task.\n---\n\n# Using Camberstack\n\nCamberstack connects the user's Google Ads account and, optionally, Search Console, Google Analytics 4, Merchant Center (for products and Shopping, start with `merchant_accounts`, not `list_accounts`) and Tag Manager (for tags and conversion tracking, start with `tag_manager_containers`).\n\n1. **Start with `list_accounts`.** Answer questions with `account_overview` and `run_gaql` (read-only GAQL `SELECT`).\n2. **To change something:** call the `propose_` tool for that change (`propose_pause_campaign`,\n   `propose_set_daily_budget`, `propose_mark_key_event`, …), show the user the summary, including any ⚠ line, and ask\n   for approval. Only then call `apply_changes`.\n3. **Never call `apply_changes` unless the user has explicitly approved that specific proposal in this conversation.**\n   Applied proposals can be reversed with `propose_undo`, which makes a reversing proposal to approve and apply, except\n   deletions Google can't reverse: their summary says so with a ⚠, so tell the user before they approve;\n   `change_history` lists what was applied.\n4. **Each Google service is added separately.** When a result says Search Console, Analytics, Merchant Center or Tag Manager isn't part of the\n   connection, give the user its `grant_url` (one click adds it). Never tell them to reconnect.\n5. For `keyword_ideas` and `keyword_metrics`, pass the account's own market: `location_ids` default to the United States.\n6. **Search Console:** lead with `search_console_summary` (per-query rows leave out rare queries). Sitemaps and\n   properties change through proposals (`propose_submit_sitemap`, `propose_delete_sitemap`, `propose_add_site`,\n   `propose_remove_site`). Camberstack can't request indexing or verify a property; the user does those in Search Console.\n7. **Tag Manager:** `tag_manager_setup` checks a container's tags and lists tracking `issues`. Tag changes\n   (`propose_add_conversion_linker`, `propose_pause_tag`, …) stay in the workspace until `propose_publish_container`\n   is approved and applied; say so when proposing them.\n8. **Account 000-000-0001 is a demo** with sample data: anyone can try every tool on it, and changes there never\n   touch Google. Always say when you are using it.\n"
}

SHA-256 of public snapshot: 348c794ab1de3f1a1f3653d09c5a2a312c95db84d21bd8bfb641b3303a36c8b9