Repository navigation
new suspected_bot metric for interaction ping - #22
Merged
Merged
Conversation
efixler
approved these changes
Oct 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:""(empty)over_limitstaleIt'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.