---
name: google-ads-conversion-tracking-check
description: "Each morning: Google Ads conversion actions that went silent for 48 hours while clicks kept coming, with a question about what changed on the site. Use when the user asks for this, or when it runs on a schedule."
---

# Google Ads conversion tracking check

Each morning: Google Ads conversion actions that went silent for 48 hours while clicks kept coming, with a question about what changed on the site.

When a purchase tag breaks, Google Ads does not stop spending. Smart Bidding sees fewer conversions, lowers its estimates, and starts bidding on the wrong traffic, while ROAS and CPA reports describe a market that does not exist. The usual trigger is a site release, a new checkout or a consent banner, and the usual discovery is a week later.

This skill checks each enabled conversion action against its own normal daily volume. When one that usually fires every day has been silent for two days while ad clicks look normal, it asks you about the tag, which is the cheapest moment to find it.

## Two ways to get the data

Use the API or MCP route when you have an MCP server, a CLI or an API token for the app. Otherwise, if you can drive a browser the user is signed in to (Claude in Chrome, a Playwright or Chrome DevTools MCP server), use the browser route. Say which one you used.

## Route A: API or MCP server

### What you need

- Read access to the Google Ads account and its customer ID.
- The read-only Google Ads MCP server, or Google Ads API OAuth credentials, to run GAQL.

If something is missing, say what and stop; do not invent numbers.

### Steps

1. **List the conversion actions** (Google Ads): Query `SELECT conversion_action.resource_name, conversion_action.name, conversion_action.type, conversion_action.category, conversion_action.status, conversion_action.primary_for_goal FROM conversion_action WHERE conversion_action.status = 'ENABLED'`.
2. **Count conversions per action per day** (Google Ads): Query `SELECT segments.conversion_action, segments.date, metrics.all_conversions_by_conversion_date FROM campaign WHERE segments.date DURING LAST_30_DAYS` and sum across campaigns. The by-conversion-date metric puts each conversion on the day it happened, not the day of the click. Actions with no rows had zero conversions.
3. **Check the traffic** (Google Ads): Pull `metrics.clicks` by `segments.date` from `customer` for the same 30 days. If clicks in the last 48 hours are within 30% of normal, a silent action points at tracking; if clicks fell too, it is a traffic problem.
4. **Decide what is broken**: Silent: averaged 1 or more a day over days 3 to 30 back and recorded 0 in the last 48 hours. Down sharply: under a quarter of its usual 48-hour count. Never fires: enabled, 0 in 30 days. Primary actions come first, since they steer bidding.
5. **Ask about the tag**: Post an action card naming the action, its type, the last day it recorded anything and the click volume since. With nothing wrong, update the card to "all conversion actions recording" so you know the check ran.

## Route B: the browser

### What you need

- Signed in to Google with a user that has at least Read only access to the Google Ads account.

If something is missing, say what and stop; do not invent numbers.

### Steps

Start at https://ads.google.com/aw/conversions. The user is signed in already; never type passwords or codes, and ask if a sign-in page appears.

1. **Open the conversion summary**: In Google Ads, open **Goals > Conversions > Summary** and pick the account if more than one is listed. Set the date range to **Last 30 days**. The table lists every conversion action with its type, its **Status** (`Recording conversions`, `No recent conversions`, `Inactive`) and whether it is **Primary** or **Secondary**.
2. **Build a per-day report**: The summary has no daily split, so open **Campaigns > Insights and reports > Report editor**, create a table with the rows `Conversion action` and `Day`, the column `All conv. (by conv. time)`, and the same 30-day range. Download it as CSV if it runs past a screen.
3. **Read account clicks for the same days**: Back on **Campaigns**, set **Last 30 days**, segment by **Time > Day** and read the `Clicks` total row for each of the last 2 days against the 28 before.
4. **Decide what is broken**: Silent: averaged 1 or more a day over days 3 to 30 back and 0 in the last 48 hours. Down sharply: under a quarter of its usual 48-hour count. Never fires: enabled, 0 in 30 days. If clicks in the last 48 hours are within 30% of normal, blame tracking; if clicks fell too, blame traffic.

