Projects / Max Media Manager

Max Media Manager

Max Media Manager is an ad server based on phpAdsNew, enhanced for performance, with many new features, and restructured for expansion. New features include agency support, rich media ads, conversion tracking, third-party ad tracking, and optimization and restructuring for a high-volume multi-server environment. Planned additional modules include: Search Engine Keyword Marketing, Email Marketing, Affiliate Management, and Conversion Tracking. Third-party ad tracking includes: DoubleClick, ValueClick, Bluestreak, Mediaplex, Atlas, Eyeblaster, Tango Zebra.

Tags
Licenses
Operating Systems
Implementation

Recent releases

  •  09 Aug 2004 20:44

    No changes have been submitted for this release.

    •  28 Jul 2004 08:55

      Release Notes: This release supports click tracking for internal redirects and for Atlas, Doubleclick, Tango Zebra, and many other ad servers. Problems with clearing the banner cache on multiple servers were fixed and delivery dependence on the database when a cache is present was removed. Pro-active cache regeneration was added along with third-party click tracking functionality and JavaScript tracker tags.

      Recent comments

      07 Mar 2007 14:38 gsherrow

      source for documentation
      Can you please point me to the source file for the documentation PDF since I assume that is also released under the GPL?

      19 Nov 2005 13:24 crmmaster

      Thanks
      Looking forward to all of the new improvements.

      01 Oct 2004 18:00 kenmcd2003

      Max Media Manager Update - September 29, 2004

      From the Max Media Manager Developers Mailing List

      https://max.awarez.net/mailman/listinfo/developers

      ------

      Max v0.1 is based on PHPAdsNew code.

      We have modified phpAdsNew for 2 years now, adding functionality to this code base. The time in which to add new features to phpAdsNew is LONG - the reasoning for this is the following:

      1. There is no underlying architecture. Developers have come and gone on the project, and there has not been someone with the responsibility of the long term architecture of the system.

      2. There is no developer documentation. There are different coding standards, libraries, etc. for each task, rather than a cohesive set of utilities that are documented.

      3. There is no external library use. All utilities have been coded by the developers, rather than used from PEAR or other library sites. Case in point - There is a huge amount of work that went into the caching system for phpAdsNew, rather than just importing PEAR Cache Lite, which is a faster and more robust method of caching.

      4. There is no test suite to speak of. When adding new features, it is impossible to see whether these new features break existing features.

      Because of this, we have made the following strategic decision concerning Max: Make Max v0.1 completely bug free, and use Max v0.2 as the platform for new features.

      Every issue that our customers or people in the community find with Max v0.1 (what is currently available from http://max.awarez.net) will be fixed ASAP. Releases will be made of Max v0.1 for the forseeable future. One new feature will be added to Max v0.1, which is a zone-based prioritisation system. This is due for delivery in a few weeks' time. We will, however make a release available before this, with a number of bug fixes, and additional integration with 3rd party adservers.

      Max v0.2 has been written from scratch by us over the past year.

      We have not made any releases of this product availaible, because there are major fundamental pieces missing. We plan on implementing new features on this codebase, rather than Max v0.1, because it is much faster to develop on this codebase. For example, conversion tracking took about 2 months to implement in Max v0.1, and it took about 7 days in Max v0.2.

      FYI - our plans for Max v0.2 is to integrate Ad Serving, Searchterm Bid Management, Trusted Feeds, Email Marketing, and other online marketing initiatives into one tool.

      As far as the stability of Max v0.1 is concerned, we have been by far the heaviest user (billions of ads per month) of Max Media Manager, and while there are a couple of outstanding bugs, we have no major bugs on our bug list. I am keen to make sure that Max v0.1 is an excellent, bug free tool that people enjoy using. That said, there are some improvements that can be made with Max v0.1, including:

      1. End User Documentation

      2. Administration Documentation

      3. Robust upgrade path from Max and phpAdsNew

      4. A more seamless installation and configuration methodology

      If anyone wants to help in any of these areas, please let me know! I can get you started off the right foot!

      If you have any issues, please post them to the list. Usually, all issues can be fixed by tweaking the configuration, and they can be answered quickly by someone on the list rather than spending the day trying to get to the bottom of the issue yourself. Also, if you intend to modify the source, either myself or any of the Max developers are intimately familiar with the code, and can answer any questions you may have. Also, if there are specific things that are making your life with Max difficult, email the list or myself personally, and I will try to help you out.

      I hope this gives you a little insight on what we are up to at the moment, and I encourage you to be active on this list.

      I hear your feedback, and will try to be more respectful to the community by resuming an aggressive release schedule for Max v0.1, and by releasing Max v0.2 to the community for feedback sooner rather than later, even though the ad serving engine is not finished yet.

      Thanks,

      Scott Switzer

      Lead Developer

      Screenshot

      Project Spotlight

      OpenStack4j

      A Fluent OpenStack client API for Java.

      Screenshot

      Project Spotlight

      TurnKey TWiki Appliance

      A TWiki appliance that is easy to use and lightweight.