Above the Fold: May 11, 2026

by

Above the Fold: May 11, 2026

BY ROB BEELER

This information is confidential and for the internal use of our partners only. The Above the Fold Report is an amalgamation of the discussions taking place within the Beeler.Tech universe.

Much of what is presented is based on conversations held behind closed doors within the last week. The topics will range from existential threats to publishers down to questions about how to use a specific feature in an ad server. If you are a publisher or someone who works with publishers, all of these provide opportunities to help or learn. The report’s format varies based on the conversations.

Top Topics Discussed This Week

AI Consumer Adoption Plateau?: AI consumer apps may be hitting a growth plateau, but that does not necessarily mean AI adoption is slowing. A more likely explanation is that most consumers will continue using AI through browsers or embedded assistants until agentic tools become simple, reliable, and “spoon-fed” through familiar app experiences. The current slowdown may reflect friction in distribution, marketing, and behavior change more than a lack of demand.

Several people argued that the strongest near-term AI economics are in enterprise, where companies have budgets, urgent use cases, and high switching costs. Tools like Claude Code become embedded in workflows, making replacement difficult once teams build around them. In that sense, enterprise AI has a clearer path to durable revenue than standalone consumer apps.

The broader point: AI has made building and shipping software easier, which means the build itself is no longer the moat. Success now depends on whether the problem is painful enough, whether the product truly fits the market, and whether the company has access to data others cannot easily replicate. Mediocre products can still win when they solve a severe enough pain point.

The conversation also turned to whether apps themselves remain necessary. If assistants can call MCPs and surface “playable cards” with core app functionality, then many consumer apps may become backend services exposed through AI interfaces. That could matter for publishers too: instead of AI summarizing content and sending a hyperlink, a publisher MCP could return an interactive content card with the publisher’s UI, monetization, and ad placements intact.

Still, mass disruption will take time. Consumers are not all power users, and adoption will likely move in waves based on technical comfort. Existing apps with strong footprints may survive by integrating AI features, while new apps face the old realities of marketing, pricing, and distribution.

The strongest moat may be data: customer data, commerce data, workflow data, supply-path data, location data, or any dataset that takes time to build and helps agents act. Data is the food AI agents consume.

New Slack Channel for Mobile UX Experiences: A new community Slack channel has been created to discuss mobile app ad experiences, with an initial focus on interstitials. The goal is to build consensus around baseline expectations for a UX-friendly interstitial template, not to “fix” the most aggressive templates one by one. We will share a first draft of Mobile App Experience principles for comment, with the goal of establishing a common floor and possible pathways toward more native fullscreen ad experiences.

The linked post argues that mobile app interstitials have steadily degraded publisher UX. Publishers often lack meaningful control once an interstitial is shown, while ad networks default toward aggressive settings designed to maximize yield. That creates a mismatch: networks optimize for impression-level revenue, while publishers have to protect long-term user retention, trust, and lifetime value.

Specific pain points include tiny or hidden close buttons, misleading “next” buttons, excessive end cards, confusing timers, broken creatives, and templates that appear designed to prolong exposure or trigger accidental clicks. The broader issue is that publishers are ceding app UX control to partners whose incentives may not align with audience experience.

The proposed path forward is to define reasonable controls over interstitial UX elements, allow declared publisher overrides, and acknowledge that better UX may mean lower yield per impression but healthier long-term value.

Sensitive Click Ads – Opera DSP: Opera Ads creatives appear to be generating false clicks during normal mobile scrolling. The issue seems tied to Opera’s custom touch-based click-detection SDK, specifically in tpl_generic_d_e_v1.js, rather than to native browser click handling.

The SDK listens for touchstart and touchend, calls stopPropagation(), and treats a touch as a valid click if it lasts less than 500ms and the finger moves less than 20px. That logic misses an important scroll case: during feed scrolling, the page moves while the finger’s viewport-relative position may barely change. As a result, a user scrolling past a 300×250 Opera creative can be counted as a click, even when no intentional tap occurs.

This was reproduced on iOS using Chrome mobile emulation and on a real Android device. By contrast, Google native ad templates rely on standard browser click events, which are generally canceled during scroll gestures. Those did not show the same sensitive-click behavior in testing.

The concern is that Opera’s SDK bypasses native scroll/tap disambiguation, potentially inflating click activity. Publishers seeing unusual CTR, accidental landings, poor post-click engagement, or user complaints about Opera demand should consider testing Opera creatives specifically, isolating mobile feed placements, and asking Opera whether their template supports native click handling or accounts for page scroll distance before firing.

AdMob: A publisher asked whether anyone uses AdMob and could share a contact, hoping to test it against other demand sources. One respondent said they use AdMob but are not enthusiastic about it, and would choose GAM plus Open Bidding if starting over. Another noted that AdMob likely will not bring meaningfully different demand from GAM, since it is essentially similar to Google demand without direct ad serving. They suggested leveraging a GAM rep or signing up directly online.

Smile Wanted: A publisher asked about Smile Wanted, a French SSP expanding from the UK into the US, and what demand value they bring. Feedback was cautious: one respondent had prior concerns about their practices. Their pitch appears to center on an AI curation layer for PMPs plus French/EU brand demand seeking US audiences.

OMS/Salesforce: Publishers using an OMS with Salesforce CRM generally seem to track seller revenue forecasts and percent-to-goal in the CRM, especially when Salesforce is where sellers already manage pipeline and daily activity. One reason is that earlier-stage deals may not yet have been pushed into the OMS, so Salesforce provides a fuller view of seller performance and forecasts.

That said, some teams use both systems depending on role and workflow. Boostr has native dashboards for this use case, while FatTail/AdBook supports pushing OMS data into Salesforce for dashboarding. In that setup, Salesforce may be the visualization layer, but the OMS remains the revenue system of record.

Developing Discussions

  • Does anyone have a recommendation for an agency to support on Direct Sales in the EU or LATAM? (Axiom Media mentioned for UK/EU)
  • Is anyone seeing a revenue lift with OpenAds? Still on the fence about implementing, esp with recent TTD agency fallout news
  •  I’m looking for programmatic fill for my international users (the largest market is India). Does anyone have experience in Non-US programmatic?
  • Can every publisher please, please, please ask your Google rep to make the change history accessible via API? Please, please, please.  Imagine a world where your discrepancy analysis agent checks your game changelogs automatically and finds the problems
  • Is anyone here actively working with AnyClip on video monetization? (response: Just saw that AnyClip entered insolvency in case anyone is working with them.)
  • Does anyone know how we can ensure vertical video renders on vertical ad requests in Prebid? Outside of just trying to match the player size to the size or aspect ratio of the video?
  • Is anyone working with Pushly for push notifications and willing to chat?