MonetizeMore chief executive Kean Graham told publishers at a webinar organised with the Indonesian online media association AMSI that Google's invalid traffic enforcement can erase all unpaid ad revenue "overnight," and pitched the company's Traffic Cop detection tool, an AI assistant called Obi and an unreleased ad policy grader as the answer. The recording, titled "How Publishers Scale Ad Revenue & Prevent Policy Bans," was published on MonetizeMore's YouTube channel on October 8, 2026, the date used for this article.

In Short

A company that helps websites earn money from ads held an online session for Indonesian news publishers about why Google sometimes takes back money it owed them. Its boss said fake or accidental clicks on ads can get a site banned and its unpaid earnings cancelled, and that most publishers only take this seriously after it happens to them. The company used the session to sell its own tools, so the numbers and claims in it are the company's own and were not checked by anyone else.

The event and the sources

The session was billed on screen as "Smarter Monetization: Performance, Policy and Profits in Sync," hosted by MonetizeMore in collaboration with Asosiasi Media Siber Indonesia (AMSI). According to the moderator, AMSI is the national association of online media companies in Indonesia and has, since 2017, been "promoting credible journalism fighting misinformations and representing digital publishers across Indonesia."

The YouTube page for the recording shows an upload date of 08/10/2026 in a Portuguese-language interface, which reads as October 8, 2026. At the time the page was captured it had 11 views, 0 likes and no comments, and the channel had 7,400 subscribers. The video runs about 48 minutes. The page does not say when the webinar was streamed live, so the upload date is the only verifiable date.

According to the video description, the webinar was aimed at "mid-to-large publishers, media groups, and AdOps teams" and covered five topics: revenue blockers in Tier 1 and Tier 2 traffic, compliance strategy, PubGuru, Traffic Cop, and APAC case studies with a live Q&A.

Two people speak. The moderator describes herself as a senior account executive at MonetizeMore. The other speaker is Kean Graham, MonetizeMore's founder and chief executive, who according to the moderator "has led monetize more for over a decade."

Where the captions cannot be trusted

The quotes in this article come from YouTube's automatic captions, and those captions are unreliable on names. Graham's first name is rendered as "Kin," "Keen," "Ken" and "Kim" at different points. The association's acronym appears as "ANCI" and its name as "Associated Media Cyber Indonesia," while the video description gives "Asosiasi Media Siber Indonesia (AMSI)." The company's IVT product appears as "Traffic Cop," "Traffic Hop," "traffic comp," "traffic pop" and "trafficcom"; the video description confirms Traffic Cop. PubGuru appears as "pup guru" and "Pop guru." The AI assistant appears as "OBI" and "OB," and MonetizeMore's own blog names it Obi AI. The moderator's surname, captioned as "Matula," could not be confirmed and is not used here. Where a quote below contains a garbled product name, the correct name is given in square brackets.

The captions also garble at least two numbers in the case studies, which are discussed below.

Revenue in the interface versus revenue in the bank

Graham's central argument was about the gap between what a publisher sees in a dashboard and what is eventually paid. Publishers that cut corners on compliance can get short-term growth, he said, but Google "eventually" finds the violations.

"If Google doesn't detect it now they will eventually detect it and these punishments are very severe. So we're talking about all unpaid ad revenues uh disappearing overnight," Graham said in the recording. He added that publishers can lose "access to your Google ad revenue account which is the most important in terms of ad monetization."

He described the strictest category as invalid traffic: "whenever they detect say bot traffic that views or clicks on the ads any non-genuine clicks other types of ad setup policy violations." Revenue shown in the AdSense interface that is later clawed back, he said, "doesn't really mean anything." His summary: "at the end of the day, what's most important is what makes it to your bank account."

The concern is not hypothetical. Termination with withheld balances has been litigated in the United States. In May 2018, Google agreed to pay $11 million to settle a class action brought by Free Range Content on behalf of AdSense publishers terminated between May 20, 2010 and May 7, 2018 with withheld balances of $10 or more. The suit alleged that Google "improperly withheld unpaid amounts"; Google denied the claims.

Advertiser-friendly domains and testing

Asked about the biggest hidden revenue blockers in Tier 1 and Tier 2 traffic, Graham named making a domain "advertiser friendly" as one of the "invisible" ones. That meant, in his description, running ad formats that are good for user experience, preventing accidental or non-genuine clicks, keeping content brand safe and making sure traffic is "100% human."

