4 ms·
> ads can be requested server side by sending the URL where the ad will be displayed through an API. The response contains the ad code, as well as the expiratio
by yilugurlu 10y ago
> ads can be requested server side by sending the URL where the ad will be displayed through an API. The response contains the ad code, as well as the expiration date
So, while adserver waiting for an ad from the RTB waterfall, then your server would wait too. It's not best practice I guess.
Besides that, many of your points already adopted by all ad networks. Many of the ad sector's problems directly related to advertisers. They want to measure everything, everything! There is a section in VAST definition called TrackingEvents. start, firstQuartile, midpoint, thirdQuartile, complete, pause, mute, click, skip ... goes on.
Agency make plans and send Vast codes to networks (for example sizmek vast code). We have many publishers well we have to measure that actions too. Stats has to be match. Then we are putting incoming vast to our adserver and it generates new one with wrapped vast. Then we are sending to publisher and of course they want to measure these actions too. They putting our vast code to their DFP and it generates new codes and ad goes to public.
Dfp Code > Our Adserver Code > Agency code
Then user sees the ad, for example video ad then tracking starts.
Impression: [Dfp, Our adserver, Sizmek]
Ad start: [Dfp, Our adserver, Sizmek]
First Quartile: [Dfp, Our adserver, Sizmek]
Midpoint: [Dfp, Our adserver, Sizmek]
Complete: [Dfp, Our adserver, Sizmek]
Click: [Dfp, Our adserver, Sizmek]
See, list goes on. One ad and many requests and counting. I am not talking about RTB waterfalls it is something else already.
We all have to measure this stats because many of the advertisers pay based on this measurements.
(you name it the currency)
%25 == 0
%50 == 0.003
%75 == 0.0055
%100 == 0.007
- spiderfarmer 10y agoRequesting ads doesn't have to be on pageload. Advertisers may want to track everything, but that doesn't mean you have to. If everyone is doing it, you can differentiate by saying NO. As a marketer my problem never was "I don't have enough data", but it always was "I don't have enough traffic". Give me quality traffic and I'll hand you my money. As a publisher THAT's what I want to offer. Quality traffic, without all the bullshit. Maybe that gets me 10% of the revenue that all scummy 'best practices' get me, but I think it will work out great in the long run. I only need an ad network to facilitate this, without having to set it up myself.
- yilugurlu 10y agoHow can I provide you a good quality traffic without having those stats? I am classifying publishers based on those stats and also requesting money from you again based on those stats. You can not differentiate by saying not, because there is no such an option like NO!
- spiderfarmer 10y agoI define good quality traffic by what they are doing on my website, not by who they are or what they are doing before they end up here.
- shostack 10y agoSounds like you are a direct response advertiser (as am I). For brand advertisers, ad engagement is a huge part of their measurement. Likewise, for direct response advertisers growing awareness through display and video, these ad engagement signals are critical for optimizing. On-site performance is just one measure, but when you start going down the whole view-through attribution rabbit hole, you'll want to look at engagement metrics like these to provide additional signals to steer you in the right direction.
- marcosdumay 10y agoWell, you would certainly not load ads in sync with page loads. About measurements, you can measure almost anything (except for user identity). As long as you don't monetize it. You can monetize clicks or conversions.
- pdkl95 10y ago> They want to measure everything, everything! They can learn to live without spying on everything (this means no javascript), or they can learn to deal with more and more people installing an adblocker. Wanting something doesn't mean they get it.