MyWebReps · Evidence ledger
Every claim we make sits on this page until an instrument settles it.
Every entry carries a date, a claim with the number inside it, the instrument that measured it, and a verification state. No undated numbers, no placeholders. Clients are anonymized by trade unless written consent is on file.
How to read an entry
- Entry · date
- when it was filed, ISO, never renumbered
- Claim
- one flat sentence with the number inside it
- Instrument
- what measured it, named
- State
- earned by the pull, not styled
6 of 11 verified
- verified
- the instrument pull happened
- pending
- it has not happened yet
- refuted
- it failed and stays on the record
Entries 001 to 007.
Each entry links the program page it belongs to. Numbering is global and stable; entries are appended, never renumbered.
- entries
- 11
- verified
- 6
- pending
- 5
- refuted
- 0
| Entry | Claim | Instrument | Date | State |
|---|---|---|---|---|
| 001 | A mobile dog grooming company: 261 verified conversions in 30 days. Counted from the platform's own conversion ledger with Enhanced Conversions live on the account. | Google Ads API pull, Enhanced Conversions | verified | |
| 002 | Our own Q4 2025 ad flight sourced at least 5 of our 10 all-time pipeline deals. Seven conversions at $65 average CPC. The dashboard said pause. The pipeline said it was the best money the account ever spent. | Ads account and sales pipeline cross-check | verified | |
| 003 | We ran our rescue procedure on our own account. The findings publish with the bugs included. Four findings filed as entries 008 through 011, each paired with a dated fix state. | Self-audit, full procedure | pending | |
| 004 | A mobile cleaning company: 186 verified conversions in 30 days. | Google Ads API pull, verified conversion actions | verified | |
| 005 | A $750 fixed-scope rescue converted to a monthly retainer within five months. Findings first, retainer second. The order is the sales process. | Engagement records, February to July 2026 | verified | |
| 006 | A 23-account fleet QA sweep found live defects in 9 accounts, including our own. The checklist that runs on client accounts ran on ours and failed us too. Our defect is filed on the self-audit. | MCC-wide QA sweep, machine-executed checklist | verified | |
| 007 | A monthly operations program above ad management has run in production through 2026: campaign operations, landing page builds, tracking, and reporting. Delivered under codified doctrine by the agent fleet. The program shape is described on its page. | Work-management delivery log, all-items pull | verified |
Why this ledger is hard to cherry-pick.
A ledger that contains only wins is marketing with a date column. This one contains our own account: 29 paused campaigns, a live ad typo, unreconciled books, and a lead that never reached the pipeline board. Entries 008 through 011 are our own defects, filed with the same grammar as everything else and paired with dated fix states. They live on the self-audit exhibit and update as the fixes land.
008
All 29 campaigns paused
pending
009
Live ad typo
pending
010
Unreconciled books
pending
011
Lead never reached the board
pending
On the record
- What is on the MyWebReps proof ledger?
- Dated entries. Each states a claim, the instrument that measured it, and its verification state. No undated numbers, no placeholders.
- Does MyWebReps publish failures?
- Yes. The ledger includes our own self-audit, bugs included, with dated fix statuses.