The payoff, according to Graham, is bidder density. A domain that meets those conditions gets "a lot of different advertiser biders bidding on your ad inventory," including the most premium advertisers, which he said is "how you unlock uh the highest RPMs."

The second blocker he named was a lack of structured testing. He described running A/B or multivariate tests on layouts, ad formats and ad tech tools, and running a header bidding auction while testing which bidders, and how many, to include. Later in the session he said that "even moving say you know a display ad by like a few pixels can make a huge different for clickthrough rates."

Why publishers ignore compliance until they are burned

The moderator asked why many publishers treat policy compliance as an afterthought. Graham's answer was that the publishers who take it seriously "are usually the ones that have been burnt by it before."

"They've gone through a termination. Maybe they had a close call with a policy violation. Maybe they received a large revenue deduction because of invalid traffic and then they took it seriously," he said in the recording. "People don't really know how how uh damaging some of the this punishment can be until they actually feel it themselves."

He argued that compliance belongs in content creation and site redesigns, not a separate step, and linked it back to advertiser demand: a publisher that does not take a brand safety approach, he said, gets "blacklisted by some of the best advertisers out there and your RPMs will get impacted."

In-house teams and the case for outsourcing

On in-house ad operations teams, Graham acknowledged that large media companies want control over revenue that can reach "seven, eight, nine figures per year in programmatic ad revenues." What those teams lack, in his view, is a benchmark: "You don't really know the money that you're leaving on the table until you see what other websites are earning in similar vertical."

He listed the disciplines publishers now have to master, including SEO, "geo like the SEO for AI," community building, user-generated content and site design, and argued that adding monetization as a core competency "is in some cases like too much to ask for." Ad tech specialists, he said, "eat sleep and dream adtech."

That is the standard pitch of every managed monetization service, and MonetizeMore is not alone in making it. PPC Land has tracked how the entry thresholds for these services have fallen: as of January 2026, Raptive had cut its minimum to 25,000 monthly pageviews, Mediavine required $5,000 in annual ad revenue for its main platform, and Ezoic had removed pageview limits for new sign-ups.

Obi, the AI assistant for ad optimizers

Graham described Obi as an "AI co-pilot for ad optimizers," a counterpart to coding assistants for software engineers, for people who manage inventory through Google Ad Manager. According to Graham, it can explain why revenue or RPM moved, surface discrepancies between Google Ad Manager and SSPs, and answer compliance questions such as which ad units have the highest click spam or which traffic sources carry the highest invalid traffic percentage.

"You can uncover this with [Obi] in seconds," he said in the recording, contrasting it with the hours an analyst would otherwise spend pulling data from Google Ad Manager, several SSPs and a separate IVT vendor into a spreadsheet. In the Q&A, he said users can also ask Obi to analyse a page and suggest layout changes, and to edit charts it has generated "on the fly."

The webinar gave no figures on Obi's accuracy, pricing or adoption. Google itself has moved in the same direction: in November 2025 it added generative AI reporting to Ad Manager in beta, letting publishers build custom reports from natural-language prompts, with a warning to review the output.

How Traffic Cop works, according to MonetizeMore

Most of the technical detail in the session concerned Traffic Cop, which Graham said MonetizeMore released "in 2019" as "an AI driven solution." He also said the company has been "iterating that for six years now," which would place the present at 2025 rather than 2026; the discrepancy is in his remarks.

The mechanics he described are as follows. A JavaScript tag is placed on the page and wraps the ad units. Users judged high risk are shown a CAPTCHA. "If the user is able to solve the capta, then it's determined that it's actually a human user. Right? If not, it keeps the say the bot traffic away from viewing or clicking the ads," Graham said in the recording.

Graham drew the standard industry distinction between general invalid traffic, which "you can typically detect by, you know, looking at their IP address, if it's in a blacklist," and sophisticated invalid traffic, which he called "the most dangerous" and said can only be detected "on the page in real time." Traffic Cop runs "over a 100 checks" on users to estimate "the percentage risk that they're invalid or human," according to Graham, though he did not describe what those checks are.

Click categories and reports

On click spam, Graham said Traffic Cop separates multiple clicks by the same user, "bounce clicks," accidental clicks and invalid clicks, broken down by ad unit. He gave mobile "fat thumb clicks" near buttons as an example of placement-driven accidental clicks. "There's no other invalid traffic solution that offers this granular detail," he said, a competitive claim the webinar did not support with any comparison.

