Set up your conversion tracking

/setup-google-ads-tracking

Run this from your AI editor (Claude Code, Cursor, Codex, or another MCP-capable IDE) with your product repository open.

If you're starting from Buron or the docs, copy this prompt into your IDE instead:

Check whether the Buron CLI is installed. If not, install the Buron CLI package with `npm install -g @buron/cli` (or `pnpm add -g @buron/cli` if this repo uses pnpm). Then run `buron setup` from the project root to link the repo, set up MCP, and install the skills.

Fetch the conversion tracking brief from Buron at `/ads/google/conversion-tracking.md` using the Buron MCP file tools if available, or with `buron file read /ads/google/conversion-tracking.md`.

Use the `setup-google-ads-tracking` skill to inspect this repo, set up any missing conversion tracking, validate what you can, and write the updated conversion tracking doc back to `/ads/google/conversion-tracking.md` through MCP or `buron file write`.

Conversion tracking is how Google Ads knows which actions matter to your business, like a signup, a purchase, or a demo booked. Buron uses your conversion data to calculate ROAS and surface findings about your campaigns.

How the skill works

The skill walks you through 4 phases.

1. Decide what to track. The skill confirms your sales motion, then helps you choose your primary conversion, your secondary events, and a value model for each. Every decision has a default for your motion. You can override any of them.
2. Audit your codebase. The skill checks whether each event fires in the right place and whether your app preserves gclid and UTMs through to the conversion. It also queries your Google Ads account to compare what's configured there against what your codebase emits.
3. Implement the gaps. Your editor's agent writes the code for any missing or broken tracking. The skill tells the agent what each event should look like.
4. Validate and finalize. The skill gives you a checklist to verify in GA4 DebugView, Tag Assistant, and your Google Ads conversions report. Once you confirm it works, the skill saves the spec to Buron.

What the skill saves

After validation, the skill saves 2 files to Buron.

• google-ads-conversions.md is the spec for what counts as a conversion.
• google-ads-tracking-status.md is the per-event audit results.

Buron uses these files as the source of truth. The Agent reads them when it surfaces findings, your reports use them to calculate ROAS, and your launches reference them when they need to point to a conversion metric.

Optional regression tests

The skill can write a regression test for each primary conversion in the testing framework your codebase already uses. The tests run on every PR through your existing CI, so drift gets caught early. The skill asks before adding them.

Re-run the skill

Re-run the skill any time. It reads the existing spec, audits your codebase against the current state, and writes any drift to the status file. Good times to re-run:

• Your sales motion changes
• You ship a major funnel change
• Once a quarter as a check-in

Use your conversion in Buron

After the spec is finalized, go to Settings in your Google Ads workspace. Under Conversion action, choose your primary conversion. This is the conversion Buron uses for your dashboard KPIs.

When you're ready to see what Buron finds in your account, check out Audit your account.