I sat down (virtually) with Neera Shanker from Blockthrough in December to discuss a few market trends like non-addressable audiences, privacy regulation and the platform giants (Apple and Google).
In this episode, I actually know wtf I’m talking about. It’s only my second attempt at guesting on a podcast, and the first time I really had the appropriate expertise on a subject.
Here I’m talking about ad-tech and how non-addressable audiences (no cookie IDs and such) are an important area of focus that many online publishers are not giving enough attention. If that kinda thing is interesting to you, or you just like hearing the sound of my voice, give it a listen.
Tune in to learn about how I got started in ad tech waaaaaay back in 1997. The internet was a different place back then and it’s striking to remember how a small operation could have a large impact.
Then you’ll hear about my work at Yieldmo, my day job. Hint: I really like my job. In my best radio voice I talk about my typical day, challenges I’m helping to overcome and how we measure success.
Finally, I evangelize the need for non-addressable solutions in the market. It’s a big issue that will require investment (time and money) in order to future-proof the industry.
If you’d like to grab the podcast in your favorite app, jump over to buzzsprout for the links.
You may have heard of this being referred to as Stack Class. These white-board sessions originated in the early days of Real-Time Bidding (RTB), before the dark times… before The Empire, er.. Header Bidding. Before Header Bidding.
This video is a little dated, but it covers the technical basics of RTB. I’ve been toting it around for years privately. I figured it’s about time to set it free.
I called it Stack Class in the beginning because I was describing all the components of RTB, you know… the stack upon which everything is built. In this video you’ll find SSPs, DSPs, user synchronization (cookies?!%$#@!), bids, responses, PMPs, ad markup… you know, all the things.
A couple weeks ago I was looking over geographic location data to inform the return on investment of an advertising campaign. A significant portion of metropolitan data was showing a large percentage of the users sitting in the exact same location. It was as if they all checked-in on their apps while they were standing at the center of the city. That seemed unlikely. Was there something wrong with the data? Well, yes and no. More importantly: was it fraud?
I was trying to figure out what to do with my Sunday. My options were: build a little header bidding ad server plugin for WordPress; run, sleep and eat; or write up some blog post on a pacing algorithm, because people still seem to be producing crappy ones. Since you’re reading this, you can probably guess which choice I made. I mean, it’s not the first post I’ve written on the subject.
It showed up again last week. I didn’t expect it, but I guess I never do. A saw-tooth pattern on a chart, indicative of a capping of sorts. A chart that says, “I want a thing to happen, but only so much.” In this case it was a traffic allocation. This was a surprise.
A little history
Most of the time when I run into a bad pacing algorithm it’s in the form of a campaign trying to limit itself. It only needs to acquire a few thousand impressions every five minutes, for example. So the hastily written algorithm might divvy up the impression allocation into five minutes buckets. Effectively that’s 12 buckets every hour. So it takes an hour’s worth of impression needs and divides it by twelve. One twelfth of the impressions are purchased every five minutes. Unfortunately at that point it switches to a simple counter that says, “for the next five minutes buy impressions until the number purchased reaches 1/12th of what I need in this hour.”
You end up with a purchase graph that looks like this.
Having just returned from my fifth trip to Tokyo, I think I’m finally comfortable offering some tips, tricks and a short-list of fun sights to see. This is by no means a comprehensive list. It’s just enough to facilitate your basic mobility needs and your curiosity. I’ll start with the airport.
Terminal One at Narita International Airport is part airport, part train station, and part shopping mall. Your other international hubs have cute stores and all, but how many choices of kitch and foodstuffs and ramen shops can you find? Chances are you won’t find half as many as you do at Narita. The trick is that you have to hit both sides of T1 if you want to catch ‘em all. Unfortunately you’ll be locked into one or the other, depending on your airline. Worry not, wayward traveler, you win on either side.
I’m still searching for the best way to get to downtown Tokyo from the airport. Right now I’m getting a full-fare ticket on the Narita Express (NEX) on the JR East railway. Unfortunately you have to pay cash, about 3,000 yen, if you want to use the automated machines. Your western credit cards won’t work in them. If all you’ve got is your Visa, you’ll have to wait in line and get it from an agent. If it’s your first time in JP, you might want to do that anyway. Some of the machine jibber jabber can be a bit confusing for a non-native, even when you set the language to English. Read on to find out the easy math of the Japanese Yen and how you might encounter more than a few smokers indoors