Find out the day a Google Ads conversion tag stops firing

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.

Runs
Every day at 10:00
Posts
Asks you

From your apps to your board

How the skill works: your agent reads conversion actions from Google Ads; google ads customer id from What you tell it, every day at 10:00, and gives you a question for you and a telegram ping and the report in the chat.

Reads

  • Google AdsConversion actions
  • What you tell itGoogle Ads customer ID
reads
Your agentClaude Code, Codex, Cursor or GeminiEvery day at 10:00
posts

You get

  • A question for youOn your board, answered with a tap
  • A Telegram pingOnly when it needs your answer, if you connect Telegram
  • The report in the chatEvery run, with or without Briefkin

What you get

  • 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.

The card on the right is a sample. Yours shows your own numbers and updates in place every run.

What lands on your board

Acme StoreGoogle Ads conversion tracking check · Claude Code

Purchase conversions silent for 48 hours

Did anything change on the checkout or order confirmation page on Wednesday morning? Purchase is a primary action, so Smart Bidding is already reacting.

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.

Conversion actionTypeLast 48hUsual 48hStatus
PurchaseWebsite082Silent
Add to cartWebsite1,2641,280OK
Lead formWebsite1817OK
Calls from adsCall67OK
Newsletter signupGA4 import00Nothing in 30 days
Resolve
An example with made-up numbers. Your agent posts your real ones.

What it does

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.

How it works

  1. 1List the conversion actions

    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. 2Count conversions per action per day

    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. 3Check the traffic

    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. 4

    4Decide 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. 5

    5Ask 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.

  6. Post it to the board

    With BRIEFKIN_TOKEN set, the agent sends the result as one card that updates in place every run. Without it, you get the report in the chat.

Install and run it

Pick your agent, where the data comes from and how to schedule it; the commands below follow.

Agent
Data
Schedule
  1. Install the skill

    One command. It puts the SKILL.md in ~/.claude/skills and in ~/.agents/skills, which Codex, Cursor, Gemini CLI, Copilot CLI and OpenCode read too.

    shellcurl -fsSL https://briefkin.dev/skills/google-ads-conversion-tracking-check/install | sh
  2. Run it

    Ask Claude Code:

    promptRun the google-ads-conversion-tracking-check skill

    Or paste the prompt instead of installing:

    promptUsing the Google Ads API, list my enabled conversion actions (name, type, status, primary_for_goal). Then get daily all_conversions_by_conversion_date per conversion action for the last 30 days (segment by conversion_action from the campaign resource and sum across campaigns), and daily clicks for the account. Flag any action that averaged at least 1 conversion a day over days 3 to 30 back but recorded 0 in the last 48 hours, any action under a quarter of its usual 48-hour count, and enabled actions with nothing in 30 days. Tell me whether clicks over the last 48 hours were normal, so I know whether it is tracking or traffic, and ask me what changed on the site.
  3. Put it on a schedule

    Every day at 10:00, from cron on any machine where Claude Code is signed in:

    crontab0 10 * * * claude -p "Run the google-ads-conversion-tracking-check skill"

    Add it with crontab -e. A laptop asleep at that time runs it when it wakes if you use launchd or Task Scheduler instead; GitHub Actions works for the API route.

  4. Send it to your board

    Connect Briefkin once with curl -fsSL https://briefkin.dev/install | sh and every run lands on your board as a question for you. How setup works

View the SKILL.mdRaw file
SKILL.md---
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

What your agent needs

  • 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.

Connecting Google Ads

  1. Google Ads MCP server, Google's open-source, read-only server (google-ads-mcp, source). Run it locally with pipx run --spec git+https://github.com/googleads/google-ads-mcp.git google-ads-mcp, or deploy it to Cloud Run for remote clients. Its tools are list_accessible_customers, search for GAQL and get_resource_metadata (docs).
  2. Google Ads API with OAuth. Enable the Google Ads API in a Google Cloud project, sign in with Application Default Credentials (gcloud auth application-default login with the adwords scope) or an OAuth client, and set GOOGLE_PROJECT_ID. Add GOOGLE_ADS_LOGIN_CUSTOMER_ID when you reach client accounts through a manager account, and write customer IDs without dashes.

The adwords scope can't be narrowed, so sign in as a Google Ads user with Read only access; the MCP server has no write tools either way.

Questions

Does it see the "No recent conversions" status from the Google Ads UI?

It does not rely on it. The skill rebuilds the same signal from daily counts, which is faster: the UI status can take days to change, while a primary action that normally fires 40 times a day and then stops is visible after 48 hours.

What about actions that only fire a few times a week?

Below one conversion a day, two silent days are normal, so those actions are skipped by the 48-hour rule. They still appear under "never fires" after 30 empty days. For a low-volume action that matters, set its own window in the skill, for example 7 days.

Do I need Briefkin to use the Google Ads conversion tracking check skill?

No. The skill runs with your own agent and gives you the report in the chat. With a Briefkin token set, each run also posts it to your board as a asks you, so you can glance at it instead of asking again.

Which agents can run it?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot CLI, OpenCode, Windsurf and Amp all read SKILL.md files. The install command puts it in ~/.claude/skills and ~/.agents/skills, where they look. ChatGPT, the Claude app and Grok take the prompt instead. Pick your agent under "Install and run it" and the commands change to match.

Can it work without an API or MCP server, from my browser?

Yes. Switch the data source to "Your browser" and the steps change to the Google Ads pages themselves: the agent opens ads.google.com/aw/conversions in a browser you are signed in to and reads the numbers off the page. Claude Code, Codex, Cursor, Claude app and ChatGPT can drive a browser out of the box; Gemini CLI, Copilot CLI and OpenCode need a Playwright or Chrome DevTools MCP server first. It is slower than the API and needs you signed in, so it suits a report you run by hand or from a scheduler on your own computer.

Answer your agents from one board, or from Telegram

Skills are free to use with any agent. Briefkin is where their results land: one board for every report, number and question your agents send, with a ping when something needs you.

Free during the open beta. No card.