Skip to content

new suspected_bot metric for interaction ping - #22

Merged
tanfarming merged 2 commits into
mainfrom
geng/suspected_bot
Oct 19, 2026
Merged

tanfarming merged 2 commits into
mainfrom
geng/suspected_bot

Conversation

@tanfarming

@tanfarming tanfarming commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

This adds one string metric, technical_operations.suspected_bot, to the MARS (ads_backend) interaction ping. It records why MARS's server-side detection flagged an ad interaction as suspected bot traffic (for example over_limit or stale), and is empty if the interaction wasn't flagged. It's Category 1 (Technical) and adds no new user data. We'll use it to exclude invalid traffic from impression and click reporting, and to tune detection.

Sample values for technical_operations.suspected_bot:

Value Meaning
"" (empty) Not flagged
over_limit Too many impressions/clicks for the same ad request within a short window
stale The ad was served longer ago than the detection policy's max age

It's a string rather than a boolean so it can carry the reason the detector returns. New reasons can be added in MARS without a schema change. Empty means not flagged.

@tanfarming
tanfarming requested a review from a team as a code owner October 15, 2026 13:35
@tanfarming
tanfarming merged commit a518fa6 into main Oct 19, 2026
2 checks passed
@tanfarming
tanfarming deleted the geng/suspected_bot branch October 19, 2026 16:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants