Ad Serving Backend Question (Development/code-related)
The development team is working on a project to streamline the way our ads are served on the backend. They showed me a prototype yesterday that really shocked me so I wanted to see if anyone else was working this way. I’ll use a simplified newspaper model as an example for their approach.
Basically, we would create ads and placements only as they were needed and delete them as we were finished. Our inventory would be blind until it was sold. So when we sell the Sports Section Photo Galleries we would go into the site admin/CMS and create those ads tags, create them in the ad server, and then create the campaign in the ad server and traffic the ad. Then when the campaign is over, we’re supposed to delete that “ad path” from the CMS only keeping paths live as they were what the developers see as relevant because they are actively sold. So unless we had an ad sold to the Lifestyle or Business sections, those impressions would fall to bulk network tags.
Are any of you manually manipulating the inventory on your sites like this? I guess I should say that we’re doing about 120M impressions per month to a 50-site network. My level of visibility for forecasting would be whatever was gathered in Google Analytics.
Is this as ludacris as it sounds or do I need to shift my thinking?
Thanks for the reality check,