He also said Traffic Cop reports IVT percentages by country and by traffic source, so that publishers can stop buying traffic from bad sources. His illustration was hypothetical: a publisher seeing high IVT from "the Reddit traffic that I'm buying" and deciding to stop.

Graham listed "overlapping ads, aggressive refreshes, ads off the viewports" as ad setup violations that are "considered invalid traffic according to Google," and said "Google doesn't talk about those things in the terms and conditions." He said Traffic Cop flags them by page, screen size and ad unit. Google does publish ad placement and implementation policies for AdSense and Ad Manager; the webinar did not specify which behaviours Graham believes are missing from them.

What it does not cover

Asked whether Traffic Cop works for mobile apps, Graham said: "currently it is not available for mobile apps." He said MonetizeMore plans to add app support "eventually" and invited interested publishers to get in touch to help prioritise it. He gave no date.

Asked whether Traffic Cop is standalone or uses data from other Media Rating Council accredited partners, and how it differs from vendors such as Pixalate, Graham said it is standalone. MRC-accredited vendors, in his account, "mostly focus on the buy side" and none "are a monetization partner as well," so they lack the monetization data on which MonetizeMore built its models. He described Pixalate's domain scoring as based on "different signals" and said many signals those vendors use are "irrelevant to Google." The webinar did not say whether Traffic Cop holds any MRC accreditation.

The Google relationship claim

The most consequential claim in the session came in answer to an attendee who wrote that Google's policy team had seemed "quite inaccessible."

"This is definitely not accessible to like uh pretty much any publisher," Graham said in the recording. He said MonetizeMore has demoed Traffic Cop "to many of the the different Google offices ac across the world," has "taken a lot of feedback," and that Google is "very aware of what we've built and and very happy of what we've built." Earlier, he said the company has been a Google Certified Publishing Partner "for over 10 years" and has "conversations with the trust and safety team. So we understand how they make these decisions and we've incorporated it into [Traffic Cop]."

He went further, saying MonetizeMore had "looked under the hood" and was "privy to such uh uh important information to be able to prevent these terminations."

None of this was supported with documentation, and Google did not participate in the webinar. Certified Publishing Partner status, as the name indicates, certifies a company to manage Google publisher products for others. Nothing in the webinar indicates that Google has assessed Traffic Cop itself, and the session offered no statement from Google about the tool.

Graham also claimed that being "100% Google compliant" means a publisher is "compliant for all the other major SSPs, you know, even the Trade Desk, uh, App Nexus, you know, OpenX." The Trade Desk is a demand-side platform rather than an SSP, and buyers and exchanges each apply their own quality rules, so the claim reads as a generalisation rather than a documented equivalence.

The ad policy grader

In response to a publisher who said applications for Google Ad Manager and Ad Exchange had been rejected despite an invalid traffic rate "consistently below 1%" and 12 successful payments, Graham said "there is no restriction uh based on ECPI," his apparent reference to eCPM, and that rejections often turn on rules "more in the minutia" of Google's terms.

He described a tool "that we're going to be releasing soon called the ad policy grader." A publisher enters a domain; the tool scans its pages and returns a score out of 100, a comparison with other sites, and the results of "about a hundred checks," including the URLs and details of any violation. "It's kind of difficult because Google doesn't give actual reasons why they rejected a certain publisher," he said. Later in the session he referred to the grader as if it were available and said it already provides data for mobile apps; the session gave no launch date, so its status is unclear from the recording.

The rejected publisher's account matches a broader frustration PPC Land has documented. Google added policy ad serving status, Confirmed Click status and traffic source breakdowns to AdSense reporting, with policy data starting June 27, 2025, partly to give publishers more visibility into restrictions. The tools report status; they do not explain an Ad Exchange rejection.

Vendor figures and garbled numbers

The moderator presented two APAC case studies. Neither figure was independently verified, and both are partly garbled in the captions.

The first concerned Panlasang Pinoy, a Philippine site captioned as "panglasang pinoy," which the moderator said moved from relying only on AdSense to working with "10 plus demand partners" through PubGuru. The caption reads "a 2000 200 increase 200% increase in net ad revenue in just three years," which suggests the moderator corrected herself to 200%. No baseline revenue, start date or comparison with traffic growth was given.

The second concerned a publisher whose name is unintelligible in the captions (rendered as "job kaka"). According to the moderator, it was "losing more than 200% of revenue to clbacks from invalid traffic" and, after integrating Traffic Cop, "clack dropped to just 1%." A publisher cannot lose more than 100% of its revenue to clawbacks, so the first figure is either a captioning error or a misstatement; the recording does not make the intended number clear. The "1%" figure most likely refers to clawbacks as a share of revenue, but the caption does not say so.

