Audits how conversion actions are configured — legacy attribution models, purchase/lead counting mismatches, odd lookback windows, and primary-action overload — the settings that shape every CPA and are never reviewed after setup.
by Dmytro Tonkikh·chiliad.io
Monitors your account for unexpected performance deviations by comparing today's stats against historical averages for the same weekday. Sends an alert email when impressions, clicks, conversions, or cost deviate beyond configurable thresholds.
One 0-100 score for the whole account, built from seven objective checks — tracking flatlines, disapprovals, serving status, budget losses, negative coverage and query hygiene — with the deduction breakdown as your fix list.
Finds the structural gaps that stop ad groups from serving: ad groups without active ads, without an RSA, without keywords, keyword-stuffed themes, and multi-RSA ad groups.
Generates a daily at-a-glance performance overview of your entire Google Ads account. Writes prior-day stats to a Google Sheet with running history and optionally emails a formatted comparison of yesterday vs. two days ago vs. one week ago.
Generates a Google Spreadsheet with ad performance stats segmented by headline and final URL, including distribution charts. Covers all ad types and optionally emails the report link weekly.
Maps every campaign's ad schedule and flags forgotten narrow serving windows, stale schedule bid modifiers that Smart Bidding ignores, and (optionally) campaigns running 24/7.
Conversion actions get configured once and reviewed never — while their settings shape every number in the account. This audit checks each enabled action for four issues: attribution models that aren't data-driven (last-click starves upper-funnel campaigns of credit), counting mismatches (purchases on one-per-click undercount repeat orders; leads on every-conversion inflate on double submits), click-through lookback windows under 7 or over 90 days, and categories with many primary actions all feeding the Conversions column (double-counting risk).
| Variable | Default |
|---|---|
EMAIL_ADDRESS | (empty) |
=== Conversion Settings Audit === Enabled conversion actions: 6 Findings: 3 - LEGACY ATTRIBUTION: "Purchase — website" uses LAST_CLICK. Switch to data-driven attribution unless there is a specific reason not to. - COUNTING MISMATCH: "Lead form submit" (lead) counts every conversion - double form submits inflate the numbers. Use one-per-click for leads. - ODD LOOKBACK: "Newsletter signup" has a 3-day click-through window. Verify it matches the sales cycle. Email sent to you@example.com
Some action types (store visits, certain imports) can't use data-driven attribution — verify before switching. Counting-type recommendations follow the standard convention: every-conversion for purchases, one-per-click for leads. Settings changes here affect reported history going forward, not retroactively.