Andrey VengeretcGoogle AdX and AdSense monetization research
English
LinkedIn
AuctionsTrafficPatentsAnalytics
Andrey Vengeretc

Andrey Vengeretc

Google Ad Exchange and AdSense monetization · I research programmatic auction mechanics and invalid traffic detection using Google patents and antitrust case materials

6 years in monetization · 1,000 sites have passed through my hands · I work with publishers and MCM partners

Beyond the research I build ad formats of my own. The first is a scratch banner that raises the price of the ad next to it — a working prototype with the economics laid out.

563documents in the base
206Google patents
4models per analysis

Hello, friend

Why CPM drops in AdX and AdSense — an AI model answers from Google's own patents

I have spent six years on Google Ad Exchange (AdX) and AdSense monetization; a thousand sites have passed through my hands. My answers do not come from second-hand retellings or support macros — they come from Google's own patents and from the materials of the antitrust case against it.

● Free, no signup

Ask it yourself — right now

Don't take my word for it. Ask your own question and see what the model says: every answer arrives with the list of documents behind it and a screenshot of the exact page the quote came from.

Why did my CPM drop after I changed the floor price?

I charge nothing and sell nothing. To keep the bots out, access is password-protected — message me on Telegram or LinkedIn and I will send it over.

The uncomfortable truth about our market

Let me be blunt: most MCM partners do not understand it either. Their work comes down to poking at GAM settings — nudge a floor, watch, roll back. I know dozens of MCMs who lost their status because they onboarded publishers with bad traffic and could not see it coming.

It is not laziness. It is that Google's public documentation describes the rules, not the mechanics. It cannot tell you why your traffic was valued the way it was.

What I built

AI made it possible to stop reading other people's summaries and instead take the primary sources and build a system that answers from them.

206 Google patentsAuction mechanics, bids and CPM, invalid traffic detection, anti-fraud. Collected automatically from public registries.
302 antitrust case exhibitsInternal presentations, executive correspondence, sworn testimony. The court ordered both sides to publish them, and what normally never leaves the company came out.
55 court filings and transcriptsIncluding the April 17, 2025 ruling on the merits and the testimony of the head of Google's advertising systems.

Why a single AI cannot be trusted with this

At this volume any model starts inventing: it produces plausible percentages that are nowhere in the documents. I checked — they all do it. That is why every question goes through four passes by four different models.

Question breakdownThe question is split into independent parts so each can be searched separately. gpt-oss-120b
Evidence gatheringEach part is searched against the document base in its own pass, all at once. deepseek-v4-flash
SynthesisThe findings are assembled into one analysis with references to documents. qwen3-235b
VerificationThe analysis is checked against the sources, and anything not found in them is struck out. yandexgpt-32k

The verifying model is deliberately from a different family than the writing one: they fail differently, and what one invents the other will not confirm against the excerpts. It regularly catches invented percentages and non-existent names — which is the best proof the system works as intended.

Every answer comes with a page screenshot

Not a link to somewhere out there, but the specific patent sheet or presentation slide the quote came from. The system finds the right page by matching the text of the excerpt against the text of every page in the document.

Narrow subjects live in separate stores

The main base answers questions about auctions, bids and invalid traffic. But there are adjacent subjects that cannot be dumped into it: the system pulls twenty excerpts per question, and that is a hard ceiling. Put CAPTCHA patents in there and they start winning space away from IVT patents on the very questions where IVT is what you need.

So each such subject gets its own store and its own agent, and the code decides which one to ask based on the wording of the question:

Human verificationCAPTCHA, challenges, risk scoring, telling a bot from a personWeb analyticsevents and sessions, conversions, attribution, cross-device linkingAd serverAd Manager, Open Bidding, line item priority, server-side biddingContent qualitypage classification, keywords, publisher eligibility

Ask about CAPTCHA and the specialist agent joins in with its own base, its material marked separately in the combined answer. Ask about auctions and it stays out of the way entirely.

A story of its own: video from the case exhibits

How a recording that sat in the base as dead weight became one of the most cited documents.

Among the case exhibits there is a fourteen-minute video. The storage accepted it as video and extracted nothing: no audio, no text, no images. I checked all 878 excerpts the system had cited in its answers — this recording appeared not once.

Inside were two layers, and both valuable. On screen, Google slides about the move to a first-price auction, with the explicit line "no last look for programmatic". Below them, a transcript burned into the frame as subtitles, numbered by page and line. Real people are talking: the Exchange Bidding product manager explains the changes, publisher representatives push back.

"All that control — and control is the real keyword here — is going to be lifted from us, and we just have to hope Google is acting in our best interest. That is a lot to swallow" — from the publisher side, lines 40:4–40:7.

What I did with it

No speech recognition was needed: the text was already on screen, and it carried transcript page numbers that the audio does not have at all. I found the exact bounds of the subtitle strip, cut it out of frames every second and a half, and ran it through text recognition.

288 transcript linesFrom page 11 through 96. Lines are merged by their "page:line" number, so there are no duplicates — a single line stays on screen for several frames.
3 presentation slidesFound by comparing frame fingerprints and kept whole, together with what was said while each was up.
17 pages in the finished documentA slide and what was said over it, then the full transcript. An ordinary PDF with real text — search and page screenshots work on it.

Two checks paid off. Deposition transcripts run twenty-five lines to a page, so lines numbered 33 and 34 were recognition errors and I dropped them. And I re-sampled the gaps in the numbering at half-second intervals: not a single line was added, which means those are genuine edit cuts. Only excerpts were entered into evidence, not the whole recording — now that is verified rather than assumed.

The result

A recording that had never once taken part in an answer is now cited alongside the patents. Ask about per-buyer floor prices and the system answers with a reference to it — and shows you the page.

What it has already shown

Four findings that change how you configure monetization. I verified each one myself in the source documents.

65 of 100

is what reaches the publisher

Out of a hundred advertiser dollars. Twenty go to the exchange. This is not an outside estimate — it is Google's own slide, entered into evidence.

85%

of auctions carried two of its own bids

In a second-price auction the winner pays the next bid down. If both top bids belong to the same buyer, that buyer sets its own price.

× 0

traffic is not rejected — it is discounted

The patent describes not "good" and "bad" traffic but zones with a discount coefficient: 0.5, then 0.3, then zero. No notification is sent.

2 sec

the short click is the key signal

The person clicked through and came straight back. It is the share of such clicks that moves you into the discount zone. That is ad relevance and page speed, not bots.

"In auctions where GDN second-prices itself, Bernanke allows >14% margin capture" — the caption on Google's own slide, entered into evidence.

Try it yourself

The research is open in two forms. One is a finished analysis you can simply read. The other is live access to the system, where you can ask your own question.

Finished analysis

Case analysis

Twelve sections on how money and fraud actually work in Google advertising. Auction mechanics, where the fees go, how invalid traffic is caught, and why traffic gets discounted instead of rejected.

  • Diagrams that explain the mechanics
  • Screenshots of source pages
  • Every claim linked to its document
Open the analysis
In real time

Ask the system

Ask your question and get an answer from the documents in about ten seconds. For a hard question there is deep analysis: it is split into parts, each searched separately, and the result is checked against the sources by a different model.

  • An answer with the documents it rests on
  • A screenshot of the page the quote came from
  • Search across a catalogue of 563 sources
Ask a question

Password-protected access — message me and I will send it over.

What this gives you

I am not selling a way around anti-fraud — there isn't one, and attempts end with a lost account. I am offering something else: understanding what is happening to your traffic and why.

Once you know the mechanics you stop poking at settings blindly. You see which signals are collected about you, which of them you can change and which you cannot. And you know in advance how taking on the next traffic source will end.

Let's stay in touch

Follow me on LinkedIn so our contacts are kept and you don't lose track of the research. I publish analyses as the base grows.

Follow on LinkedIn Message on Telegram