Google Ad Fraud Report — Spendraven

2026-06-04 · Ben · audit

Google Ad Fraud Report — Spendraven

Status: scaffold — awaiting the report. Created as a tracked task; the findings, impact, and action items below are placeholders to be filled from the actual Spendraven report.

BLUF: (one line — what Spendraven flagged and the headline cost/impact, once known)

Audit finding (2026-06-04): Spendraven is already integrated — cdn.spendraven.com/r.js runs on the live site and shows as a resource error on ~224 sessions/30d in itbroke. So Spendraven is a vendor we're paying/running, not a cold pitch. Two actions fall out: (1) confirm the script is firing (resource errors are partly ad-blocker noise, but verify it's not 404/misconfigured), and (2) this is the lens for the report — they have on-site data on our paid traffic. Pair with the OpenAI lead pixel (also on-site, also erroring) when checking conversion-tracking integrity.

Source

• From: Spendraven (vendor / tool / contact — confirm what Spendraven is and our relationship)
• Received: (date)
• Scope: Google Ads account(s) / campaigns covered (confirm which account — Michael's?)
• Report artifact: (link or attachment reference)

What the report claims

(Summarize Spendraven's findings. Typical ad-fraud report contents:)

• Invalid / fraudulent click volume and %

• Suspect sources (IPs, placements, geos, devices, bot signatures)

• Time window analyzed

• Estimated wasted spend

• Capture the specific claims here

Impact

• Wasted spend (claimed): (amount / %)
• Campaigns affected: (list)
• Confidence: (is the methodology credible, or is this a sales pitch? — verify before acting)

Recommended actions (ROI-ranked)

(To be filled once findings are in. Likely candidates:)

• Verify the claim independently against Google Ads' own Invalid Clicks / IVT data before paying for or acting on it
• If credible: exclude flagged IP ranges / placements; tighten geo + device targeting
• File for Google ad credits on confirmed invalid traffic
• Decide whether Spendraven's protection service is worth the fee vs Google's built-in IVT filtering

Decisions / dependencies

• Owner: (who runs Google Ads — Michael?)
• Is Spendraven a paid vendor or a prospecting pitch? (this changes how much weight the report gets)
• Blocking: need the report contents + Google Ads access to validate

Done when

• Claims validated (or dismissed) against Google's own invalid-traffic data
• Confirmed wasted spend recovered via ad credits where applicable
• Decision made on Spendraven (engage / decline) with rationale recorded