1.6.2 Release

A Critical Signup bug was found by a user. The wrong field was getting assigned a MySQL date.
Also another bug was fixed for a new bug found by a user: Windows requires an .xlsx extension to open the file after download. Windows 8 does not require this (mime type), but it could be a previous version of Windows.

1.6.1 Release

One of the Ad Networks using NginAd for RTB found a massive bug with some of the new 1.6 classes which compile RTB statistics for RTB requests shown in the inventory choosers. We have patched these bugs, with mutexes and semaphores that spin lock the data keys in APC while the existing data is flushed back to the DB in an upsert.

1.6 Release

NginAd 1.6 release. This release features private exchanges, vanity domains, AJAX creatives uploads and much more. There is a confluence page describing the features and differences here: https://nginad.atlassian.net/wiki/display/NGIN/NginAd-Concepts

1.5.2 Release

The 1.5.2 release adds support for the Fidelity Media OpenRTB bid responder module: http://fidelity-media.com

• It also adds nurl (bid win notice URL) tracking and logging and a JSON log aggregator in the new unit_test folder.

1.5.1 Release

The 1.5.1 release adds support for the Forensiq.com proprietary Ad Fraud detection service.
It adds both the OpenRTB API implementation for real time ad fraud blocking and the pixel service for tracking the success of the blocking campaign after the ad tag has already been shown, or is in the process of being loaded by the end user's browser. Support for Forensiq is disabled by default just like the Project Honeypot check.
You need to go to http://www.forensiq.com and contact them if you wish to pay for their service.
Also, the paid 3rd party API was optimized in the work flow so it's only used when an OpenRTB request has a valid response. You wouldn't want to run up your 3rd party service API bill if your instance of NginAd has no valid response to the bid request. Also added was a tasklet to check the floor price against the OpenRTB impression bidfloor price. That way it can respect the low bid of DSPs. You may want to disable this, but it's enabled by default.

1.5 Release

The 1.5 release fixes various OpenRTB specific bugs encountered when using the app versus the site object. It also fixes a logging bug with the geo object. Also added some new monthly invoicing SQL scripts.

1.4.51 Release

The 1.4.51 release adds Google backed Project Honeypot ad fraud detection to NginAd, though it is disabled by default.

1.4.50 Release

The 1.4.50 Release includes a critical fix for the bidding logic and a fix for the OpenRTB fold position check.

1.4.49 Release

This release includes a security fix for publisher and demand registrations and also contains a workflow logic fix for ExclusiveInclusion domains so that if at least one exclusive inclusion domain on the list is present the business logic will bid on the impression as long as all other criteria are met.

• Security fix for direct controller POST of sign-up information
• Business Logic fix for ExclusiveInclusion domains in the demand dashboard.
• Bug fix for updating the network loss rates on individual publishers
• MySQL schema fix to allow for over 10 countries or states to be filtered in the demand dashboard's geo filters

1.4.48 Release

The 1.4.48 release to address the lack of a way to view statistics for an individual demand customer or publisher as admin, and provides a way to download excel stats for single users only for accounting purposes.
Also addresses the lack of admin email alerts and ways to turn those alerts on or off via the email config file.

• Fixes statistics functions so if a publisher or demand user is selected, the statistics will be shown for that user only until they are deselected. The same functionality is applied to the Excel file download.
• Also adds configurable email alerts for the following user events: user sign-ups, ad zone changes, website domain additions, and ad campaign changes. The new alerts are configurable in email.local.php in the dist file.
• Users need to be notified by email when their domains, ad zones and ad campaigns are manually approved as opposed to auto-approval for publisher domains and ad zones. The new alerts are also configurable in email.local.php in the dist file.