Reader Complaints About Ads and How I Respond

I read every ad complaint that reaches my inbox. Most are short: the page jumped, a video started talking, a box covered the recipe, or the close button was too small on a phone. I do not treat these as noise. If one reader takes time to write, others probably felt the same thing and left without saying anything.

My first step is to separate the complaint from the guess. I ask what page they were on, what device they used, and what happened just before the problem. I do not ask for personal details. A simple reply like “Was it a phone or a laptop, and did the ad cover the text?” usually gets enough context to reproduce the issue. If someone sends a screenshot, I note the placement, the size, and whether the page shifted before or after the ad appeared.

Then I check on a real phone. Not a desktop browser squeezed narrow, and not a clean test profile that blocks everything. I use an ordinary mid-range phone on a normal connection, open the same page, and scroll the way a reader would. I watch for layout shifts, sticky units that eat the screen, autoplay sound, and close buttons that are hard to tap. I also check whether the ad loads late and pushes content down after someone starts reading.

If a unit is intrusive, I remove it. That can mean pulling a sticky footer ad, turning off a full-screen interstitial, or dropping a slot that causes too much movement. I would rather lose one placement than train readers to leave. When I test a change, I compare the page on the same phone before and after, then watch complaint volume for a week or two. For small sites, a handful of emails can be a useful signal; I do not need a big dashboard to see that a close button is too small.

I keep a short list for each review:

• Note the page and device.
• Reproduce on a real phone.
• Remove or shrink the intrusive unit.
• Recheck reading flow.
• Reply to the reader with what changed.

When I want a second opinion on which networks or formats are worth testing, I look at comparison sites such as AdNetworkRank and then verify the details myself. Provider terms change, so I always check the current documentation before making a switch. The goal is simple: ads should not get in the way of the page.

— Daniel Hayes