Note: The Status column in the conversion summary is the same signal, but it can lag by days; the per-day report finds a silent tag sooner. Report editor saves nothing unless you ask it to, so the browser route builds the table fresh each day.

## The report

- **Silent actions**: name, type, last day with a conversion, usual daily count.
- **Sharp drops**: actions recording a fraction of their normal volume.
- **Never fires**: enabled actions with nothing in 30 days, often leftovers to remove.
- **Clicks** over the same 48 hours, to separate tracking from traffic.
- The ask: what changed on the site, with quick replies.

## Post it to Briefkin

When `BRIEFKIN_TOKEN` is set, or `~/.config/briefkin/env` exists (the installer from https://briefkin.dev/docs writes it), also send the result to the user's Briefkin board as one card. Keep the `item_key` the same on every run so the card updates in place, use a new `event_id` per run, and put today's real numbers in place of the example ones. If the request fails, say so once and carry on.

```bash
[ -n "${BRIEFKIN_TOKEN:-}" ] || . ~/.config/briefkin/env
curl -sS -X POST "${BRIEFKIN_URL:-https://briefkin.dev}/v1/events" \
  -H "authorization: Bearer $BRIEFKIN_TOKEN" \
  -H "content-type: application/json" \
  -d @- <<'JSON'
{
  "v": 1,
  "event_id": "google-ads-conversion-tracking-check/<date of this run, e.g. 2026-10-16>",
  "item_key": "google-ads-conversion-tracking-check",
  "project": "Acme Store",
  "source": "Google Ads conversion tracking check skill",
  "kind": "action",
  "title": "Purchase conversions silent for 48 hours",
  "summary": "**Purchase** has recorded **0 conversions** since Wednesday 09:00, against about 41 a day before. Clicks over the same 48 hours were **3,920**, in line with normal, so the tag is the likely cause.",
  "action": {
    "request": "Did anything change on the checkout or order confirmation page on Wednesday morning? Purchase is a primary action, so Smart Bidding is already reacting.",
    "options": [
      "Checking the tag now",
      "Known: new checkout",
      "Sales really are down",
      "Snooze 24 hours"
    ]
  },
  "widget": {
    "type": "Table",
    "props": {
      "columns": [
        "Conversion action",
        "Type",
        "Last 48h",
        "Usual 48h",
        "Status"
      ],
      "align": [
        "left",
        "left",
        "right",
        "right",
        "left"
      ],
      "rows": [
        [
          "Purchase",
          "Website",
          0,
          82,
          "Silent"
        ],
        [
          "Add to cart",
          "Website",
          1264,
          1280,
          "OK"
        ],
        [
          "Lead form",
          "Website",
          18,
          17,
          "OK"
        ],
        [
          "Calls from ads",
          "Call",
          6,
          7,
          "OK"
        ],
        [
          "Newsletter signup",
          "GA4 import",
          0,
          0,
          "Nothing in 30 days"
        ]
      ]
    }
  }
}
JSON
```

Widgets come from the Briefkin catalog (https://briefkin.dev/v1/catalog). Without a token, just give the user the report.

## Run it on a schedule

Suggested: Every day at 10:00 (`0 10 * * *`). From cron, with the agent signed in on that machine:

```bash
0 10 * * * claude -p "Run the google-ads-conversion-tracking-check skill"
# Codex: codex exec, Gemini CLI: gemini -p, Copilot CLI: copilot -p, OpenCode: opencode run
```

Or use the agent's own scheduler (Claude Code routines, Codex automations, Claude or ChatGPT scheduled tasks): https://briefkin.dev/skills/google-ads-conversion-tracking-check#schedule

Source: https://briefkin.dev/skills/google-ads-conversion-tracking-check
