adloop 0.19.6__tar.gz → 0.21.0__tar.gz

{adloop-0.19.6 → adloop-0.21.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: adloop
-Version: 0.19.6
+Version: 0.21.0
 Summary: The AI command center for Google Ads, Reddit Ads, GA4, and tracking code.
 Keywords: mcp,google-ads,reddit-ads,google-analytics,ga4,cursor,marketing
 Author: Daniel Klose
@@ -13,6 +13,7 @@ Requires-Dist: google-analytics-admin>=0.27.0
 Requires-Dist: google-api-python-client>=2.100.0
 Requires-Dist: google-auth-oauthlib>=1.0.0
 Requires-Dist: google-api-python-client>=2.0.0
+Requires-Dist: phonenumbers>=8.13
 Requires-Dist: pyyaml>=6.0
 Requires-Dist: requests>=2.31
 Requires-Dist: pytest>=8.0 ; extra == 'dev'
@@ -187,6 +188,26 @@ These tools read the live GTM container and join it with the codebase + GA4 to f
 | `list_gtm_versions` | Publish history with version IDs and entity counts. Use to correlate a metric drop with a recent publish. |
 | `get_gtm_version` | Full metadata + tag/trigger names for a single historical container version |
 
+#### GTM write tools (opt-in)
+
+Off by default. Set `gtm.write_enabled: true` in `~/.adloop/config.yaml` and restart; the next call asks you to re-consent with the Tag Manager edit + publish scopes, which are never part of the default grant. Everything follows the usual draft → preview → `confirm_and_apply` flow, and tag/trigger edits only touch a workspace until you publish it.
+
+| Tool | What It Does |
+|------|-------------|
+| `draft_gtm_tag` | Create a tag, or update one by `tag_id`. Updates are a read-modify-write: `parameters` merge by key and every field you don't pass (priority, consent settings, firing options, schedule, folder, …) is preserved. Tag types are canonical GTM template IDs (`googtag`, `gaawe`, `awct`, `sp`, `gclidw`, …) or `cvt_<id>` gallery templates. |
+| `draft_gtm_trigger` | Create a trigger, or update one by `trigger_id` (type is immutable). `custom_event_name` wires a `customEvent` trigger to a dataLayer event. |
+| `draft_delete_gtm_entity` | Delete a workspace tag or trigger. Triggers still referenced by a tag are refused up front, with the tags listed. |
+| `draft_publish_gtm_workspace` | Publish a workspace live. The preview lists every pending change, including edits other people made in the GTM UI. |
+
+Safety gates specific to GTM:
+- **Custom HTML** runs arbitrary JavaScript on your site, so creating or editing an `html` tag — or publishing a workspace that adds or changes one — is refused unless `gtm.allow_custom_html: true` is also set. Pausing or deleting one is always allowed.
+- **No stale writes.** Updates and deletes pin the entity's fingerprint from the preview, and publish pins the workspace's pending changes; if someone edits the container in between, apply refuses and you re-draft.
+- Publishing stops on merge conflicts or GTM compiler errors. The dry run runs a Tag Manager **quick preview** first (Tag Manager has no validate-only mode), so compiler errors surface before a version is even created. That preview is a POST and stores a preview version in the container — nothing is published and no live tag changes; the rest of the dry run only reads.
+- The publish result names the version it replaced (`previous_live_version_id`), so rolling back is one step: publish that version again in the GTM UI. If the version was created but publishing it failed, the error carries both the created version id and the still-live one.
+- Per-operation names for `safety.blocked_operations`: `gtm_create_tag`, `gtm_update_tag`, `gtm_delete_tag`, `gtm_create_trigger`, `gtm_update_trigger`, `gtm_delete_trigger`, `gtm_publish_workspace`.
+
+The Google account also needs **Edit** permission on the container (and **Publish** to publish) under Admin → User Management.
+
 > **Setup for GTM tools** — Enable the **Tag Manager API v2** in your GCP project, then add your AdLoop credentials' email (the OAuth user, or the service account email if using a service account) as a **Read** user on the GTM container under Admin → User Management. Service accounts pick up access on the next call. **OAuth users upgrading from an earlier AdLoop version must re-authorize once**: the GTM scope is new, so delete `~/.adloop/token.json` and run any tool to re-consent — until then GTM tools return a permissions error.
 
 ### Search Console Tools
@@ -515,7 +536,7 @@ Most MCP clients (claude.ai, ChatGPT, Cursor, …) load **every tool schema into
 | `ads` | Google Ads reads, writes, and planning (Keyword Planner) |
 | `ga4` | Google Analytics reports, realtime, key events |
 | `tracking` | Cross-channel attribution + tracking code generation |
-| `gtm` | Google Tag Manager audits and reads |
+| `gtm` | Google Tag Manager audits, reads, and opt-in writes |
 | `gsc` | Search Console reads |
 | `web` | PageSpeed / Core Web Vitals |
 | `merchant` | Merchant Center feed health |

{adloop-0.19.6 → adloop-0.21.0}/README.md

@@ -160,6 +160,26 @@ These tools read the live GTM container and join it with the codebase + GA4 to f
 | `list_gtm_versions` | Publish history with version IDs and entity counts. Use to correlate a metric drop with a recent publish. |
 | `get_gtm_version` | Full metadata + tag/trigger names for a single historical container version |
 
+#### GTM write tools (opt-in)
+
+Off by default. Set `gtm.write_enabled: true` in `~/.adloop/config.yaml` and restart; the next call asks you to re-consent with the Tag Manager edit + publish scopes, which are never part of the default grant. Everything follows the usual draft → preview → `confirm_and_apply` flow, and tag/trigger edits only touch a workspace until you publish it.
+
+| Tool | What It Does |
+|------|-------------|
+| `draft_gtm_tag` | Create a tag, or update one by `tag_id`. Updates are a read-modify-write: `parameters` merge by key and every field you don't pass (priority, consent settings, firing options, schedule, folder, …) is preserved. Tag types are canonical GTM template IDs (`googtag`, `gaawe`, `awct`, `sp`, `gclidw`, …) or `cvt_<id>` gallery templates. |
+| `draft_gtm_trigger` | Create a trigger, or update one by `trigger_id` (type is immutable). `custom_event_name` wires a `customEvent` trigger to a dataLayer event. |
+| `draft_delete_gtm_entity` | Delete a workspace tag or trigger. Triggers still referenced by a tag are refused up front, with the tags listed. |
+| `draft_publish_gtm_workspace` | Publish a workspace live. The preview lists every pending change, including edits other people made in the GTM UI. |
+
+Safety gates specific to GTM:
+- **Custom HTML** runs arbitrary JavaScript on your site, so creating or editing an `html` tag — or publishing a workspace that adds or changes one — is refused unless `gtm.allow_custom_html: true` is also set. Pausing or deleting one is always allowed.
+- **No stale writes.** Updates and deletes pin the entity's fingerprint from the preview, and publish pins the workspace's pending changes; if someone edits the container in between, apply refuses and you re-draft.
+- Publishing stops on merge conflicts or GTM compiler errors. The dry run runs a Tag Manager **quick preview** first (Tag Manager has no validate-only mode), so compiler errors surface before a version is even created. That preview is a POST and stores a preview version in the container — nothing is published and no live tag changes; the rest of the dry run only reads.
+- The publish result names the version it replaced (`previous_live_version_id`), so rolling back is one step: publish that version again in the GTM UI. If the version was created but publishing it failed, the error carries both the created version id and the still-live one.
+- Per-operation names for `safety.blocked_operations`: `gtm_create_tag`, `gtm_update_tag`, `gtm_delete_tag`, `gtm_create_trigger`, `gtm_update_trigger`, `gtm_delete_trigger`, `gtm_publish_workspace`.
+
+The Google account also needs **Edit** permission on the container (and **Publish** to publish) under Admin → User Management.
+
 > **Setup for GTM tools** — Enable the **Tag Manager API v2** in your GCP project, then add your AdLoop credentials' email (the OAuth user, or the service account email if using a service account) as a **Read** user on the GTM container under Admin → User Management. Service accounts pick up access on the next call. **OAuth users upgrading from an earlier AdLoop version must re-authorize once**: the GTM scope is new, so delete `~/.adloop/token.json` and run any tool to re-consent — until then GTM tools return a permissions error.
 
 ### Search Console Tools
@@ -488,7 +508,7 @@ Most MCP clients (claude.ai, ChatGPT, Cursor, …) load **every tool schema into
 | `ads` | Google Ads reads, writes, and planning (Keyword Planner) |
 | `ga4` | Google Analytics reports, realtime, key events |
 | `tracking` | Cross-channel attribution + tracking code generation |
-| `gtm` | Google Tag Manager audits and reads |
+| `gtm` | Google Tag Manager audits, reads, and opt-in writes |
 | `gsc` | Search Console reads |
 | `web` | PageSpeed / Core Web Vitals |
 | `merchant` | Merchant Center feed health |

{adloop-0.19.6 → adloop-0.21.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "adloop"
-version = "0.19.6"
+version = "0.21.0"
 description = "The AI command center for Google Ads, Reddit Ads, GA4, and tracking code."
 readme = "README.md"
 requires-python = ">=3.11"
@@ -21,6 +21,7 @@ dependencies = [
     "google-api-python-client>=2.100.0",
     "google-auth-oauthlib>=1.0.0",
     "google-api-python-client>=2.0.0",
+    "phonenumbers>=8.13",
     "pyyaml>=6.0",
     "requests>=2.31",
 ]

{adloop-0.19.6 → adloop-0.21.0}/pyproject.toml.orig

@@ -1,6 +1,6 @@
 [project]
 name = "adloop"
-version = "0.19.6"
+version = "0.21.0"
 description = "The AI command center for Google Ads, Reddit Ads, GA4, and tracking code."
 readme = "README.md"
 authors = [
@@ -17,6 +17,7 @@ dependencies = [
     "google-api-python-client>=2.100.0",
     "google-auth-oauthlib>=1.0.0",
     "google-api-python-client>=2.0.0",
+    "phonenumbers>=8.13",
     "pyyaml>=6.0",
     # Reddit Ads has no SDK; the REST client (adloop.reddit.client) and the
     # PageSpeed helper call requests directly.