The moderator also described PubGuru as offering "AI powered floor pricing by geo and ad unit," a form of dynamic price floor setting, plus real-time reporting with profit attribution. And she presented a commercial offer: a 0% revenue share for the first 30 days across PubGuru, Traffic Cop, compliance monitoring and reporting, with "no lockins." The webinar did not state the revenue share that applies after 30 days.

Audience questions on Ad Manager setup

One attendee asked whether creating an order and line item is necessary when creating an ad code for Ad Exchange. Graham said it is, when using Google Ad Manager with Ad Exchange "to compete against um you know the rest of the ad inventory," and that the ad code is generated within Google Ad Manager. On optimising revenue per ad unit and viewability, he recommended heat mapping tools as a "general rule of thumb" to place ads "where users tend to stop."

Why this matters for publishers

The webinar is a sales presentation, and that frames everything in it. Its value lies less in the product claims than in what a vendor serving APAC publishers chose to emphasise: that Google enforcement is opaque, that its consequences are financial and retroactive, and that publishers lack tools to see what Google sees.

That framing lands at a time when the open web is a shrinking line in Google's results. Google Network advertising revenue fell about 4% year on year to $6.97 billion in the first quarter of 2026. Enforcement volume is also large. Google data reproduced by the Video Advertising Bureau in September 2026 showed more than 245,000 publisher sites were actioned in 2025, through demonetization, ad termination or account suspension, and more than 480 million pages blocked or restricted.

Clawbacks are becoming more visible on the buy side, too. On October 6, 2026, Pixalate added a "Clawback Warning" label to its Media Ratings Terminal, marking apps and websites that buyers have disputed as invalid traffic within a rolling 12-month window, across more than 17.5 million properties. A publisher with a clawback history now risks being flagged to buyers, not only losing the clawed-back revenue.

Measurement rules are shifting as well. AdSense and Ad Manager banner inventory moves from count-on-download to begin-to-render impression counting on February 17, 2027, and Google has said publishers "may notice a decrease in total display impressions." Changes like that alter the RPM baselines that vendors such as MonetizeMore use to sell optimisation.

Platform reliability is a separate risk that no compliance tool addresses. Simultaneous Google Ad Manager and AdSense disruptions on January 13-14, 2026 cut publisher revenue by 50% to 90%, according to publisher reports at the time, with one US RPM falling from $110 to $23 in a day.

Google itself has invested in IVT detection with AI. In August 2025, it said a pilot using multimodal large language models cut mobile invalid traffic from deceptive or disruptive ads by 40%. If Google's own detection keeps getting better, the question for any third-party sell-side tool is whether it can stay ahead of Google's models, or only approximate them. Graham's answer was that close contact with Google gives MonetizeMore that edge. The webinar offered no way to check.

Then there is the gap the recording leaves open. Traffic Cop does not yet cover mobile apps, the environment where Pixalate's Q1 2025 research put invalid traffic at 31%, against 18% on the web.

Timeline

Summary

Who: MonetizeMore, a Google Certified Publishing Partner, represented by founder and chief executive Kean Graham and a senior account executive who moderated, in partnership with Asosiasi Media Siber Indonesia (AMSI), Indonesia's association of online media companies. The audience was APAC publishers, media groups and ad operations teams.

What: A roughly 48-minute webinar in which Graham argued that Google invalid traffic enforcement can erase unpaid revenue and terminate accounts, and described MonetizeMore's Traffic Cop IVT tool (JavaScript wrapper, CAPTCHA challenge, more than 100 checks, no mobile app support yet), its Obi AI assistant, an ad policy grader with about 100 checks, and PubGuru. Graham claimed input from Google's trust and safety team shaped Traffic Cop; the claim was not documented. Case study figures were vendor-supplied and partly garbled in the captions.

When: The recording was published on MonetizeMore's YouTube channel on October 8, 2026. The live broadcast date is not stated on the page.

Where: Online, with the recording at https://www.youtube.com/watch?v=mLTc0O71Ax0, aimed at publishers in Indonesia and the wider APAC region.

Why: Publishers face shrinking Google Network revenue, large-scale enforcement and growing scrutiny of clawbacks, and Google does not explain most rejections. MonetizeMore presented its tools as a way to see what Google enforces before it acts, which is also how the company sells its services.